Several kernel-related textual changes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3722 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alexander E. Patrakov 2004-05-29 15:11:32 +00:00
parent 1cd9252bdd
commit a56c4bb4ed
5 changed files with 49 additions and 18 deletions

View File

@ -102,6 +102,16 @@ first a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>May 29, 2004 [alexander]: Mentioned the hotplug+udev+modules
problem. Removed the effectively dead link to the Kernel
HOWTO.</para></listitem>
<listitem><para>May 29, 2004 [alexander]: Corrected usbfs line in
/etc/fstab.</para></listitem>
<listitem><para>May 29, 2004 [alexander]: New LFS bootscripts already come
with the /etc/sysconfig/console file. Corrected the text.</para></listitem>
<listitem><para>May 25, 2004 [jeremy]: Chapter 6 - Upgraded psmisc to
21.5.</para></listitem>

View File

@ -22,10 +22,12 @@ the <command>console</command> initscript will do nothing.</para>
<filename>/etc/sysconfig/console</filename>
as a configuration file. You need to decide which keymap and screen font you
will use. The language-specific HOWTO can help you.
In the future releases of LFS-Bootscripts, there will be a pre-made
A pre-made
<filename>/etc/sysconfig/console</filename> file with known
good settings for several countries, and you will just have to uncomment
the relevant section.
good settings for several countries was installed with the LFS-Bootscripts
package, and you just have to uncomment
the relevant section if your country is supported (but read the rest
of this section anyway).
If still in doubt,
look into <filename class="directory">/usr/share/kbd</filename>
for valid keymaps and screen fonts. Then read the <command>loadkeys</command>

View File

@ -25,7 +25,6 @@ proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devpts /dev/pts devpts gid=4,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0
# End /etc/fstab
<userinput>EOF</userinput></screen>
@ -33,8 +32,7 @@ usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0
and <filename>fff</filename> with the values appropriate for your system --
for example <filename>hda2</filename>, <filename>hda5</filename> and
<filename>reiserfs</filename>. For all the details on the six fields in this
table, see <command>man 5 fstab</command>. Omit the usbfs line if you didn't
compile "USB device filesystem" into the kernel.</para>
table, see <command>man 5 fstab</command>.</para>
<para>When using a reiserfs partition, the <emphasis>1 1</emphasis> at the
end of the line should be replaced with <emphasis>0 0</emphasis>, as such a
@ -53,9 +51,10 @@ tree.</para>
<filename>fstab</filename> file. One example is a line to use if you intend to
use USB devices:</para>
<screen>usbfs /proc/bus/usb usbfs defaults 0 0</screen>
<screen> usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0 </screen>
<para>This option will of course only work if you have the relevant support
compiled into your kernel.</para>
<para>This option will of course only work if you have the
"Support for Host-side USB" and "USB device filesystem"
compiled into your kernel (not as a module).</para>
</sect1>

View File

@ -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>

View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "CVS-20040525">
<!ENTITY releasedate "May 25, 2004">
<!ENTITY version "CVS-20040529">
<!ENTITY releasedate "May 29, 2004">
<!ENTITY milestone "6.0">
<!ENTITY lfs-root "http://www.linuxfromscratch.org/">