Changeset 4e982a0 for BOOK/bootable/x86/kernel.xml

Timestamp:

Jun 13, 2014, 8:54:33 PM (10 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-3.0.0-systemd, master, systemd

Children:

031870f9, 21e76b6

Parents:

7a62c83

Message:

Updated text on kernel page

File:

• BOOK/bootable/x86/kernel.xml (modified) (1 diff)

BOOK/bootable/x86/kernel.xml

@@ -104 +104 @@
 <screen os="n"><userinput>make</userinput></screen>
 
-    <para os="o">If using kernel modules, an
-    <filename>/etc/modprobe.conf</filename> file may be needed.
+    <para os="o">If using kernel modules, a configuration file in
+    <filename class="directory">/etc/modprobe.d</filename> file may be needed.
     Information pertaining to modules and kernel configuration is
     located in the kernel documentation in the <filename
     class="directory">Documentation</filename> directory of the kernel
-    sources tree. Also, <filename>modprobe.conf(5)</filename> may
+    sources tree. Also, <filename>modprobe.d(5)</filename> may
     be of interest.</para>
-
-    <para os="p">Be very careful when reading other documentation relating to
-    kernel modules because it usually applies to 2.4.x kernels only. As
-    far as we know, kernel configuration issues specific to Hotplug and
-    Eudev are not documented. The problem is that Eudev 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 the one below in the
-    <filename>/etc/modprobe.conf</filename> file do not work with Eudev:</para>
-
-<screen os="q"><literal>alias char-major-XXX some-module</literal></screen>
-
-    <para os="r">Because of the complications with Eudev and modules,
-    we strongly recommend starting with a completely non-modular kernel
-    configuration, especially if this is the first time using Eudev.</para>
 
     <para os="s">Install the modules, if the kernel configuration uses