Changeset aabd480
- Timestamp:
- 07/01/2005 11:16:14 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- 808f5af
- Parents:
- 90b56f5
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
appendixb/acknowledgments.xml
r90b56f5 raabd480 36 36 37 37 <listitem><para><ulink url="mailto:nathan@linuxfromscratch.org">Nathan 38 Coulson</ulink> <nathan@linuxfromscratch.org> – LFS bootscripts38 Coulson</ulink> <nathan@linuxfromscratch.org> – LFS-Bootscripts 39 39 maintainer</para></listitem> 40 40 … … 91 91 <listitem><para><ulink url="mailto:jeremy@linuxfromscratch.org">Jeremy 92 92 Utley</ulink> <jeremy@linuxfromscratch.org> – LFS Technical 93 Writer, Bugzilla maintainer, LFS bootscripts maintainer, LFS Server93 Writer, Bugzilla maintainer, LFS-Bootscripts maintainer, LFS Server 94 94 co-administrator</para></listitem> 95 95 -
chapter01/changelog.xml
r90b56f5 raabd480 88 88 </listitem> 89 89 90 <listitem><para>July 1st, 2005 [archaic]: Brought all occurences of 91 LFS-Bootscripts into conformity.</para></listitem> 92 90 93 <listitem><para>June 30th, 2005 [archaic]: Several minor wording changes in 91 94 chapters 1 - 5 (matt).</para></listitem> -
chapter01/how.xml
r90b56f5 raabd480 72 72 computer as normal.</para> 73 73 74 <para>To finish the installation, the bootscripts are set up in <xref74 <para>To finish the installation, the LFS-Bootscripts are set up in <xref 75 75 linkend="chapter-bootscripts"/>, and the kernel and boot loader are set 76 76 up in <xref linkend="chapter-bootable"/>. <xref -
chapter06/devices.xml
r90b56f5 raabd480 31 31 be created dynamically on that virtual filesystem as they are detected or 32 32 accessed. This is generally done during the boot process. Since this new system 33 has not been booted, it is necessary to do what the bootscripts would otherwise34 do by mounting <filename class="directory">/dev</filename>:</para>33 has not been booted, it is necessary to do what the LFS-Bootscripts package would 34 otherwise do by mounting <filename class="directory">/dev</filename>:</para> 35 35 36 36 <screen><userinput>mount -n -t tmpfs none /dev</userinput></screen> … … 52 52 53 53 <para>There are some symlinks and directories required by LFS that are created 54 during system startup by the bootscripts. Since this is a chroot environment and55 not a booted environment, those symlinks and directories need to be created 56 here:</para>54 during system startup by the LFS-Bootscripts package. Since this is a chroot 55 environment and not a booted environment, those symlinks and directories need to 56 be created here:</para> 57 57 58 58 <screen><userinput>ln -s /proc/self/fd /dev/fd -
chapter06/hotplug.xml
r90b56f5 raabd480 41 41 <screen><userinput>cp etc/hotplug/pnp.distmap /etc/hotplug</userinput></screen> 42 42 43 <para>Remove the init script that Hotplug installs , since we're going to be44 using the script included with LFS-Bootscripts:</para>43 <para>Remove the init script that Hotplug installs since we are going to be 44 using the script included in the LFS-Bootscripts package:</para> 45 45 46 46 <screen><userinput>rm -rf /etc/init.d</userinput></screen> 47 47 48 <para>Network device hotplugging is not supported by LFS-Bootscripts yet. For49 that reason, remove the network hotplug agent:</para>48 <para>Network device hotplugging is not yet supported by the LFS-Bootscripts 49 package. For that reason, remove the network hotplug agent:</para> 50 50 51 51 <screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen> … … 91 91 <listitem> 92 92 <para>These scripts are used for cold plugging, i.e., detecting and acting upon 93 hardware already present during system startup. 94 <filename>hotplug</filename> initscript that comes from the LFS-Bootscripts95 package. The <command>*.rc</command> scripts try to recover hotplug events that96 were lost during system boot because, for example, the root filesystem was not 97 mounted bythe kernel</para>93 hardware already present during system startup. They are called by the 94 <filename>hotplug</filename> initscript included in the LFS-Bootscripts package. 95 The <command>*.rc</command> scripts try to recover hotplug events that were lost 96 during system boot because, for example, the root filesystem was not mounted by 97 the kernel</para> 98 98 <indexterm zone="ch-system-hotplug hotplug-rc"><primary 99 99 sortas="d-/etc/hotplug/*.rc">/etc/hotplug/*.rc</primary></indexterm> -
chapter06/iproute2.xml
r90b56f5 raabd480 55 55 <varlistentry> 56 56 <term><parameter>SBINDIR=/sbin</parameter></term> 57 <listitem><para>This makes surethat the IPRoute2 binaries will install into58 <filename class="directory">/sbin</filename>. This is the correct59 location according to the FHS, because some of the IPRoute2 binaries are used60 in the bootscripts.</para>57 <listitem><para>This ensures that the IPRoute2 binaries will install into 58 <filename class="directory">/sbin</filename>. This is the correct location 59 according to the FHS, because some of the IPRoute2 binaries are used by 60 the LFS-Bootscripts package.</para> 61 61 </listitem> 62 62 </varlistentry> -
chapter06/psmisc.xml
r90b56f5 raabd480 39 39 <varlistentry> 40 40 <term><parameter>--exec-prefix=""</parameter></term> 41 <listitem><para>This causes the binaries to be installed in <filename 42 class="directory">/bin</filename> instead of <filename 43 class="directory">/usr/bin</filename>. Because the Psmisc programs are 44 often used in bootscripts, they should be available when the <filename 45 class="directory">/usr</filename> file system is not 46 mounted.</para></listitem> 41 <listitem><para>This ensures that the Psmisc binaries will install into 42 <filename class="directory">/bin</filename> instead of <filename 43 class="directory">/usr/bin</filename>. This is the correct location according to 44 the FHS, because some of the Psmisc binaries are used by the LFS-Bootscripts 45 package.</para></listitem> 47 46 </varlistentry> 48 47 </variablelist> -
chapter06/util-linux.xml
r90b56f5 raabd480 81 81 82 82 <para>Install the package and move the <command>logger</command> binary to 83 <filename class="directory">/bin</filename> as it is needed by the bootscripts:84 </para>83 <filename class="directory">/bin</filename> as it is needed by the 84 LFS-Bootscripts package:</para> 85 85 86 86 <screen><userinput>make HAVE_KILL=yes HAVE_SLN=yes install -
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 -
general.ent
r90b56f5 raabd480 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 <!ENTITY version "TESTING-20050 630">3 <!ENTITY releasedate "Ju ne 30, 2005">2 <!ENTITY version "TESTING-20050701"> 3 <!ENTITY releasedate "July 1, 2005"> 4 4 <!ENTITY milestone "6.1"> 5 5 <!ENTITY generic-version "testing"> <!-- Use "svn", "testing", or "x.y[-pre{x}]" -->
Note:
See TracChangeset
for help on using the changeset viewer.