Changeset 9da6c48 in clfs-sysroot
- Timestamp:
- Jan 5, 2009, 12:03:54 AM (16 years ago)
- Branches:
- master
- Children:
- 76c3eca
- Parents:
- b8b5495
- Location:
- BOOK
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/introduction/common/resources.xml
rb8b5495 r9da6c48 24 24 <title>Mailing Lists</title> 25 25 26 <para>The <uri> linuxfromscratch.org</uri> server hosts a number of26 <para>The <uri>cross-lfs.org</uri> server hosts a number of 27 27 mailing lists used for the development of the CLFS project. These lists 28 28 include the main development and support lists, among others. If the 29 FAQ does not solve the problem you are having, the next step would be to 30 search the mailing lists at <ulink url="&lfs-root;search.html"/>.</para> 29 FAQ does not contain your answer, you can search the CLFS lists via 30 The Mail Archive <ulink url="http://www.mail-archive.com"/>. You can 31 find the mail lists with the following link:</para> 31 32 33 <para><ulink url="http://www.mail-archive.com/index.php?hunt=clfs"/></para> 34 32 35 <para>For information on the different lists, how to subscribe, archive 33 locations, and additional information, visit 34 <ulink url="&lfs-root;mail.html"/>. For mailing lists specifically 35 for CLFS, visit <ulink url="&clfs-wiki;wiki/lists"/>.</para> 36 locations, and additional information, visit <ulink url="&clfs-wiki;wiki/lists"/>.</para> 36 37 37 38 </sect2> … … 40 41 <title>News Server</title> 41 42 42 <para> The Linux From Scratch News Server is no longer available. 43 Please use the other support methods listed on this page 44 </para> 43 <para>Cross-LFS does not maintain its own News Server, but we do provide 44 access via <uri>gmane.org</uri> <ulink url="http://gmane.org"/>. If you want to subscribe 45 to the Cross-LFS lists via a newsreader you can utilize <uri>gmane.org</uri>. 46 You can find the gmane search for CLFS with the following link:</para> 47 48 <para><ulink url="http://dir.gmane.org/search.php?match=clfs"/></para> 45 49 46 50 </sect2> … … 53 57 please make sure that your question is not already answered in the CLFS 54 58 FAQ or the mailing list archives. You can find the IRC network at 55 <uri>chat.freenode.net</uri>. The support channel for cross-lfs 56 isnamed #cross-lfs. If you need to show people the output of your59 <uri>chat.freenode.net</uri>. The support channel for cross-lfs is 60 named #cross-lfs. If you need to show people the output of your 57 61 problems, please use http://pastebin.cross-lfs.org and reference 58 62 the pastebin URL when asking your questions.</para> 59 60 </sect2>61 62 <sect2 id="ch-intro-references">63 <title>References</title>64 65 <para>For additional information on the packages, useful tips are66 available in the LFS Package Reference page located at <ulink67 url="&lfs-root;~matthew/LFS-references.html"/>.</para>68 63 69 64 </sect2> … … 72 67 <title>Mirror Sites</title> 73 68 74 <para>The LFS project has a number of world-wide mirrors to make69 <para>The CLFS project has a number of world-wide mirrors to make 75 70 accessing the website and downloading the required packages more 76 convenient. Please visit the LFS website at <ulink 77 url="&lfs-root;mirrors.html"/> for a list of current mirrors of 78 the LFS website, or <ulink url="&clfs-wiki;wiki/mirrors"/> for 79 mirrors of CLFS.</para> 71 convenient. Please visit the CLFS website at 72 <ulink url="&clfs-wiki;wiki/mirrors"/> for mirrors of CLFS.</para> 80 73 81 74 </sect2> … … 84 77 <title>Contact Information</title> 85 78 86 <para>Please direct all your questions and comments to one of the LFS87 orCLFS mailing lists (see above).</para>79 <para>Please direct all your questions and comments to the 80 CLFS mailing lists (see above).</para> 88 81 89 82 </sect2> -
BOOK/partitioning/common/creatingpartition.xml
rb8b5495 r9da6c48 11 11 <title>Creating a New Partition</title> 12 12 13 <para os="a">Like most other operating systems, CLFS is usually installed on14 a dedicated partition. The recommended approach to building a CLFS13 <para os="a">Like most other operating systems, CLFS is usually installed 14 on a dedicated partition. The recommended approach to building a CLFS 15 15 system is to use an available empty partition or, if you have enough 16 unpartitioned space, to create one. However, a CLFS system (in fact 17 even multiple CLFS systems) may also be installed on a partition already 18 occupied by another operating system and the different systems will 19 co-exist peacefully. The document <ulink 20 url="&hints-root;lfs_next_to_existing_systems.txt"/> explains how to 21 implement this, whereas this book discusses the method of using a fresh 22 partition for the installation.</para> 16 unpartitioned space, to create one. However, if you're building for a different 17 architecture you can simply build everything in <quote>/mnt/clfs</quote> 18 and transfer it to your target machine.</para> 23 19 24 <para os="b">A minimal system requires a partition of around 1.3 gigabytes (GB). 25 This is enough to store all the source tarballs and compile the packages. 26 However, if the CLFS system is intended to be the primary Linux system, 27 additional software will probably be installed which will require 28 additional space (2-3 GB). The CLFS system itself will not take up this 29 much room. A large portion of this requirement is to provide sufficient 30 free temporary storage. Compiling packages can require a lot of disk space 31 which will be reclaimed after the package is installed.</para> 20 <para os="b">A minimal system requires around 2.5 gigabytes (GB). 21 This is enough to store all the source tarballs and compile the packages. The CLFS 22 system itself will not take up this much room. A large portion of this requirement 23 is to provide sufficient free temporary storage. Compiling packages can require a 24 lot of disk space which will be reclaimed after the package is installed. If the 25 CLFS system is intended to be the primary Linux system, additional software will 26 probably be installed which will require additional space (2-10 GB). </para> 32 27 33 28 <para os="c">Because there is not always enough Random Access Memory (RAM)
Note:
See TracChangeset
for help on using the changeset viewer.