gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-09 15:39:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge r5317 and 5318 (wording and tagging corrections) to the testing branch

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@5319 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-05-12 22:07:33 +00:00
parent e750af101f
commit afbe6d98ba
6 changed files with 32 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
chapter01/changelog.xml
View File

@ -12,8 +12,8 @@
version is probably already available. To find out, please check one of the
mirrors via <ulink url="&lfs-root;"/>.</para>
<para>Below is a list of changes made since the previous release of the book,
first a summary, then a detailed log.</para>
<para>Below is a list of changes made since the previous release of the book.
First a summary, then a detailed log.</para>
<itemizedlist>
@ -83,6 +83,12 @@ first a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>May 12th, 2005 [matt]: More wording and tagging improvements
(thanks to Peter Ennis and Tony Morgan)</para></listitem>
<listitem><para>May 12th, 2005 [matt]: Minor wording improvements (thanks to
Peter Ennis)</para></listitem>
<listitem><para>April 27th, 2005 [archaic]: Added a patch to fix 2 glibc
testsuite failures when the running kernel is 2.6.11.x.</para></listitem>
@ -132,7 +138,7 @@ Kadzban)</para></listitem>
creates it (Ken Moffat). Also minor rewording to improve consistency.</para>
</listitem>
<listitem><para>April 4, 2005 [matt]: Fix E2fsprogs compile problem (Ken Moffat
<listitem><para>April 4, 2005 [matt]: Fix e2fsprogs compile problem (Ken Moffat
&amp; Greg Schafer)</para></listitem>
<listitem><para>April 2, 2005 [jhuntwork]: Fixed dtd url for sysklogd xml files</para></listitem>
@ -192,7 +198,7 @@ descriptions in a somewhat more alphabetic order.</para></listitem>
<listitem><para>March 14, 2005 [matt]: Upgraded to gettext-0.14.3</para>
</listitem>
<listitem><para>March 14, 2005 [jim]: Added /var/log/hotplug for capturing
<listitem><para>March 14, 2005 [jim]: Added <filename class="directory">/var/log/hotplug</filename> for capturing
of hotplug events. Added /lib/firmware for firmware loading with hotplug</para></listitem>
<listitem><para>March 13, 2005 [jim]: Updated iproute2 db patch to iproute2-2.6.11-050310. Removed
@ -238,8 +244,8 @@ bug 1047. Thanks to Steve Crosby for the suggested explanatory text.</para>
<listitem><para>February 28, 2005 [matt]: Upgraded binutils to 2.14.94.0.2.2
</para></listitem>
<listitem><para>February 28, 2005 [matt]: Move /usr/bin/logger to /bin
as the bootscripts need it there. Fixes bug 1035.</para>
<listitem><para>February 28, 2005 [matt]: Move <filename>/usr/bin/logger</filename>
to <filename class="directory">/bin</filename> as the bootscripts need it there. Fixes bug 1035.</para>
</listitem>
<listitem><para>February 28, 2005 [matt]: Upgraded to iana-etc-1.04</para>
@ -274,7 +280,7 @@ class="directory">/tools</filename>. This directory is not created
anymore.</para></listitem>
<listitem><para>February 19, 2005 [jeremy]: Added correction to chapter 5
glibc build to correct the disabling of selinux functionality. Thanks to
glibc build to fix the disabling of selinux functionality. Thanks to
Bobson on IRC (bobson@bobson.net) for pointing this out. Closes bugzilla
1034.</para></listitem>
@ -359,7 +365,7 @@ should fix the TLS strip issue that's been seen, at least on X86</para></listite
<listitem><para>December 22, 2004 [manuel]: Readded to chapter09/reboot.xml a para lost
from version 5.1.</para></listitem>
<listitem><para>December 20, 2004 [manuel]: Made Grub's configuration location
<listitem><para>December 20, 2004 [manuel]: Made grub's configuration location
FHS compliant.</para></listitem>
<listitem><para>December 19, 2004 [manuel]: Added the irc.lfs-matrix.de IRC server.</para></listitem>

9
chapter02/creatingfilesystem.xml
View File

@ -9,9 +9,9 @@
<para>Now that a blank partition has been set up, the file system can
be created. The most widely-used system in the Linux world is the
second extended file system (ext2), but with the newer high-capacity
hard disks, the journaling file systems are becoming increasingly
popular. Here we will create an ext2 file system, but build
second extended file system (ext2), but with newer high-capacity
hard disks, journaling file systems are becoming increasingly
popular. We will create an ext2 file system, however build
instructions for other file systems can be found at <ulink
url="&blfs-root;view/svn/postlfs/filesystems.html"><phrase
condition="pdf">&blfs-root;view/svn/ postlfs/filesystems.html</phrase></ulink>.</para>
@ -51,8 +51,7 @@ rm -rf e2fsprogs-&e2fsprogs-version;</userinput></screen>
</note>
<para>If a swap partition was created, it will need to be initialized
as a swap partition too (also known as formatting, as described above
with <command>mke2fs</command>) by running the following. If you are using an existing
as a swap partition by using the command below. If you are using an existing
swap partition, there is no need to format it.</para>
<screen><userinput>mkswap /dev/<replaceable>[yyy]</replaceable></userinput></screen>

20
chapter02/creatingpartition.xml
View File

@ -7,11 +7,10 @@
<title>Creating a New Partition</title>
<?dbhtml filename="creatingpartition.html"?>
<!--Edit Me-->
<para>Like most other operating systems, LFS is usually installed on
a dedicated partition. If you have an empty partition or enough
unpartitioned space on one of your hard disks to make one, using this
for your LFS installation is recommended. However, an LFS system (in
a dedicated partition. The recommended approach to building an LFS
system is to use an available empty partition or, if you have enough
unpartitioned space, to create one. However, an LFS system (in
fact even multiple LFS systems) may also be installed on a partition
already occupied by another operating system and the different systems
will co-exist peacefully. The document
@ -19,25 +18,24 @@ will co-exist peacefully. The document
condition="pdf">&hints-root;lfs_next_to_existing_ systems.txt</phrase></ulink>
explains how to implement this, whereas this book discusses the method of
using a fresh partition for the installation.</para>
<!--End Edit Me-->
<para>A minimal system requires a partition of around 1.3 gigabytes
(GB). This is enough to store all the source tarballs and compile
the packages. However, if the LFS system is intended to be the primary
Linux system, additional software will probably be installed which
will require additional space (2 or 3 GB). The LFS system itself will
not take up this much space. A large portion of this required amount
of space is to provide sufficient free temporary space. Compiling
not take up this much room. A large portion of this requirement
is to provide sufficient free temporary storage. Compiling
packages can require a lot of disk space which will be reclaimed after
the package is installed.</para>
<para>Because there is not always enough Random Access Memory (RAM)
available for compilation processes, it is a good idea to use a small
disk partition as swap space. This space is used by the kernel to
store seldom-used data to make room in memory for active processes.
disk partition as swap space. This is used by the kernel to
store seldom-used data and leave more memory available for active processes.
The swap partition for an LFS system can be the same as the one used
by the host system, so another swap partition will not need to be
created if your host system already has one setup.</para>
by the host system, in which case it is not necessary to create another
one.</para>
<para>Start a disk partitioning program such as
<command>cfdisk</command> or <command>fdisk</command> with a command

2
chapter05/glibc.xml
View File

@ -144,7 +144,7 @@ command will do so:</para>
<para>For a discussion of test failures that are of particular
importance, please see <xref linkend="ch-system-glibc" role="."/></para>
<para>In this chapter, some tests can be adversely effected by
<para>In this chapter, some tests can be adversely affected by
existing tools or environmental issues on the host system. Glibc test
suite failures in this chapter are typically not worrisome. The Glibc
installed in <xref linkend="chapter-building-system"/> is the one that

4
chapter05/toolchaintechnotes.xml
View File

@ -66,7 +66,7 @@ search path ensures programs are linked only against chosen
libraries</para></listitem>
<listitem><para>Careful manipulation of <command>gcc</command>'s
<filename>specs</filename> file tell the compiler which target dynamic
<filename>specs</filename> file tells the compiler which target dynamic
linker will be used</para></listitem>
</itemizedlist>
@ -77,7 +77,7 @@ software features to enable or disable. This is more important than
one might first realize. An incorrectly configured GCC or Glibc can
result in a subtly broken toolchain, where the impact of such breakage
might not show up until near the end of the build of an entire
distribution. A test suite failure will usually alert this error
distribution. A test suite failure will usually highlight this error
before too much additional work is performed.</para>
<beginpage/>

4
general.ent
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "TESTING-20050428">
<!ENTITY releasedate "April 28, 2005">
<!ENTITY version "TESTING-20050512">
<!ENTITY releasedate "May 12, 2005">
<!ENTITY milestone "6.1">
<!ENTITY lfs-root "http://www.linuxfromscratch.org/">