|
@@ -64,8 +64,9 @@ scratch.</para>
|
|
|
the <quote>File systems</quote> menu and is normally enabled by default.</para>
|
|
|
|
|
|
<para>LFS bootscripts make the assumption that you either compile
|
|
|
-"USB device filesystem" directly into the kernel, or don't compile it at
|
|
|
-all. They will not work properly if it is a module (usbcore.ko).</para>
|
|
|
+both "Support for Host-side USB" and
|
|
|
+"USB device filesystem" directly into the kernel, or don't compile them at
|
|
|
+all. Bootscripts will not work properly if it is a module (usbcore.ko).</para>
|
|
|
|
|
|
<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in this case
|
|
|
&gcc-version;. Compiling with 2.95.x is known to cause failures in the glibc
|
|
@@ -76,16 +77,35 @@ unless you know what you're getting yourself into.</para></note>
|
|
|
|
|
|
<screen><userinput>make</userinput></screen>
|
|
|
|
|
|
-<para>If you intend to use kernel modules, you will need an
|
|
|
+<para>If you intend to use kernel modules, you may need an
|
|
|
<filename>/etc/modprobe.conf</filename> file. Information pertaining
|
|
|
to modules and to kernel configuration in general may be found in the
|
|
|
kernel documentation, which is found in the
|
|
|
-<filename>linux-&linux-version;/Documentation</filename> directory. The
|
|
|
-modules.conf man page and the kernel HOWTO at
|
|
|
-<ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> may also be of
|
|
|
+<filename>linux-&linux-version;/Documentation</filename> directory.
|
|
|
+The
|
|
|
+modprobe.conf man page
|
|
|
+<!-- removed for review from tldp.org
|
|
|
+and the kernel HOWTO at
|
|
|
+<ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> -->
|
|
|
+may also be of
|
|
|
interest to you.</para>
|
|
|
|
|
|
-<para>Install the modules:</para>
|
|
|
+<para>Be very suspicious while reading other documentation, because it
|
|
|
+usually applies to 2.4.x kernels only. As far as the editors know, kernel
|
|
|
+configuration issues specific to Hotplug and Udev
|
|
|
+are documented nowhere. The problem is that Udev will create a device node
|
|
|
+only if Hotplug or a user-written script inserts the corresponding module
|
|
|
+into the kernel, and not all modules are detectable by Hotplug. Note
|
|
|
+that statements like
|
|
|
+<screen>alias char-major-XXX some-module</screen>
|
|
|
+in <filename>/etc/modprobe.conf</filename> file don't work with
|
|
|
+Udev, and other aliases are often unnecessary with Hotplug.</para>
|
|
|
+
|
|
|
+<para>Because of all those compilcations with Hotplug, Udev and modules, we
|
|
|
+strongly recommend you to start with a completely non-modular kernel
|
|
|
+configuration, especially if this is the first time you use Udev.</para>
|
|
|
+
|
|
|
+<para>Install the modules, if your kernel configuration uses them:</para>
|
|
|
|
|
|
<screen><userinput>make modules_install</userinput></screen>
|
|
|
|