gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-27 15:49:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Several minor wording changes in chapter 6 (matt).

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6249 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Archaic 2005-06-30 14:49:44 +00:00
parent e9e4abc031
commit 2645ec62a3
8 changed files with 56 additions and 57 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter01/changelog.xml
View File

@ -91,6 +91,9 @@ First a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>June 30th, 2005 [archaic]: Several minor wording changes in
chapter 6 (matt).</para></listitem>
<listitem><para>June 29th, 2005 [archaic]: Several minor wording changes in
chapters 1 - 5 (matt).</para></listitem>

12
chapter06/chroot.xml
View File

@ -37,12 +37,12 @@ restricted to the LFS file system. This is because the Bash shell is
told that <filename class="directory">$LFS</filename> is now the root
(<filename class="directory">/</filename>) directory.</para>
<para>Notice that <filename class="directory">/tools/bin</filename>
comes last in the <envar>PATH</envar>. This means that a
temporary tool will not be used anymore as soon as its final version
is installed. This occurs when the shell does not <quote>remember</quote> the
locations of executed binaries&mdash;for this reason, hashing is switched
off by passing the <parameter>+h</parameter> option to <command>bash</command>.</para>
<para>Notice that <filename class="directory">/tools/bin</filename> comes last
in the <envar>PATH</envar>. This means that a temporary tool will no longer be
used once its final version is installed. This occurs when the shell does not
<quote>remember</quote> the locations of executed binaries&mdash;for this
reason, hashing is switched off by passing the <parameter>+h</parameter> option
to <command>bash</command>.</para>
<para>It is important that all the commands throughout the remainder
of this chapter and the following chapters are run from within the

8
chapter06/createfiles.xml
View File

@ -7,10 +7,10 @@
<title>Creating Essential Symlinks</title>
<?dbhtml filename="createfiles.html"?>
<para>Some programs use hard-wired paths to programs which do not yet
exist. In order to satisfy these programs, create a number of symbolic
links which will be replaced by real files throughout the course of
this chapter after the software has been installed.</para>
<para>Some programs use hard-wired paths to programs which do not exist yet. In
order to satisfy these programs, create a number of symbolic links which will be
replaced by real files throughout the course of this chapter after the software
has been installed.</para>
<screen><userinput>ln -s /tools/bin/{bash,cat,pwd,stty} /bin
ln -s /tools/bin/perl /usr/bin

17
chapter06/creatingdirs.xml
View File

@ -49,16 +49,15 @@ bit mask.</para>
<sect2>
<title>FHS Compliance Note</title>
<para>The directory tree is based on the Filesystem Hierarchy Standard
(FHS) standard (available at <ulink
url="http://www.pathname.com/fhs/"/>). Besides the tree created above,
this standard stipulates the existence of <filename
<para>The directory tree is based on the Filesystem Hierarchy Standard (FHS)
(available at <ulink url="http://www.pathname.com/fhs/"/>). In addition
to the tree created above, this standard stipulates the existence of <filename
class="directory">/usr/local/games</filename> and <filename
class="directory">/usr/share/games</filename>. We do not recommend
these for a base system, however, feel free to make the system
FHS-compliant. The FHS is not precise as to the structure of the
<filename class="directory">/usr/local/share</filename> subdirectory,
so we created only the directories that are needed.</para>
class="directory">/usr/share/games</filename>. The FHS is not precise as to the
structure of the <filename class="directory">/usr/local/share</filename>
subdirectory, so we create only the directories that are needed. However, feel
free to create these directories if you prefer to conform more strictly to the
FHS standard.</para>
</sect2>

17
chapter06/glibc.xml
View File

@ -110,8 +110,9 @@ Certain optimization settings are also known to be a factor here.</para></listit
host system issues. The exact reasons are not yet clear.</para></listitem>
<listitem><para>If you have mounted the LFS partition with the
<parameter>noatime</parameter> option, the <emphasis>atime</emphasis>
test will fail. This is not critical.</para></listitem>
<parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test will
fail. As mentioned in <xref linkend="space-mounting"/>, do not use the
<parameter>noatime</parameter> option while building LFS.</para></listitem>
<listitem><para>When running on older and slower hardware, some tests
can fail because of test timeouts being exceeded.</para></listitem>
@ -189,10 +190,10 @@ on the threading API (applicable to NPTL as well):</para>
<indexterm zone="conf-glibc"><primary sortas="e-/etc/nsswitch.conf">/etc/nsswitch.conf</primary></indexterm>
<indexterm zone="conf-glibc"><primary sortas="e-/etc/localtime">/etc/localtime</primary></indexterm>
<para>The <filename>/etc/nsswitch.conf</filename> file needs to be
created because, although Glibc provides defaults when this file is
missing or corrupt, the Glibc defaults do not work well with
networking. The time zone also needs to be set up.</para>
<para>The <filename>/etc/nsswitch.conf</filename> file needs to be created
because, although Glibc provides defaults when this file is missing or corrupt,
the Glibc defaults do not work well in a networked environment. The time zone
also needs to be configured.</para>
<para>Create a new file <filename>/etc/nsswitch.conf</filename> by running the
following:</para>
@ -228,8 +229,8 @@ running:</para>
<screen><userinput>cp --remove-destination /usr/share/zoneinfo/<replaceable>[xxx]</replaceable> \
/etc/localtime</userinput></screen>
<para>Replace <replaceable>[xxx]</replaceable> with the name of the time zone that the
<command>tzselect</command> provided (e.g., Canada/Eastern).</para>
<para>Replace <replaceable>[xxx]</replaceable> with the name of the time zone
that <command>tzselect</command> provided (e.g., Canada/Eastern).</para>
<para>The meaning of the cp option:</para>

6
chapter06/kernfs.xml
View File

@ -7,9 +7,9 @@
<title>Mounting Virtual Kernel File Systems</title>
<?dbhtml filename="kernfs.html"?>
<para>Various file systems exported by the kernel do not exist on the
hard drive, but are used to communicate to and from the kernel
itself.</para>
<para>Various file systems exported by the kernel are used to communicate to and
from the kernel itself. These file systems are virtual in that no disk space is
used for them. The contents of the file systems resides in memory.</para>
<para>Begin by creating directories onto which the file systems will be mounted:</para>

17
chapter06/pwdgroup.xml
View File

@ -50,15 +50,14 @@ utmp:x:13:
usb:x:14:</literal>
EOF</userinput></screen>
<para>The created groups are not part of any standard&mdash;they are some
of the groups that the Udev configuration will be using in the next
section. The Linux Standard Base (LSB, available at <ulink
url="http://www.linuxbase.org"/>) recommends only that, besides the
group <quote>root</quote> with a Group ID (GID) of 0, a group
<quote>bin</quote> with a GID of 1 be present. All other group names
and GIDs can be chosen freely by the system administrator since
well-written packages do not depend on GID numbers, but rather use the
group's name.</para>
<para>The created groups are not part of any standard&mdash;they are some of the
groups that the Udev configuration will use in the next section. The Linux
Standard Base (LSB, available at <ulink url="http://www.linuxbase.org"/>)
recommends only that, besides the group <quote>root</quote> with a Group ID
(GID) of 0, a group <quote>bin</quote> with a GID of 1 be present. All other
group names and GIDs can be chosen freely by the system administrator since
well-written packages do not depend on GID numbers, but rather use the group's
name.</para>
<para>To remove the <quote>I have no name!</quote> prompt, start a new
shell. Since a full Glibc was installed in <xref

33
chapter06/readjusting.xml
View File

@ -7,25 +7,22 @@
<title>Re-adjusting the Toolchain</title>
<?dbhtml filename="readjusting.html"?>
<para>Now that the new and final C libraries have been installed, it
is time to adjust the toolchain again. The toolchain will be adjusted
so that it will link any newly compiled program against these new
libraries. This is the same process used in the
<quote>Adjusting</quote> phase in the beginning of <xref
linkend="chapter-temporary-tools"/>, even though it looks to be
reversed. In <xref linkend="chapter-temporary-tools"/>, the chain was
guided from the host's <filename
class="directory">/{,usr/}lib</filename> directories to the new
<filename class="directory">/tools/lib</filename> directory. Now, the
chain will be guided from that same <filename
class="directory">/tools/lib</filename> directory to the LFS
<filename class="directory">/{,usr/}lib</filename> directories.</para>
<para>Now that the final C libraries have been installed, it is time to adjust
the toolchain again. The toolchain will be adjusted so that it will link any
newly compiled program against these new libraries. This is the same process
used in the <quote>Adjusting</quote> phase in the beginning of <xref
linkend="chapter-temporary-tools"/>, but with the adjustments reversed. In <xref
linkend="chapter-temporary-tools"/>, the chain was guided from the host's
<filename class="directory">/{,usr/}lib</filename> directories to the new
<filename class="directory">/tools/lib</filename> directory. Now, the chain will
be guided from that same <filename class="directory">/tools/lib</filename>
directory to the LFS <filename class="directory">/{,usr/}lib</filename>
directories.</para>
<para>Start by adjusting the linker. The source and build directories
from the second pass over Binutils were retained for this purpose.
Install the adjusted linker by running the following command from
within the <filename class="directory">binutils-build</filename>
directory:</para>
<para>Start by adjusting the linker. The source and build directories from the
second pass of Binutils were retained for this purpose. Install the adjusted
linker by running the following command from within the <filename
class="directory">binutils-build</filename> directory:</para>
<screen><userinput>make -C ld INSTALL=/tools/bin/install install</userinput></screen>