Changeset 387a32af


Ignore:
Timestamp:
06/11/2020 03:13:43 AM (16 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, ml-11.0, multilib, trunk, xry111/git-transition, xry111/glibc-2.34, xry111/tester-nohack, xry111/usr-move
Children:
aefc822
Parents:
bc8cca5
Message:

Update initial Chapter 7 pages for cross2 branch

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11918 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
8 edited

Legend:

Unmodified
Added
Removed
  • chapter07/changingowner.xml

    rbc8cca5 r387a32af  
    2929  these files to possible malicious manipulation.</para>
    3030
    31   <para>To avoid this issue, you could add the <systemitem
    32   class="username">lfs</systemitem> user to the new LFS system later when
    33   creating the <filename>/etc/passwd</filename> file, taking care to assign it
    34   the same user and group IDs as on the host system. Better yet, change the
     31  <para>To address this issue, change the
    3532  ownership of the <filename class="directory">$LFS/*</filename> directories to
    3633  user <systemitem class="username">root</systemitem> by running the following
  • chapter07/chroot.xml

    rbc8cca5 r387a32af  
    1111  <title>Entering the Chroot Environment</title>
    1212
    13   <para>Now that all the packages which depend on themselves for being built
    14   are on the system, it is time to enter the chroot environment to finish
    15   installing the remaining temporary tools. This environment will be in use
    16   also for installing the final system. As user <systemitem
     13  <para>Now that all the packages which are required to build the rest of the
     14  needed tools are on the system, it is time to enter the chroot environment to
     15  finish installing the remaining temporary tools. This environment will be in
     16  use also for installing the final system. As user <systemitem
    1717  class="username">root</systemitem>, run the following command to enter the
    18   realm that is, at the moment, populated with only the temporary tools:</para>
     18  environment that is, at the moment, populated with only the temporary
     19  tools:</para>
    1920
    20 <screen role="nodump"><userinput>chroot "$LFS" /usr/bin/env -i \
     21<screen role="nodump"><userinput>chroot "$LFS" /usr/bin/env -i   \
    2122    HOME=/root                  \
    2223    TERM="$TERM"                \
     
    3233  variable inside chroot to the same value as outside chroot. This variable is
    3334  needed for programs like <command>vim</command> and <command>less</command>
    34   to operate properly.  If other variables are needed, such as
     35  to operate properly.  If other variables are desired, such as
    3536  <envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>, this is a good place to set
    3637  them again.</para>
    3738
    3839  <para>From this point on, there is no need to use the
    39   <envar>LFS</envar> variable anymore, because all work will be restricted
     40  <envar>LFS</envar> variable anymore because all work will be restricted
    4041  to the LFS file system.  This is because the Bash shell is told that
    4142  <filename class="directory">$LFS</filename> is now the root
     
    4344
    4445  <para>Notice that <filename class="directory">/tools/bin</filename> is not
    45   anymore in the <envar>PATH</envar>. This means that a temporary tool will no longer be
     46  in the <envar>PATH</envar>. This means that a temporary tool will no longer be
    4647  used once its final version is installed. This occurs when the shell does not
    4748  <quote>remember</quote> the locations of executed binaries&mdash;for this
  • chapter07/createfiles.xml

    rbc8cca5 r387a32af  
    7777
    7878  <para>The actual password for <systemitem class="username">root</systemitem>
    79   (the <quote>x</quote> used here is just a placeholder) will be set later.</para>
     79  will be set later.</para>
    8080
    8181  <para>Create the <filename>/etc/group</filename> file by running the following
     
    146146
    147147  <para>The created groups are not part of any standard&mdash;they are groups
    148   decided on in part by the requirements of the Udev configuration in the next
    149   chapter, and in part by common convention employed by a number of existing
    150   Linux distributions. In addition, some test suites rely on specific users
    151   or groups.  The Linux Standard Base (LSB, available at <ulink
    152   url="http://www.linuxbase.org"/>) recommends only that, besides the group
    153   <systemitem class="groupname">root</systemitem> with a Group ID (GID) of 0,
    154   a group <systemitem class="groupname">bin</systemitem> with a GID of 1 be
    155   present. All other group names and GIDs can be chosen freely by the system
    156   administrator since well-written programs do not depend on GID numbers, but
    157   rather use the group's name.</para>
     148  decided on in part by the requirements of the Udev configuration in Chapter
     149  9, and in part by common convention employed by a number of existing Linux
     150  distributions. In addition, some test suites rely on specific users or
     151  groups.  The Linux Standard Base (LSB, available at <ulink
     152  url="http://refspecs.linuxfoundation.org/lsb.shtml"/>) only recommends that,
     153  besides the group <systemitem class="groupname">root</systemitem> with a
     154  Group ID (GID) of 0, a group <systemitem class="groupname">bin</systemitem>
     155  with a GID of 1 be present. All other group names and GIDs can be chosen
     156  freely by the system administrator since well-written programs do not depend
     157  on GID numbers, but rather use the group's name.</para>
    158158
    159159  <para>Some tests in <xref linkend="chapter-building-system"/> need a regular
     
    178178  executed. To ensure the use of the newly compiled binaries as soon as they are
    179179  installed, the <parameter>+h</parameter> directive will be used for the duration
    180   of this chapter.</para>
     180  of this and the next chapter.</para>
    181181
    182182  <para>The <command>login</command>, <command>agetty</command>, and
  • chapter07/creatingdirs.xml

    rbc8cca5 r387a32af  
    1616<screen><userinput>mkdir -pv /{bin,boot,etc/{opt,sysconfig},home,lib/firmware,mnt,opt}
    1717mkdir -pv /{media/{floppy,cdrom},srv,var}
    18 install -dv -m 0750 /root
    19 install -dv -m 1777 /tmp /var/tmp
    2018mkdir -pv /usr/{,local/}{bin,include,lib,sbin,src}
    2119mkdir -pv /usr/{,local/}share/{color,dict,doc,info,locale,man}
    22 mkdir -pv  /usr/{,local/}share/{misc,terminfo,zoneinfo}
     20mkdir -pv /usr/{,local/}share/{misc,terminfo,zoneinfo}
    2321mkdir -pv /usr/{,local/}share/man/man{1..8}
     22install -dv -m 1777 /tmp /var/tmp
     23install -dv -m 0750 /root
    2424
    2525mkdir -v /var/{log,mail,spool}
  • chapter07/introduction.xml

    rbc8cca5 r387a32af  
    1111  <title>Introduction</title>
    1212
    13   <para>This chapter shows how to build the last missing bits of the
    14   temporary system: first, the tools needed by the build machinery of
    15   various packages, then three packages needed to run tests.
    16   Now that all circular dependencies have been resolved,
    17   we can use a <quote>chroot</quote> environment, completely isolated
    18   from the computer used for the build, except for the running kernel.</para>
     13  <para>This chapter shows how to build the last missing bits of the temporary
     14  system: first, the tools needed by the build machinery of various packages,
     15  then three packages needed to run tests.  Now that all circular dependencies
     16  have been resolved, we can use a <quote>chroot</quote> environment,
     17  completely isolated the host operating system used for the build, except
     18  for the running kernel.</para>
    1919
    2020  <para>For proper operation of the isolated environment, some communication
     
    2222  so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
    2323  mounted when entering the chroot environment. You may want to check
    24   that they are mounted by issuing <command>ls $LFS/dev</command>,
    25   <command>ls $LFS/proc</command>, or <command>ls $LFS/sys</command>.
    26   Note that mounting the virtual kernel file systems must be done
    27   <emphasis>each time you want to enter the chroot
    28   environment</emphasis>.</para>
     24  that they are mounted by issuing <command>findmnt</command>.</para>
    2925
    3026  <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
     
    3228  <envar>LFS</envar> variable set. After entering chroot, all commands
    3329  are run as root, fortunately without access to the OS of the computer
    34   you build LFS on. Be careful anyway, as it is easy to destroy the whole
     30  you built LFS on. Be careful anyway, as it is easy to destroy the whole
    3531  LFS system with badly formed commands.</para>
    3632
  • chapter07/kernfs.xml

    rbc8cca5 r387a32af  
    3131    device nodes, in particular the <filename
    3232    class="devicefile">console</filename> and <filename
    33     class="devicefile">null</filename> devices. The device nodes must be created
    34     on the hard disk so that they are available before <command>udevd</command>
    35     has been started, and additionally when Linux is started with
     33    class="devicefile">null</filename> devices. The device nodes must be
     34    created on the hard disk so that they are available before the kernel
     35    populates <systemitem class="filesystem">/dev</systemitem>), and
     36    additionally when Linux is started with
    3637    <parameter>init=/bin/bash</parameter>. Create the devices by running the
    3738    following commands:</para>
     
    7374mount -vt sysfs sysfs $LFS/sys
    7475mount -vt tmpfs tmpfs $LFS/run</userinput></screen>
    75 
     76<!--
    7677    <variablelist>
    7778      <title>The meaning of the mount options for devpts:</title>
     
    101102
    102103    </variablelist>
    103 
     104-->
    104105      <para>In some host systems, <filename>/dev/shm</filename> is a
    105106      symbolic link to <filename class="directory">/run/shm</filename>.
  • chapter08/grep.xml

    rbc8cca5 r387a32af  
    2424    <title/>
    2525
    26     <para>The Grep package contains programs for searching through teh contents of files.</para>
     26    <para>The Grep package contains programs for searching through the contents of files.</para>
    2727
    2828    <segmentedlist>
  • chapter08/make.xml

    rbc8cca5 r387a32af  
    2525
    2626    <para>The Make package contains a program for controlling the generation of
    27     executables and other non-source files of a program from the program's
    28     source files. .</para>
     27    executables and other non-source files of a package from source files.</para>
    2928
    3029    <segmentedlist>
Note: See TracChangeset for help on using the changeset viewer.