Changeset dd61c77 for chapter07


Ignore:
Timestamp:
10/01/2022 08:03:20 AM (2 years ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/clfs-ng
Children:
ef1f48b
Parents:
259794e (diff), 2bf32ff (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

Location:
chapter07
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • chapter07/creatingdirs.xml

    r259794e rdd61c77  
    1111  <title>Creating Directories</title>
    1212
    13   <para>It is time to create the full structure in the LFS file system.</para>
     13  <para>It is time to create the full directory structure in the LFS file system.</para>
    1414
    15   <note><para>Some of the directories mentioned in this section may be
    16   already created earlier with explicit instructions or when installing some
     15  <note><para>Some of the directories mentioned in this section may have
     16  already been created earlier with explicit instructions, or when installing some
    1717  packages.  They are repeated below for completeness.</para></note>
    1818
     
    4343
    4444  <para>Directories are, by default, created with permission mode 755, but
    45   this is not desirable for all directories. In the commands above, two
     45  this is not desirable everywhere. In the commands above, two
    4646  changes are made&mdash;one to the home directory of user <systemitem
    4747  class="username">root</systemitem>, and another to the directories for
     
    4949
    5050  <para>The first mode change ensures that not just anybody can enter
    51   the <filename class="directory">/root</filename> directory&mdash;the
    52   same as a normal user would do with his or her home directory. The
     51  the <filename class="directory">/root</filename> directory&mdash;just
     52  like a normal user would do with his or her own home directory. The
    5353  second mode change makes sure that any user can write to the
    5454  <filename class="directory">/tmp</filename> and <filename
     
    6060    <title>FHS Compliance Note</title>
    6161
    62     <para>The directory tree is based on the Filesystem Hierarchy Standard
     62    <para>This directory tree is based on the Filesystem Hierarchy Standard
    6363    (FHS) (available at <ulink
    6464    url="https://refspecs.linuxfoundation.org/fhs.shtml"/>).  The FHS also specifies
    65     the optional existence of some directories such as <filename
     65    the optional existence of additional directories such as <filename
    6666    class="directory">/usr/local/games</filename> and <filename
    67     class="directory">/usr/share/games</filename>.  We create only the
    68     directories that are needed. However, feel free to create these
    69     directories.  </para>
     67    class="directory">/usr/share/games</filename>.  In LFS, we create only the
     68    directories that are really necessary. However, feel free to create more
     69    directories, if you wish.  </para>
    7070
    7171  </sect2>
  • chapter07/introduction.xml

    r259794e rdd61c77  
    2121
    2222  <para>This chapter shows how to build the last missing bits of the temporary
    23   system: the tools needed by the build machinery of various packages.  Now
     23  system: the tools needed to build the various packages.  Now
    2424  that all circular dependencies have been resolved and the temporary system
    2525  is already bootable, we can boot it on the target machine and it would be
     
    2929  <para>For proper operation of the temporary system, some communication
    3030  with the running kernel must be established. This is done through the
    31   so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
     31  so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be
    3232  mounted as soon as possible after boot. You may want to check
    3333  that they are mounted by issuing <command>mount</command>.</para>
     
    3636  target system, fortunately without access to the host system.
    3737  Be careful anyway, as if the storage devices of your target system already
    38   contain some important data, it's possible to destroy them with badly
    39   formed commands.</para>
     38  contain some important data, it's possible to destroy them with bad
     39  commands.</para>
    4040
    4141</sect1>
  • chapter07/kernfs.xml

    r259794e rdd61c77  
    1515  </indexterm>
    1616
    17     <para>Various file systems exported by the kernel are used to communicate to
    18     and from the kernel itself. These file systems are virtual in that no disk
     17    <para>Applications running in user space utilize various file
     18    systems exported by the kernel to communicate
     19    with the kernel itself. These file systems are virtual: no disk
    1920    space is used for them. The content of the file systems resides in
    20     memory.</para>
     21    memory. These file systems must be mounted in the $LFS directory tree
     22    so the applications can find them in the chroot environment.</para>
    2123
    22     <para>Begin by creating directories onto which the file systems will be
     24    <para>Begin by creating directories on which the file systems will be
    2325    mounted:</para>
    2426
Note: See TracChangeset for help on using the changeset viewer.