From fde4f7de29feb3a867ab572415c2eb7722d3d880 Mon Sep 17 00:00:00 2001 From: Archaic Date: Fri, 1 Jul 2005 20:39:25 +0000 Subject: Brought all occurences of LFS-Bootscripts into conformity. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6288 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter07/bootscripts.xml | 5 +++-- chapter07/introduction.xml | 8 ++++---- chapter07/network.xml | 12 ++++++------ chapter07/udev.xml | 39 ++++++++++++++++++--------------------- 4 files changed, 31 insertions(+), 33 deletions(-) (limited to 'chapter07') diff --git a/chapter07/bootscripts.xml b/chapter07/bootscripts.xml index 186e29730..721b4e909 100644 --- a/chapter07/bootscripts.xml +++ b/chapter07/bootscripts.xml @@ -10,7 +10,8 @@ Bootscripts -<para>The LFS-Bootscripts package contains a set of bootscripts.</para> +<para>The LFS-Bootscripts package contains a set of scripts to start/stop the +LFS system at bootup/shutdown.</para> <segmentedlist> <segtitle>&buildtime;</segtitle> @@ -33,7 +34,7 @@ </sect2> -<sect2 id="contents-bootscripts" role="content"><title>Contents of LFS-bootscripts +Contents of LFS-Bootscripts Installed scripts diff --git a/chapter07/introduction.xml b/chapter07/introduction.xml index b4c8ea547..c54d7fdab 100644 --- a/chapter07/introduction.xml +++ b/chapter07/introduction.xml @@ -7,10 +7,10 @@ Introduction -This chapter details how to install the bootscripts and set them up -properly. Most of these scripts will work without modification, but a -few require additional configuration files because they deal with -hardware-dependent information. +This chapter details how to install and configure the LFS-Bootscripts +package. Most of these scripts will work without modification, but a few require +additional configuration files because they deal with hardware-dependent +information. System-V style init scripts are employed in this book because they are widely used. For additional options, a hint detailing the BSD style diff --git a/chapter07/network.xml b/chapter07/network.xml index dbbf283dc..98bb8f7d7 100644 --- a/chapter07/network.xml +++ b/chapter07/network.xml @@ -54,12 +54,12 @@ Network Interface Card (NIC) during booting of the system. If set to anything but yes the NIC will be ignored by the network script and not brought up. -The SERVICE variable defines the method of -obtaining the IP address. The LFS bootscripts have a modular IP -assignment format, and creating additional files in the /etc/sysconfig/network-devices/services -directory allows other IP assignment methods. This is commonly used -for Dynamic Host Configuration Protocol (DHCP), which is addressed in the BLFS book. +The SERVICE variable defines the method of obtaining the IP +address. The LFS-Bootscripts package has a modular IP assignment format, and +creating additional files in the /etc/sysconfig/network-devices/services directory +allows other IP assignment methods. This is commonly used for Dynamic Host +Configuration Protocol (DHCP), which is addressed in the BLFS book. The GATEWAY variable should contain the default gateway IP address, if one is present. If not, then comment out diff --git a/chapter07/udev.xml b/chapter07/udev.xml index 5cdd2d363..7b9be92ad 100644 --- a/chapter07/udev.xml +++ b/chapter07/udev.xml @@ -82,27 +82,24 @@ built-in drivers registered with sysfs are available to userspace processes and to udev for device node creation. -The S10udev initscript takes care of creating -these device nodes when Linux is booted. This script starts with -registering /sbin/udevsend as a hotplug event handler. -Hotplug events (discussed below) should not be generated during this -stage, but udev is registered just in case they do -occur. The udevstart program then walks through -the /sys filesystem and -creates devices under /dev that -match the descriptions. For example, -/sys/class/tty/vcs/dev contains the string -7:0 This string is used by udevstart -to create /dev/vcs with major number -7 and minor 0. The names and -permissions of the nodes created under the -/dev directory are configured according -to the rules specified in the files within the -/etc/udev/rules.d/ directory. These are -numbered in a similar fashion to the LFS bootscripts. If -udev can't find a rule for the device it is creating, it will -default permissions to 660 and ownership to -root:root. +The S10udev initscript takes care of creating these +device nodes when Linux is booted. This script starts with registering +/sbin/udevsend as a hotplug event handler. Hotplug events +(discussed below) should not be generated during this stage, but +udev is registered just in case they do occur. The +udevstart program then walks through the /sys filesystem and creates devices under +/dev that match the descriptions. For +example, /sys/class/tty/vcs/dev contains the string +7:0 This string is used by udevstart to create +/dev/vcs with major number 7 and minor +0. The names and permissions of the nodes created under +the /dev directory are configured +according to the rules specified in the files within the /etc/udev/rules.d/ directory. These are numbered in +a similar fashion to the LFS-Bootscripts package. If udev +can't find a rule for the device it is creating, it will default permissions to +660 and ownership to root:root. Once the above stage is complete, all devices that were already present and have compiled-in drivers will be available for use. What -- cgit v1.2.3-54-g00ecf