- Timestamp:
- 07/01/2005 11:16:14 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- 808f5af
- Parents:
- 90b56f5
- Location:
- chapter06
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
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
Note:
See TracChangeset
for help on using the changeset viewer.