diff options
Diffstat (limited to 'doc/handbook/faq.xml')
| -rw-r--r-- | doc/handbook/faq.xml | 178 |
1 files changed, 178 insertions, 0 deletions
diff --git a/doc/handbook/faq.xml b/doc/handbook/faq.xml new file mode 100644 index 0000000..1c14079 --- /dev/null +++ b/doc/handbook/faq.xml @@ -0,0 +1,178 @@ +<!-- $Id: faq.xml,v 1.6 2004/05/28 11:30:00 per Exp $ --> + +<title>Frequently Asked Questions</title> + +<section id="Frequently-Asked-Questions-General"> + <title>General</title> + + <procedure> + <step> + <title>Why the name <quote>CRUX</quote>?</title> + + <para>Sorry, there's no interesting story behind the name. + I chose it simply because I thought it sounded cool, it was short, + it was failry easy to remember and it had the mandatory X in the end + to make it UNIX/Linux-ish ;)</para> + </step> + + <step> + <title>When will the next version be released?</title> + + <para>Well, the standard answer to this question is + <quote>when it's done</quote>. New versions are however + usually released every 3 or 4 months. Between releases, + updated packages are made available through the ports + system.</para> + </step> + + <step> + <title>Is it called CRUX Linux or CRUX GNU/Linux?</title> + + <para>None of the above. It's called CRUX, no more no less.</para> + </step> + + <step> + <title>I heard CRUX was based on Slackware, is that true?</title> + + <para>No, that's incorrect. CRUX was built from scratch and has never + been based on any other Linux distribution.</para> + </step> + </procedure> +</section> + +<section id="Frequently-Asked-Questions-Installation"> + <title>Installation</title> + + <procedure> + <step> + <title>Will CRUX work with AMD K6/K6-II/K6-III?</title> + + <para>Yes and No. AMD K6, K6-II and K6-III have an i586 + (Pentium) compatible instruction set. Packages on the official + CRUX ISO are compiled with <userinput + >-march=i686</userinput>, which means that CRUX requires a + processor which has an i686 compatible instruction set (i.e. + Intel PPro/Celeron/PII/PIII/P4 or AMD K7/Athlon). However, + Jürgen Daubert maintains an i586 version of the CRUX ISO + image which can be found <ulink url="ftp://ftp.fukt.bth.se/pub/os/linux/crux/latest/contrib/" + >here</ulink>. The i586 version of the CRUX ISO works on AMD + K6/K6-II/K6-III.</para> + </step> + + <step> + <title>When booting from the CRUX CD-ROM I get a kernel panic + saying <quote>VFS: Unable to mount root fs</quote>. What's + wrong?</title> + + <para>This can happen if you have more than one CD-ROM drive. + Make sure you boot from then "first" CD-ROM drive, i.e. + <filename>/dev/cdroms/cdrom0</filename>. If you must boot from + a different drive (i.e. not the first one) you can still do + that but you have to type <userinput>CRUX + root=/dev/cdroms/cdrom1</userinput> at the boot prompt + (<userinput>cdrom1</userinput> indicates that it is the + second drive, <userinput>cdrom2</userinput> that it is the + third, and so on).</para> + </step> + + <step> + <title>When booting CRUX for the first time I get the error + <quote>Unable to open initial console</quote>. What's + wrong?</title> + + <para>You most likely forgot to enable devfs or didn't tell the + kernel to mount devfs at boot. The installation instructions + (<xref linkend="Installing-From-CD-ROM"/>) tell you how to + enable it.</para> + </step> + + <step> + <title>When logging in to my newly installed CRUX for the first + time it asks for a password, but the installation guide says + <quote>Login as root (no password required)</quote>. What's + wrong?</title> + + <para>You most likely forgot to edit <filename + >/mnt/etc/fstab</filename> before you rebooted or you entered + the wrong name of your new root parition at the boot + prompt.</para> + </step> + </procedure> +</section> + +<section id="Frequently-Asked-Questions-Configuration"> + <title>Configuration</title> + + <procedure> + <step> + <title>Why are changes made to files under <filename + >/dev</filename> lost the next time I boot into CRUX?</title> + + <para>CRUX uses <literal>devfs</literal>, which is a virtual + filsystem kept in RAM. Changes made to files under <filename + >/dev</filename> are always lost when you turn off the power. + However, you can configure <userinput>devfsd(8)</userinput> + to restore them when you boot. You need to modify <filename + >/etc/devfsd.conf</filename> according to your needs. See the + <userinput>devfsd(8)</userinput> man-page for details. + Example:</para> + + <informalexample> +<programlisting># +# /etc/devfsd.conf: devfsd(8) configuration +# + +REGISTER .* MKOLDCOMPAT +UNREGISTER .* RMOLDCOMPAT + +LOOKUP .* MODLOAD + +REGISTER ^sound/.* PERMISSIONS root.users 660 +REGISTER ^v4l/.* PERMISSIONS root.users 660 + +# End of file</programlisting> + </informalexample> + </step> + + <step> + <title>How do I get sshd running?</title> + + <para>You have to edit <filename>/etc/hosts.deny</filename> + and/or <filename>/ets/hosts.allow</filename> to specify which + hosts are allowed/denied access. To allow anyone to connect + to your machine you can add <literal>sshd: ALL</literal> to + <filename>/etc/hosts.allow</filename>. See the + <literal>hosts_access(5)</literal> man-page for further + information about the file format. When this is done you can + start sshd by entering the command <userinput>/etc/rc.d/sshd + start</userinput> and/or edit <filename + >/etc/rc.conf</filename> and add <literal>sshd</literal> to + the <literal>SERVICES</literal> array, i.e. <literal + >SERVICES=(<replaceable + >...</replaceable> sshd <replaceable + >...</replaceable>)</literal>, which means that sshd will be + started when the system boots.</para> + </step> + + <step> + <title>Mozilla crashes or refuses to start, what's wrong?</title> + + <para>Mozilla is extremely sensitive to missing <filename + >fonts.cache-1</filename> files. If mozilla refuses to start + (due to segmentation violation or just silent permature + termination) it is most likely becuase the font cache files + are missing. Run <userinput>fc-cache</userinput> (as + <userinput>root</userinput>) to create/update the cache files. + See the <userinput>fc-cache(1)</userinput> man page for + information about this program.</para> + </step> + + <step> + <title>It says <quote><literal>ports: no driver(s) installed</literal></quote> when + I try to update my ports, what's wrong?</title> + + <para>You forgot to install the <filename>opt/cvsup</filename> package. You will find + it on the CRUX ISO (under <filename>/crux/opt/</filename>).</para> + </step> + </procedure> +</section> |