Release: 0.2 (Vega)
Devel:   0.3




                     ============================
                      FREQUENTLY ASKED QUESTIONS
                     ============================

[Q]  Why the name Arch Linux?
[A]  From dictionary.com:

     arch (ärch)
     adj.

     1. Chief; principal: their arch foe.
     2. Mischievous; roguish: an arch glance.


     I came across the well-known term "arch-enemy" in a book and
     clued in that "arch" means "the primary", "the principal", the one
     that comes first among others.  Far from true with regard to
     Arch Linux perhaps, but I'm proud of it.  Now, the second
     definition may or may not fit; I guess it depends on how you use
     your computer.  ;)

[Q]  What is Arch Linux all about?  What's it trying to do?
[A]  Arch Linux is my perfect distro, to sum it up.  I starting building
     it for two reasons:

       1) I didn't find any other distributions that met my ideals.  Some
          came very close to what I wanted but there were annoying
          quirks, or an added complexity that seemed to hurt more than
          help.
       2) For fun, and to give a little something back to the free
          software community, since I've taken so much.

     Arch Linux is fast.  Packages are compiled with i686 optimizations.

     Arch Linux is small.  It doesn't install things that it doesn't
     need unless you ask for them.  Packages can be cleanly installed
     and removed, no cruft or clutter.  Even /usr/doc is gone -- if I
     need documentation, I can read it on the net, so /usr/doc is
     useless to me.

     Arch Linux is simple.  Almost all utility and package management
     programs are written in bash except for the package manager itself.
     Things are flexible and easy to tweak in Arch Linux.  The package
     database is in plain text format, the init scripts are simple
     bsd-style, but with clean output and an easy way to start/stop
     daemons.  The package build system is simple so users are
     encouraged to build their own packages.  The Arch Build System is
     summed up in a single man page ('man makepkg').

     Arch Linux is flexible.  Because of its simplicity, AL can easily
     be extended or modified to suit different tasks.  I will be posting
     a document that provides step-by-step instructions for creating a
     customized boot cd.

[Q]  Are you going to add dependency support in to pacman?
[A]  Yes.

[Q]  I can't ssh into my machine!
[A]  Edit your /etc/hosts.deny file.  The default configuration will
     reject all incoming connections.

[Q]  I just installed XFree86 and now I get a "cannot find libX" error
     when I run startx.
[A]  Your ld.so.cache needs updating so binaries know where to find the
     newly installed X libs.  In other words, run 'ldconfig' as root.

[Q]  I ran 'pacsync sysupgrade' on my machine and now I get LILO errors
     on bootup.
[A]  See if you've upgraded the lilo package.  A new version of lilo
     means you have to re-install the bootloader.  Run 'lilo' as root.

[Q]  pacsync has gone crazy on me.  It wants me to upgrade to an older
     package.
[A]  This is probably because you forgot to run 'pacsync sync' first.

[Q]  I have built some of my own packages for Arch Linux that aren't on
     the AL servers.  Do you want them?
[A]  You bet.  You can upload them to ftp://ftp.archlinux.org/incoming
     When you submit the ABS build files, please include them in their
     own subdirectory.  Once they are approved and assigned to a package
     maintainer, the package will be added to the pacsync list and made
     available for general download.

$Id: faq.txt,v 1.7 2002/04/25 07:06:38 jvinet Exp $