- Timestamp:
- 07/01/2005 11:16:14 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- 808f5af
- Parents:
- 90b56f5
- Location:
- chapter07
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/bootscripts.xml
r90b56f5 raabd480 11 11 12 12 <sect2 role="package"><title/> 13 <para>The LFS-Bootscripts package contains a set of bootscripts.</para> 13 <para>The LFS-Bootscripts package contains a set of scripts to start/stop the 14 LFS system at bootup/shutdown.</para> 14 15 15 16 <segmentedlist> … … 34 35 </sect2> 35 36 36 <sect2 id="contents-bootscripts" role="content"><title>Contents of LFS- bootscripts</title>37 <sect2 id="contents-bootscripts" role="content"><title>Contents of LFS-Bootscripts</title> 37 38 38 39 <segmentedlist> -
chapter07/introduction.xml
r90b56f5 raabd480 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <para>This chapter details how to install the bootscripts and set them up11 p roperly. Most of these scripts will work without modification, but a12 few require additional configuration files because they deal with 13 hardware-dependentinformation.</para>10 <para>This chapter details how to install and configure the LFS-Bootscripts 11 package. Most of these scripts will work without modification, but a few require 12 additional configuration files because they deal with hardware-dependent 13 information.</para> 14 14 15 15 <para>System-V style init scripts are employed in this book because they are -
chapter07/network.xml
r90b56f5 raabd480 55 55 network script and not brought up.</para> 56 56 57 <para>The <envar>SERVICE</envar> variable defines the method of 58 obtaining the IP address. The LFS bootscripts have a modular IP 59 assignment format, and creating additional files in the <filename 60 class="directory" condition="html">/etc/sysconfig/network-devices/services</filename> 61 <filename class="directory" condition="pdf">/etc/sysconfig/network- devices/services</filename> 62 directory allows other IP assignment methods. This is commonly used 63 for Dynamic Host Configuration Protocol (DHCP), which is addressed in the BLFS book.</para> 57 <para>The <envar>SERVICE</envar> variable defines the method of obtaining the IP 58 address. The LFS-Bootscripts package has a modular IP assignment format, and 59 creating additional files in the <filename 60 class="directory">/etc/sysconfig/network-devices/services</filename> directory 61 allows other IP assignment methods. This is commonly used for Dynamic Host 62 Configuration Protocol (DHCP), which is addressed in the BLFS book.</para> 64 63 65 64 <para>The <envar>GATEWAY</envar> variable should contain -
chapter07/udev.xml
r90b56f5 raabd480 83 83 processes and to <command>udev</command> for device node creation.</para> 84 84 85 <para>The <command>S10udev</command> initscript takes care of creating 86 these device nodes when Linux is booted. This script starts with 87 registering <command>/sbin/udevsend</command> as a hotplug event handler. 88 Hotplug events (discussed below) should not be generated during this 89 stage, but <command>udev</command> is registered just in case they do 90 occur. The <command>udevstart</command> program then walks through 91 the <systemitem class="filesystem">/sys</systemitem> filesystem and 92 creates devices under <filename class="directory">/dev</filename> that 93 match the descriptions. For example, 94 <filename>/sys/class/tty/vcs/dev</filename> contains the string 95 <quote>7:0</quote> This string is used by <command>udevstart</command> 96 to create <filename>/dev/vcs</filename> with major number 97 <emphasis>7</emphasis> and minor <emphasis>0</emphasis>. The names and 98 permissions of the nodes created under the 99 <filename class="directory">/dev</filename> directory are configured according 100 to the rules specified in the files within the 101 <filename class="directory">/etc/udev/rules.d/</filename> directory. These are 102 numbered in a similar fashion to the LFS bootscripts. If 103 <command>udev</command> can't find a rule for the device it is creating, it will 104 default permissions to <emphasis>660</emphasis> and ownership to 105 <emphasis>root:root</emphasis>.</para> 85 <para>The <command>S10udev</command> initscript takes care of creating these 86 device nodes when Linux is booted. This script starts with registering 87 <command>/sbin/udevsend</command> as a hotplug event handler. Hotplug events 88 (discussed below) should not be generated during this stage, but 89 <command>udev</command> is registered just in case they do occur. The 90 <command>udevstart</command> program then walks through the <systemitem 91 class="filesystem">/sys</systemitem> filesystem and creates devices under 92 <filename class="directory">/dev</filename> that match the descriptions. For 93 example, <filename>/sys/class/tty/vcs/dev</filename> contains the string 94 <quote>7:0</quote> This string is used by <command>udevstart</command> to create 95 <filename>/dev/vcs</filename> with major number <emphasis>7</emphasis> and minor 96 <emphasis>0</emphasis>. The names and permissions of the nodes created under 97 the <filename class="directory">/dev</filename> directory are configured 98 according to the rules specified in the files within the <filename 99 class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in 100 a similar fashion to the LFS-Bootscripts package. If <command>udev</command> 101 can't find a rule for the device it is creating, it will default permissions to 102 <emphasis>660</emphasis> and ownership to <emphasis>root:root</emphasis>.</para> 106 103 107 104 <para>Once the above stage is complete, all devices that were already
Note:
See TracChangeset
for help on using the changeset viewer.