- Timestamp:
- 10/01/2022 08:03:20 AM (2 years ago)
- 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. - Location:
- chapter07
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/creatingdirs.xml
r259794e rdd61c77 11 11 <title>Creating Directories</title> 12 12 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> 14 14 15 <note><para>Some of the directories mentioned in this section may be16 already created earlier with explicit instructionsor when installing some15 <note><para>Some of the directories mentioned in this section may have 16 already been created earlier with explicit instructions, or when installing some 17 17 packages. They are repeated below for completeness.</para></note> 18 18 … … 43 43 44 44 <para>Directories are, by default, created with permission mode 755, but 45 this is not desirable for all directories. In the commands above, two45 this is not desirable everywhere. In the commands above, two 46 46 changes are made—one to the home directory of user <systemitem 47 47 class="username">root</systemitem>, and another to the directories for … … 49 49 50 50 <para>The first mode change ensures that not just anybody can enter 51 the <filename class="directory">/root</filename> directory— the52 same as a normal user would do with his or herhome directory. The51 the <filename class="directory">/root</filename> directory—just 52 like a normal user would do with his or her own home directory. The 53 53 second mode change makes sure that any user can write to the 54 54 <filename class="directory">/tmp</filename> and <filename … … 60 60 <title>FHS Compliance Note</title> 61 61 62 <para>Th edirectory tree is based on the Filesystem Hierarchy Standard62 <para>This directory tree is based on the Filesystem Hierarchy Standard 63 63 (FHS) (available at <ulink 64 64 url="https://refspecs.linuxfoundation.org/fhs.shtml"/>). The FHS also specifies 65 the optional existence of somedirectories such as <filename65 the optional existence of additional directories such as <filename 66 66 class="directory">/usr/local/games</filename> and <filename 67 class="directory">/usr/share/games</filename>. We create only the68 directories that are needed. However, feel free to create these69 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> 70 70 71 71 </sect2> -
chapter07/introduction.xml
r259794e rdd61c77 21 21 22 22 <para>This chapter shows how to build the last missing bits of the temporary 23 system: the tools needed by the build machinery ofvarious packages. Now23 system: the tools needed to build the various packages. Now 24 24 that all circular dependencies have been resolved and the temporary system 25 25 is already bootable, we can boot it on the target machine and it would be … … 29 29 <para>For proper operation of the temporary system, some communication 30 30 with the running kernel must be established. This is done through the 31 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which mustbe31 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be 32 32 mounted as soon as possible after boot. You may want to check 33 33 that they are mounted by issuing <command>mount</command>.</para> … … 36 36 target system, fortunately without access to the host system. 37 37 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 bad ly39 formedcommands.</para>38 contain some important data, it's possible to destroy them with bad 39 commands.</para> 40 40 41 41 </sect1> -
chapter07/kernfs.xml
r259794e rdd61c77 15 15 </indexterm> 16 16 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 19 20 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> 21 23 22 <para>Begin by creating directories on towhich the file systems will be24 <para>Begin by creating directories on which the file systems will be 23 25 mounted:</para> 24 26
Note:
See TracChangeset
for help on using the changeset viewer.