[Clfs-commits] commit: r4336 - in /branches/clfs-sysroot/BOOK: introduction/common/resources.xml partitioning/common/creatingpartition.xml
svn at cross-lfs.org
svn at cross-lfs.org
Mon Jan 5 00:03:54 PST 2009
Author: chris at beaker67.com
Date: Mon Jan 5 08:03:54 2009
New Revision: 4336
Log:
Text updates from trunk
Modified:
branches/clfs-sysroot/BOOK/introduction/common/resources.xml
branches/clfs-sysroot/BOOK/partitioning/common/creatingpartition.xml
Modified: branches/clfs-sysroot/BOOK/introduction/common/resources.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/introduction/common/resources.xml (original)
+++ branches/clfs-sysroot/BOOK/introduction/common/resources.xml Mon Jan 5 08:03:54 2009
@@ -23,25 +23,29 @@
<sect2 id="ch-intro-maillists" xreflabel="Chapter 1 - Mailing Lists">
<title>Mailing Lists</title>
- <para>The <uri>linuxfromscratch.org</uri> server hosts a number of
+ <para>The <uri>cross-lfs.org</uri> server hosts a number of
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>
+ FAQ does not contain your answer, you can search the CLFS lists via
+ The Mail Archive <ulink url="http://www.mail-archive.com"/>. You can
+ find the mail lists with the following link:</para>
+ <para><ulink url="http://www.mail-archive.com/index.php?hunt=clfs"/></para>
+
<para>For information on the different lists, how to subscribe, archive
- locations, and additional information, visit
- <ulink url="&lfs-root;mail.html"/>. For mailing lists specifically
- for CLFS, visit <ulink url="&clfs-wiki;wiki/lists"/>.</para>
+ locations, and additional information, visit <ulink url="&clfs-wiki;wiki/lists"/>.</para>
</sect2>
<sect2 id="ch-intro-newsserver">
<title>News Server</title>
- <para> The Linux From Scratch News Server is no longer available.
- Please use the other support methods listed on this page
- </para>
+ <para>Cross-LFS does not maintain its own News Server, but we do provide
+ access via <uri>gmane.org</uri> <ulink url="http://gmane.org"/>. If you want to subscribe
+ to the Cross-LFS lists via a newsreader you can utilize <uri>gmane.org</uri>.
+ You can find the gmane search for CLFS with the following link:</para>
+
+ <para><ulink url="http://dir.gmane.org/search.php?match=clfs"/></para>
</sect2>
@@ -52,39 +56,28 @@
community Internet Relay Chat (IRC) network. Before using this support,
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
+ <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
problems, please use http://pastebin.cross-lfs.org and reference
the pastebin URL when asking your questions.</para>
-
- </sect2>
-
- <sect2 id="ch-intro-references">
- <title>References</title>
-
- <para>For additional information on the packages, useful tips are
- available in the LFS Package Reference page located at <ulink
- url="&lfs-root;~matthew/LFS-references.html"/>.</para>
</sect2>
<sect2 id="ch-intro-mirrors" xreflabel="Chapter 1 - Mirror sites">
<title>Mirror Sites</title>
- <para>The LFS project has a number of world-wide mirrors to make
+ <para>The CLFS project has a number of world-wide mirrors to make
accessing the website and downloading the required packages more
- convenient. Please visit the LFS website at <ulink
- url="&lfs-root;mirrors.html"/> for a list of current mirrors of
- the LFS website, or <ulink url="&clfs-wiki;wiki/mirrors"/> for
- mirrors of CLFS.</para>
+ convenient. Please visit the CLFS website at
+ <ulink url="&clfs-wiki;wiki/mirrors"/> for mirrors of CLFS.</para>
</sect2>
<sect2 id="ch-intro-contactinfo">
<title>Contact Information</title>
- <para>Please direct all your questions and comments to one of the LFS
- or CLFS mailing lists (see above).</para>
+ <para>Please direct all your questions and comments to the
+ CLFS mailing lists (see above).</para>
</sect2>
Modified: branches/clfs-sysroot/BOOK/partitioning/common/creatingpartition.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/partitioning/common/creatingpartition.xml (original)
+++ branches/clfs-sysroot/BOOK/partitioning/common/creatingpartition.xml Mon Jan 5 08:03:54 2009
@@ -10,25 +10,20 @@
<title>Creating a New Partition</title>
- <para os="a">Like most other operating systems, CLFS is usually installed on
- a dedicated partition. The recommended approach to building a CLFS
+ <para os="a">Like most other operating systems, CLFS is usually installed
+ on a dedicated partition. The recommended approach to building a CLFS
system is to use an available empty partition or, if you have enough
- unpartitioned space, to create one. However, a CLFS system (in fact
- even multiple CLFS systems) may also be installed on a partition already
- occupied by another operating system and the different systems will
- co-exist peacefully. The document <ulink
- url="&hints-root;lfs_next_to_existing_systems.txt"/> explains how to
- implement this, whereas this book discusses the method of using a fresh
- partition for the installation.</para>
+ unpartitioned space, to create one. However, if you're building for a different
+ architecture you can simply build everything in <quote>/mnt/clfs</quote>
+ and transfer it to your target machine.</para>
- <para os="b">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 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 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>
+ <para os="b">A minimal system requires around 2.5 gigabytes (GB).
+ This is enough to store all the source tarballs and compile the packages. 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. If the
+ CLFS system is intended to be the primary Linux system, additional software will
+ probably be installed which will require additional space (2-10 GB). </para>
<para os="c">Because there is not always enough Random Access Memory (RAM)
available for compilation processes, it is a good idea to use a small disk
More information about the Clfs-commits
mailing list