Changeset fde4f7d


Ignore:
Timestamp:
07/01/2005 08:39:25 PM (19 years ago)
Author:
Archaic <archaic@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
d001e2b
Parents:
4d938ef
Message:

Brought all occurences of LFS-Bootscripts into conformity.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6288 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
13 edited

Legend:

Unmodified
Added
Removed

  • appendixb/acknowledgments.xml

    r4d938ef rfde4f7d  
    3636
    3737<listitem><para><ulink url="mailto:nathan@linuxfromscratch.org">Nathan
    38 Coulson</ulink> &lt;nathan@linuxfromscratch.org&gt; &ndash; LFS bootscripts
     38Coulson</ulink> &lt;nathan@linuxfromscratch.org&gt; &ndash; LFS-Bootscripts
    3939maintainer</para></listitem>
    4040
    … …  
    9191<listitem><para><ulink url="mailto:jeremy@linuxfromscratch.org">Jeremy
    9292Utley</ulink> &lt;jeremy@linuxfromscratch.org&gt; &ndash; LFS Technical
    93 Writer, Bugzilla maintainer, LFS bootscripts maintainer, LFS Server
     93Writer, Bugzilla maintainer, LFS-Bootscripts maintainer, LFS Server
    9494co-administrator</para></listitem>
    9595

  • chapter01/changelog.xml

    r4d938ef rfde4f7d  
    9292</listitem>
    9393
     94<listitem><para>July  1st, 2005 [archaic]: Brought all occurences of
     95LFS-Bootscripts into conformity.</para></listitem>
     96
    9497<listitem><para>June 30th, 2005 [archaic]: Several minor wording changes in
    9598chapter 6 (matt).</para></listitem>

  • chapter01/how.xml

    r4d938ef rfde4f7d  
    7272computer as normal.</para>
    7373
    74 <para>To finish the installation, the bootscripts are set up in <xref
     74<para>To finish the installation, the LFS-Bootscripts are set up in <xref
    7575linkend="chapter-bootscripts"/>, and the kernel and boot loader are set
    7676up in <xref linkend="chapter-bootable"/>. <xref

  • chapter06/devices.xml

    r4d938ef rfde4f7d  
    3131be created dynamically on that virtual filesystem as they are detected or
    3232accessed. 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 otherwise
    34 do by mounting <filename class="directory">/dev</filename>:</para>
     33has not been booted, it is necessary to do what the LFS-Bootscripts package would
     34otherwise do by mounting <filename class="directory">/dev</filename>:</para>
    3535
    3636<screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
    … …  
    5252
    5353<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 and
    55 not a booted environment, those symlinks and directories need to be created
    56 here:</para>
     54during system startup by the LFS-Bootscripts package. Since this is a chroot
     55environment and not a booted environment, those symlinks and directories need to
     56be created here:</para>
    5757
    5858<screen><userinput>ln -s /proc/self/fd /dev/fd

  • chapter06/hotplug.xml

    r4d938ef rfde4f7d  
    4343<screen><userinput>cp etc/hotplug/pnp.distmap /etc/hotplug</userinput></screen>
    4444
    45 <para>Remove the init script that Hotplug installs, since we're going to be
    46 using the script included with LFS-Bootscripts:</para>
     45<para>Remove the init script that Hotplug installs since we are going to be
     46using the script included in the LFS-Bootscripts package:</para>
    4747
    4848<screen><userinput>rm -rf /etc/init.d</userinput></screen>
    4949
    50 <para>Network device hotplugging is not supported by LFS-Bootscripts yet. For
    51 that reason, remove the network hotplug agent:</para>
     50<para>Network device hotplugging is not yet supported by the LFS-Bootscripts
     51package. For that reason, remove the network hotplug agent:</para>
    5252
    5353<screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
    … …  
    9292<listitem>
    9393<para>These scripts are used for cold plugging, i.e., detecting and acting upon
    94 hardware already present during system startup.  They are called by the
    95 <filename>hotplug</filename> initscript that comes from the LFS-Bootscripts
    96 package.  The <command>*.rc</command> scripts try to recover hotplug events that
    97 were lost during system boot because, for example, the root filesystem was not
    98 mounted by the kernel</para>
     94hardware already present during system startup. They are called by the
     95<filename>hotplug</filename> initscript included in the LFS-Bootscripts package.
     96The <command>*.rc</command> scripts try to recover hotplug events that were lost
     97during system boot because, for example, the root filesystem was not mounted by
     98the kernel</para>
    9999<indexterm zone="ch-system-hotplug hotplug-rc"><primary
    100100sortas="d-/etc/hotplug/*.rc">/etc/hotplug/*.rc</primary></indexterm>

  • chapter06/iproute2.xml

    r4d938ef rfde4f7d  
    5757    <varlistentry>
    5858    <term><parameter>SBINDIR=/sbin</parameter></term>
    59     <listitem><para>This makes sure that the IPRoute2 binaries will install into
    60       <filename class="directory">/sbin</filename>.  This is the correct
    61       location according to the FHS, because some of the IPRoute2 binaries are used
    62       in the bootscripts.</para>
     59    <listitem><para>This ensures that the IPRoute2 binaries will install into
     60      <filename class="directory">/sbin</filename>. This is the correct location
     61      according to the FHS, because some of the IPRoute2 binaries are used by
     62      the LFS-Bootscripts package.</para>
    6363    </listitem>
    6464    </varlistentry>

  • chapter06/psmisc.xml

    r4d938ef rfde4f7d  
    4141<varlistentry>
    4242<term><parameter>--exec-prefix=""</parameter></term>
    43 <listitem><para>This causes the binaries to be installed in <filename
    44 class="directory">/bin</filename> instead of <filename
    45 class="directory">/usr/bin</filename>. Because the Psmisc programs are
    46 often used in bootscripts, they should be available when the <filename
    47 class="directory">/usr</filename> file system is not
    48 mounted.</para></listitem>
     43<listitem><para>This ensures that the Psmisc binaries will install into
     44<filename class="directory">/bin</filename> instead of <filename
     45class="directory">/usr/bin</filename>. This is the correct location according to
     46the FHS, because some of the Psmisc binaries are used by the LFS-Bootscripts
     47package.</para></listitem>
    4948</varlistentry>
    5049</variablelist>

  • chapter06/util-linux.xml

    r4d938ef rfde4f7d  
    8383
    8484<para>Install the package and move the <command>logger</command> binary to
    85 <filename class="directory">/bin</filename> as it is needed by the bootscripts:
    86 </para>
     85<filename class="directory">/bin</filename> as it is needed by the
     86LFS-Bootscripts package:</para>
    8787
    8888<screen><userinput>make HAVE_KILL=yes HAVE_SLN=yes install

  • chapter07/bootscripts.xml

    r4d938ef rfde4f7d  
    1111
    1212<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
     14LFS system at bootup/shutdown.</para>
    1415
    1516<segmentedlist>
    … …  
    3435</sect2>
    3536
    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>
    3738
    3839<segmentedlist>

  • chapter07/introduction.xml

    r4d938ef rfde4f7d  
    88<?dbhtml filename="introduction.html"?>
    99
    10 <para>This chapter details how to install the bootscripts and set them up
    11 properly. Most of these scripts will work without modification, but a
    12 few require additional configuration files because they deal with
    13 hardware-dependent information.</para>
     10<para>This chapter details how to install and configure the LFS-Bootscripts
     11package. Most of these scripts will work without modification, but a few require
     12additional configuration files because they deal with hardware-dependent
     13information.</para>
    1414
    1515<para>System-V style init scripts are employed in this book because they are

  • chapter07/network.xml

    r4d938ef rfde4f7d  
    5555network script and not brought up.</para>
    5656
    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">/etc/sysconfig/network-devices/services</filename>
    61 directory allows other IP assignment methods. This is commonly used
    62 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
     58address. The LFS-Bootscripts package has a modular IP assignment format, and
     59creating additional files in the <filename
     60class="directory">/etc/sysconfig/network-devices/services</filename> directory
     61allows other IP assignment methods. This is commonly used for Dynamic Host
     62Configuration Protocol (DHCP), which is addressed in the BLFS book.</para>
    6363
    6464<para>The <envar>GATEWAY</envar> variable should contain

  • chapter07/udev.xml

    r4d938ef rfde4f7d  
    8383processes and to <command>udev</command> for device node creation.</para>
    8484
    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
     86device 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
     91class="filesystem">/sys</systemitem> filesystem and creates devices under
     92<filename class="directory">/dev</filename> that match the descriptions.  For
     93example, <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
     97the <filename class="directory">/dev</filename> directory are configured
     98according to the rules specified in the files within the <filename
     99class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in
     100a similar fashion to the LFS-Bootscripts package. If <command>udev</command>
     101can'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>
    106103
    107104<para>Once the above stage is complete, all devices that were already

  • general.ent

    r4d938ef rfde4f7d  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!ENTITY version "SVN-20050630">
    3 <!ENTITY releasedate "June 30, 2005">
     2<!ENTITY version "SVN-20050601">
     3<!ENTITY releasedate "July 01, 2005">
    44<!ENTITY milestone "6.2">
    55<!ENTITY generic-version "svn"> <!-- Use "svn", "testing", or "x.y[-pre{x}]" -->
Note: See TracChangeset for help on using the changeset viewer.