Author: jim
Date: 2006-07-09 13:49:01 -0600 (Sun, 09 Jul 2006)
New Revision: 1955
Modified:
/
branches/clfs-2.0/BOOK/appendices/dependencies/common.xml
branches/clfs-2.0/BOOK/bootable/arm-chapter.xml
branches/clfs-2.0/BOOK/bootable/arm/kernel.xml
branches/clfs-2.0/BOOK/bootable/common/introduction.xml
branches/clfs-2.0/BOOK/bootscripts/common/introduction.xml
branches/clfs-2.0/BOOK/bootscripts/common/profile.xml
branches/clfs-2.0/BOOK/bootscripts/common/setclock.xml
branches/clfs-2.0/BOOK/bootscripts/common/udev.xml
branches/clfs-2.0/BOOK/bootscripts/common/usage.xml
branches/clfs-2.0/BOOK/cross-tools/common/glibc.xml
branches/clfs-2.0/BOOK/final-preps/creatingdirs.xml
branches/clfs-2.0/BOOK/final-preps/settingenviron.xml
branches/clfs-2.0/BOOK/final-system/common/e2fsprogs.xml
branches/clfs-2.0/BOOK/final-system/common/inetutils.xml
branches/clfs-2.0/BOOK/final-system/common/man.xml
branches/clfs-2.0/BOOK/final-system/common/pkgmgt.xml
branches/clfs-2.0/BOOK/final-system/common/vim.xml
branches/clfs-2.0/BOOK/introduction/common/askforhelp.xml
branches/clfs-2.0/BOOK/introduction/common/resources.xml
branches/clfs-2.0/BOOK/materials/common/patches.xml
branches/clfs-2.0/BOOK/partitioning/common/creatingfilesystem.xml
branches/clfs-2.0/BOOK/partitioning/common/creatingpartition.xml
branches/clfs-2.0/BOOK/partitioning/common/mounting.xml
branches/clfs-2.0/BOOK/the-end/reboot.xml
branches/clfs-2.0/BOOK/the-end/whatnow.xml
Log:
[EMAIL PROTECTED] (orig r2053): jciccone | 2006-07-09 12:29:55 -0700
LFS to CLFS changes.
Property changes on:
___________________________________________________________________
Name: svk:merge
- b6734a72-470d-0410-b049-f317dca95413:/:2052
+ b6734a72-470d-0410-b049-f317dca95413:/:2053
Modified: branches/clfs-2.0/BOOK/appendices/dependencies/common.xml
===================================================================
--- branches/clfs-2.0/BOOK/appendices/dependencies/common.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/appendices/dependencies/common.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -11,11 +11,11 @@
<title>Dependencies</title>
- <para>Every package built in LFS relies on one or more other packages
+ <para>Every package built in CLFS relies on one or more other packages
in order to build and install properly. Some packages even participate
in circular dependencies, that is, the first package depends on the second
which in turn depends on the first. Because of these dependencies, the
- order in which packages are built in LFS is very important. The purpose
+ order in which packages are built in CLFS is very important. The purpose
of this page is to document the dependencies of each package built in
LFS.</para>
<para>For each package we build, we have listed three types of dependencies.
Modified: branches/clfs-2.0/BOOK/bootable/arm/kernel.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootable/arm/kernel.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/bootable/arm/kernel.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -50,7 +50,7 @@
Please note that the udev bootscript requires "rtc" and "tmpfs" to be
enabled and built into the kernel, not as modules. BLFS has
some information regarding particular kernel configuration requirements of
- packages outside of LFS at <ulink
+ packages outside of CLFS at <ulink
url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>:</para>
<screen os="i"><userinput>make ARCH=arm CROSS_COMPILE=${CLFS_TARGET}-
menuconfig</userinput></screen>
@@ -127,7 +127,7 @@
kernel source directory. This is specific to kernels prior to the
2.6 series and <emphasis>must not</emphasis> be created on an LFS
system as it can cause problems for packages you may wish to build
- once your base LFS system is complete.</para>
+ once your base CLFS system is complete.</para>
<para>Also, the headers in the system's <filename
class="directory">include</filename> directory should
Modified: branches/clfs-2.0/BOOK/bootable/arm-chapter.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootable/arm-chapter.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/bootable/arm-chapter.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -5,11 +5,11 @@
%general-entities;
]>
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
<?dbhtml dir="bootable"?>
<?dbhtml filename="chapter.html"?>
- <title>Making the LFS System Bootable</title>
+ <title>Making the CLFS System Bootable</title>
<xi:include xmlns:xi="http://www.w3.org/2003/XInclude";
href="common/introduction.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2003/XInclude";
href="common/fstab.xml"/>
Modified: branches/clfs-2.0/BOOK/bootable/common/introduction.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootable/common/introduction.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/bootable/common/introduction.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -10,10 +10,10 @@
<title>Introduction</title>
- <para>It is time to make the LFS system bootable. This chapter
+ <para>It is time to make the CLFS system bootable. This chapter
discusses creating an <filename>fstab</filename> file, building a
- kernel for the new LFS system, and installing the boot loader so
- that the LFS system can be selected for booting at startup.</para>
+ kernel for the new CLFS system, and installing the boot loader so
+ that the CLFS system can be selected for booting at startup.</para>
</sect1>
Modified: branches/clfs-2.0/BOOK/bootscripts/common/introduction.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootscripts/common/introduction.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/bootscripts/common/introduction.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -10,7 +10,7 @@
<title>Introduction</title>
- <para>This chapter details how to install and configure the LFS-Bootscripts
+ <para>This chapter details how to install and configure the CLFS-Bootscripts
package. Most of these scripts will work without modification, but a few
require additional configuration files because they deal with
hardware-dependent information.</para>
Modified: branches/clfs-2.0/BOOK/bootscripts/common/profile.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootscripts/common/profile.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/bootscripts/common/profile.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -118,7 +118,7 @@
locale. Further instructions assume that there are no such error messages
from Glibc.</para>
- <para>Some packages beyond LFS may also lack support for your chosen locale.
+ <para>Some packages beyond CLFS may also lack support for your chosen locale.
One example is the X library (part of the X Window System), which outputs
the following error message:</para>
@@ -160,7 +160,7 @@
writing direction. More complex cases (including UTF-8 based locales)
require additional steps and additional patches because many applications
tend to not work properly under such conditions. These steps and patches
- are not included in the LFS book and such locales are not yet supported
- by LFS.</para>
+ are not included in the CLFS book and such locales are not yet supported
+ by CLFS.</para>
</sect1>
Modified: branches/clfs-2.0/BOOK/bootscripts/common/setclock.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootscripts/common/setclock.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/bootscripts/common/setclock.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -49,7 +49,7 @@
# End /etc/sysconfig/clock</literal>
EOF</userinput></screen>
- <para os="e">A good hint explaining how to deal with time on LFS is available
+ <para os="e">A good hint explaining how to deal with time on CLFS is
available
at <ulink url="&hints-root;time.txt"/>. It explains issues such as
time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
Modified: branches/clfs-2.0/BOOK/bootscripts/common/udev.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootscripts/common/udev.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/bootscripts/common/udev.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -8,7 +8,7 @@
<sect1 id="ch-scripts-udev">
<?dbhtml filename="udev.html"?>
- <title>Device and Module Handling on an LFS System</title>
+ <title>Device and Module Handling on an CLFS System</title>
<indexterm zone="ch-scripts-udev">
<primary sortas="a-Udev">Udev</primary>
Modified: branches/clfs-2.0/BOOK/bootscripts/common/usage.xml
===================================================================
--- branches/clfs-2.0/BOOK/bootscripts/common/usage.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/bootscripts/common/usage.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -18,7 +18,7 @@
based on a concept of <emphasis>run-levels</emphasis>. It can be quite
different from one system to another, so it cannot be assumed that
because things worked in one particular Linux distribution, they should work
- the same in LFS too. LFS has its own way of doing things, but it
+ the same in CLFS too. CLFS has its own way of doing things, but it
respects generally accepted standards.</para>
<para>SysVinit (which will be referred to as <quote>init</quote> from
@@ -123,7 +123,7 @@
</variablelist>
<para>Feel free to modify the way the boot process works (after all,
- it is your own LFS system). The files given here are an example of how
+ it is your own CLFS system). The files given here are an example of how
it can be done.</para>
</sect1>
Modified: branches/clfs-2.0/BOOK/cross-tools/common/glibc.xml
===================================================================
--- branches/clfs-2.0/BOOK/cross-tools/common/glibc.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/cross-tools/common/glibc.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -230,10 +230,10 @@
localedata/install-locales</command> command above are not properly
supported by some applications that are in the LFS and BLFS books. Because
of the various problems that arise due to application programmers making
- assumptions that break in such locales, LFS should not be used in locales
+ assumptions that break in such locales, CLFS should not be used in locales
that utilize multibyte character sets (including UTF-8) or right-to-left
writing order. Numerous unofficial and unstable patches are required to
- fix these problems, and it has been decided by the LFS developers not to
+ fix these problems, and it has been decided by the CLFS developers not to
support such complex locales at this time. This applies to the ja_JP and
fa_IR locales as well—they have been installed only for GCC and
Gettext tests to pass, and the <command>watch</command> program (part of
Modified: branches/clfs-2.0/BOOK/final-preps/creatingdirs.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-preps/creatingdirs.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/final-preps/creatingdirs.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -10,7 +10,7 @@
<title>Creating Directories</title>
- <para>It is time to create some structure in the LFS file system. Create a
+ <para>It is time to create some structure in the CLFS file system. Create a
standard directory tree by issuing the following commands:</para>
<screen><userinput>mkdir -pv ${CLFS}/{bin,boot,dev,{etc/,}opt,home,lib,mnt}
Modified: branches/clfs-2.0/BOOK/final-preps/settingenviron.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-preps/settingenviron.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/final-preps/settingenviron.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -44,7 +44,7 @@
CLFS=/mnt/clfs
LC_ALL=POSIX
PATH=${CLFS}/cross-tools/bin:/bin:/usr/bin
-export LFS LC_ALL PATH</literal>
+export CLFS LC_ALL PATH</literal>
EOF</userinput></screen>
<para os="f">The <command>set +h</command> command turns off
Modified: branches/clfs-2.0/BOOK/final-system/common/e2fsprogs.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-system/common/e2fsprogs.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/final-system/common/e2fsprogs.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -70,7 +70,7 @@
<para>This disables the building of the Enterprise Volume
Management System (EVMS) plugin. This plugin is not up-to-date with
the latest EVMS internal interfaces and EVMS is not installed as part
- of a base LFS system, so the plugin is not required. See the EVMS
+ of a base CLFS system, so the plugin is not required. See the EVMS
website at <ulink url="http://evms.sourceforge.net/"/> for more
information regarding EVMS.</para>
</listitem>
Modified: branches/clfs-2.0/BOOK/final-system/common/inetutils.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-system/common/inetutils.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/final-system/common/inetutils.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -85,7 +85,7 @@
<listitem>
<para>This disables the installation of the various network
servers included as part of the Inetutils package. These servers are
- deemed not appropriate in a basic LFS system. Some are insecure by
+ deemed not appropriate in a basic CLFS system. Some are insecure by
nature and are only considered safe on trusted networks. More
information can be found at <ulink
url="&blfs-root;view/svn/basicnet/inetutils.html"/>. Note that
Modified: branches/clfs-2.0/BOOK/final-system/common/man.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-system/common/man.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/final-system/common/man.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -112,7 +112,7 @@
<command>man2dvi</command> program for localized man pages in
non-ISO 8859-1 locales. Also, it does not work with multibyte
character sets. The first problem does not currently have a solution.
- The second issue is not of concern because the LFS installation does
+ The second issue is not of concern because the CLFS installation does
not support multibyte character sets.</para>
<para os="v">Additional information with regards to the compression of
Modified: branches/clfs-2.0/BOOK/final-system/common/pkgmgt.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-system/common/pkgmgt.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/final-system/common/pkgmgt.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -221,7 +221,7 @@
url="http://lsbbook.gforge.freestandards.org/package.html#RPM";>Linux
Standard Base Specification</ulink>), pkg-utils, Debian's apt, and
Gentoo's Portage system. A hint describing how to adopt this style of
- package management for LFS systems is located at <ulink
+ package management for CLFS systems is located at <ulink
url="&hints-root;/fakeroot.txt"/>.</para>
</sect3>
Modified: branches/clfs-2.0/BOOK/final-system/common/vim.xml
===================================================================
--- branches/clfs-2.0/BOOK/final-system/common/vim.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/final-system/common/vim.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -380,7 +380,7 @@
<para>Spell checks a file and generates the syntax statements
necessary to highlight in <command>vim</command>. This script
requires the old Unix <command>spell</command> command, which
- is provided neither in LFS nor in BLFS</para>
+ is provided neither in CLFS nor in BLFS</para>
<indexterm zone="ch-system-vim vimspell.sh">
<primary sortas="b-vimspell.sh">vimspell.sh</primary>
</indexterm>
Modified: branches/clfs-2.0/BOOK/introduction/common/askforhelp.xml
===================================================================
--- branches/clfs-2.0/BOOK/introduction/common/askforhelp.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/introduction/common/askforhelp.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -20,7 +20,7 @@
<para>If you cannot find your problem listed in the FAQ, search the mailing
lists at <ulink url="&lfs-root;search.html"/>.</para>
- <para>We also have a wonderful LFS community that is willing to offer
+ <para>We also have a wonderful CLFS community that is willing to offer
assistance through the mailing lists and IRC (see the <xref
linkend="ch-intro-resources"/> section of this book). However, we
get several support questions everyday and many of them can be easily
@@ -58,7 +58,7 @@
<note>
<para>Deviating from this book does <emphasis>not</emphasis>
- mean that we will not help you. After all, the LFS project is
+ mean that we will not help you. After all, the CLFS project is
about personal preference. Being upfront about any changes to
the established procedure helps us evaluate and determine
possible causes of your problem.</para>
Modified: branches/clfs-2.0/BOOK/introduction/common/resources.xml
===================================================================
--- branches/clfs-2.0/BOOK/introduction/common/resources.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/introduction/common/resources.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -13,7 +13,7 @@
<sect2 id="ch-intro-faq">
<title>FAQ</title>
- <para>If during the building of the LFS system you encounter any
+ <para>If during the building of the CLFS system you encounter any
errors, have any questions, or think there is a typo in the book,
please start by consulting the Frequently Asked Questions (FAQ)
that is located at <ulink url="&faq-root;"/>.</para>
@@ -24,7 +24,7 @@
<title>Mailing Lists</title>
<para>The <uri>linuxfromscratch.org</uri> server hosts a number of
- mailing lists used for the development of the LFS project. These lists
+ mailing lists used for the development of the CLFS project. These lists
include the main development and support lists, among others. If the
FAQ does not solve the problem you are having, the next step would be to
search the mailing lists at <ulink url="&lfs-root;search.html"/>.</para>
@@ -48,9 +48,9 @@
<sect2 id="ch-intro-irc">
<title>IRC</title>
- <para>Several members of the LFS community offer assistance on our
+ <para>Several members of the CLFS community offer assistance on our
community Internet Relay Chat (IRC) network. Before using this support,
- please make sure that your question is not already answered in the LFS
+ please make sure that your question is not already answered in the CLFS
FAQ or the mailing list archives. You can find the IRC network at
<uri>chat.freenode.net</uri>. The support channel for cross-lfs
is named #cross-lfs. If you need to show people the output of your
Modified: branches/clfs-2.0/BOOK/materials/common/patches.xml
===================================================================
--- branches/clfs-2.0/BOOK/materials/common/patches.xml 2006-07-09 19:48:43 UTC
(rev 1954)
+++ branches/clfs-2.0/BOOK/materials/common/patches.xml 2006-07-09 19:49:01 UTC
(rev 1955)
@@ -14,7 +14,7 @@
These patches correct any mistakes in the packages that should be
fixed by the maintainer. The patches also make small modifications to
make the packages easier to work with. The following patches will be
- needed to build an LFS system:</para>
+ needed to build an CLFS system:</para>
<variablelist role="materials">
Modified: branches/clfs-2.0/BOOK/partitioning/common/creatingfilesystem.xml
===================================================================
--- branches/clfs-2.0/BOOK/partitioning/common/creatingfilesystem.xml
2006-07-09 19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/partitioning/common/creatingfilesystem.xml
2006-07-09 19:49:01 UTC (rev 1955)
@@ -19,7 +19,7 @@
<ulink url="&blfs-root;view/svn/postlfs/filesystems.html"/>.</para>
<para os="b">To create an <systemitem class="filesystem">ext2</systemitem>
file
- system on the LFS partition, run the following:</para>
+ system on the CLFS partition, run the following:</para>
<screen os="c"><userinput>mke2fs
/dev/<replaceable>[xxx]</replaceable></userinput></screen>
@@ -42,7 +42,7 @@
large_file; resize_inode or sparse_super then your host system may have
custom
enhancements. In that case, to avoid later problems, you should compile
the
stock E2fsprogs package and use the resulting binaries to re-create the
- filesystem on your LFS partition:</para>
+ filesystem on your CLFS partition:</para>
<screen os="g"><userinput>cd /tmp
tar xjf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.bz2
Modified: branches/clfs-2.0/BOOK/partitioning/common/creatingpartition.xml
===================================================================
--- branches/clfs-2.0/BOOK/partitioning/common/creatingpartition.xml
2006-07-09 19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/partitioning/common/creatingpartition.xml
2006-07-09 19:49:01 UTC (rev 1955)
@@ -25,7 +25,7 @@
This is enough to store all the source tarballs and compile the packages.
However, if the CLFS system is intended to be the primary Linux system,
additional software will probably be installed which will require
- additional space (2-3 GB). The LFS system itself will not take up this
+ additional space (2-3 GB). The CLFS system itself will 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>
@@ -34,7 +34,7 @@
available for compilation processes, it is a good idea to use a small 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
+ partition for an CLFS system can be the same as the one used by the host
system, in which case it is not necessary to create another one.</para>
<para os="d">Start a disk partitioning program such as
<command>cfdisk</command>
Modified: branches/clfs-2.0/BOOK/partitioning/common/mounting.xml
===================================================================
--- branches/clfs-2.0/BOOK/partitioning/common/mounting.xml 2006-07-09
19:48:43 UTC (rev 1954)
+++ branches/clfs-2.0/BOOK/partitioning/common/mounting.xml 2006-07-09
19:49:01 UTC (rev 1955)
@@ -31,7 +31,7 @@
<para>Replace <replaceable>[xxx]</replaceable> with the designation of
the CLFS partition.</para>
- <para>If using multiple partitions for LFS (e.g., one for <filename
+ <para>If using multiple partitions for CLFS (e.g., one for <filename
class="directory">/</filename> and another for <filename
class="directory">/usr</filename>), mount them using:</para>
Modified: branches/clfs-2.0/BOOK/the-end/reboot.xml
===================================================================
--- branches/clfs-2.0/BOOK/the-end/reboot.xml 2006-07-09 19:48:43 UTC (rev
1954)
+++ branches/clfs-2.0/BOOK/the-end/reboot.xml 2006-07-09 19:49:01 UTC (rev
1955)
@@ -20,7 +20,7 @@
continue forward. By installing a few extra packages from the BLFS
book while still in our current chroot environment, you can leave
yourself in a much better position to continue on once you reboot
- into your new LFS installation. Installing a text mode web browser,
+ into your new CLFS installation. Installing a text mode web browser,
such as Lynx, you can easily view the BLFS book in one virtual terminal,
while building packages in another. The GPM package will also allow you
to perform copy/paste actions in your virtual terminals. Lastly, if you
@@ -29,7 +29,7 @@
this point might also be useful.</para>
<para>Now that we have said that, lets move on to booting our shiny
- new LFS installation for the first time! First exit from the chroot
+ new CLFS installation for the first time! First exit from the chroot
environment:</para>
<screen><userinput>logout</userinput></screen>
@@ -42,7 +42,7 @@
umount $CLFS/proc
umount $CLFS/sys</userinput></screen>
- <para>Unmount the LFS file system itself:</para>
+ <para>Unmount the CLFS file system itself:</para>
<screen><userinput>umount $CLFS</userinput></screen>
@@ -60,7 +60,7 @@
<para>Assuming the boot loader was set up as outlined earlier,
<emphasis>CLFS &version;</emphasis> will boot automatically.</para>
- <para>When the reboot is complete, the LFS system is ready for use and
+ <para>When the reboot is complete, the CLFS system is ready for use and
more software may be added to suit your needs.</para>
</sect1>
Modified: branches/clfs-2.0/BOOK/the-end/whatnow.xml
===================================================================
--- branches/clfs-2.0/BOOK/the-end/whatnow.xml 2006-07-09 19:48:43 UTC (rev
1954)
+++ branches/clfs-2.0/BOOK/the-end/whatnow.xml 2006-07-09 19:49:01 UTC (rev
1955)
@@ -10,11 +10,11 @@
<title>What Now?</title>
- <para>Thank you for reading this LFS book. We hope that you have
+ <para>Thank you for reading this CLFS book. We hope that you have
found this book helpful and have learned more about the system
creation process.</para>
- <para>Now that the LFS system is installed, you may be wondering
+ <para>Now that the CLFS system is installed, you may be wondering
<quote>What next?</quote> To answer that question, we have compiled
a list of resources for you.</para>
@@ -24,7 +24,7 @@
<para>Maintenance</para>
<para>Bugs and security notices are reported regularly for all software.
- Since an LFS system is compiled from source, it is up to you to keep
+ Since an CLFS system is compiled from source, it is up to you to keep
abreast of such reports. There are several online resources that track
such reports, some of which are shown below:</para>
--
http://linuxfromscratch.org/mailman/listinfo/cross-lfs
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
