From 0c012ac2c96978a0d297cdd21888564f8267bc8c Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Sat, 19 Jun 2004 20:41:59 +0000 Subject: Fixed the identation of /etc/fstab and some tagins regresions. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3819 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter07/console.xml | 2 +- chapter08/fstab.xml | 12 ++++++------ chapter08/kernel.xml | 27 ++++++++++++--------------- 3 files changed, 19 insertions(+), 22 deletions(-) diff --git a/chapter07/console.xml b/chapter07/console.xml index 0e3cbe2ca..0c0d6fd8f 100644 --- a/chapter07/console.xml +++ b/chapter07/console.xml @@ -95,7 +95,7 @@ EOF setting it every time from the console bootscript, then instructions are given in . Doing this ensures that your keyboard will always work as expected, even when you boot into -maintenance mode (by passing `init=/bin/sh' to the kernel), as in that +maintenance mode (by passing init=/bin/sh to the kernel), as in that situation, the console bootscript won't be run. Since the kernel will set up the keymap, you can omit the KEYMAP variable diff --git a/chapter08/fstab.xml b/chapter08/fstab.xml index ef811fada..c5cc0123b 100644 --- a/chapter08/fstab.xml +++ b/chapter08/fstab.xml @@ -19,12 +19,12 @@ this: # file system mount-point fs-type options dump fsck-order -/dev/[xxx] / [fff] defaults 1 1 -/dev/[yyy] swap swap pri=1 0 0 -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 +/dev/[xxx] / [fff] defaults 1 1 +/dev/[yyy] swap swap pri=1 0 0 +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 # End /etc/fstab EOF diff --git a/chapter08/kernel.xml b/chapter08/kernel.xml index 099eb4254..d600342a8 100644 --- a/chapter08/kernel.xml +++ b/chapter08/kernel.xml @@ -51,8 +51,7 @@ to userspace until userspace specifies that it is ready: If, in , you decided you want to compile the keymap into the kernel, issue the command below: -loadkeys -m -/usr/share/kbd/keymaps/[path to keymap] > \ +loadkeys -m /usr/share/kbd/keymaps/[path to keymap] > \ [unpacked sources dir]/linux-&linux-version;/drivers/char/defkeymap.c For example, if you have a Dutch keyboard, you would use @@ -62,7 +61,7 @@ to compile the keymap into the kernel, issue the command below: make menuconfig -make oldconfig may be more appropriate in some +make oldconfig may be more appropriate in some situations. See the README file for more information. @@ -79,9 +78,9 @@ scratch. the File systems menu and is normally enabled by default. LFS bootscripts make the assumption that you either compile -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). +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). 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 @@ -96,14 +95,12 @@ unless you know what you're getting yourself into. /etc/modprobe.conf file. Information pertaining to modules and to kernel configuration in general may be found in the kernel documentation, which is found in the -linux-&linux-version;/Documentation directory. -The -modprobe.conf man page +linux-&linux-version;/Documentation directory. +The modprobe.conf man page -may also be of -interest to you. +may also be of interest to you. Be very suspicious while reading other documentation, because it usually applies to 2.4.x kernels only. As far as the editors know, kernel @@ -130,7 +127,7 @@ isn't worth the trouble, but if you're really pressed for space, then have a loo . Kernel compilation has finished but more steps are required to complete -the installation. Some files need to be copied to the /boot +the installation. Some files need to be copied to the /boot directory. The path to the kernel image may vary depending on the platform you're @@ -163,8 +160,8 @@ the packager used will be assigned to somebody on your machine and then that person would have write access to the kernel source. If you are going to keep the kernel source tree around, you may want to -run chown -R 0:0 on the -linux-&linux-version; directory to ensure all files are +run chown -R 0:0 on the +linux-&linux-version; directory to ensure all files are owned by user root. @@ -199,7 +196,7 @@ of running scores of programs seemingly at the same time. kernel headers define the interface to the services that the kernel provides. The headers in your system's -include directory should always be +include directory should always be the ones against which Glibc was compiled and should therefore not be replaced when upgrading the kernel. -- cgit v1.2.3-54-g00ecf