- Timestamp:
- Jul 9, 2006, 12:29:55 PM (18 years ago)
- Branches:
- master
- Children:
- 47c828c
- Parents:
- 83be687
- Location:
- BOOK
- Files:
-
- 25 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/appendices/dependencies/common.xml
r83be687 r755f44a 12 12 <title>Dependencies</title> 13 13 14 <para>Every package built in LFS relies on one or more other packages14 <para>Every package built in CLFS relies on one or more other packages 15 15 in order to build and install properly. Some packages even participate 16 16 in circular dependencies, that is, the first package depends on the second 17 17 which in turn depends on the first. Because of these dependencies, the 18 order in which packages are built in LFS is very important. The purpose18 order in which packages are built in CLFS is very important. The purpose 19 19 of this page is to document the dependencies of each package built in LFS.</para> 20 20 -
BOOK/bootable/arm-chapter.xml
r83be687 r755f44a 6 6 ]> 7 7 8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">8 <chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable"> 9 9 <?dbhtml dir="bootable"?> 10 10 <?dbhtml filename="chapter.html"?> 11 11 12 <title>Making the LFS System Bootable</title>12 <title>Making the CLFS System Bootable</title> 13 13 14 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/> -
BOOK/bootable/arm/kernel.xml
r83be687 r755f44a 51 51 enabled and built into the kernel, not as modules. BLFS has 52 52 some information regarding particular kernel configuration requirements of 53 packages outside of LFS at <ulink53 packages outside of CLFS at <ulink 54 54 url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>:</para> 55 55 … … 128 128 2.6 series and <emphasis>must not</emphasis> be created on an LFS 129 129 system as it can cause problems for packages you may wish to build 130 once your base LFS system is complete.</para>130 once your base CLFS system is complete.</para> 131 131 132 132 <para>Also, the headers in the system's <filename -
BOOK/bootable/common/introduction.xml
r83be687 r755f44a 11 11 <title>Introduction</title> 12 12 13 <para>It is time to make the LFS system bootable. This chapter13 <para>It is time to make the CLFS system bootable. This chapter 14 14 discusses creating an <filename>fstab</filename> file, building a 15 kernel for the new LFS system, and installing the boot loader so16 that the LFS system can be selected for booting at startup.</para>15 kernel for the new CLFS system, and installing the boot loader so 16 that the CLFS system can be selected for booting at startup.</para> 17 17 18 18 </sect1> -
BOOK/bootscripts/common/introduction.xml
r83be687 r755f44a 11 11 <title>Introduction</title> 12 12 13 <para>This chapter details how to install and configure the LFS-Bootscripts13 <para>This chapter details how to install and configure the CLFS-Bootscripts 14 14 package. Most of these scripts will work without modification, but a few 15 15 require additional configuration files because they deal with -
BOOK/bootscripts/common/profile.xml
r83be687 r755f44a 119 119 from Glibc.</para> 120 120 121 <para>Some packages beyond LFS may also lack support for your chosen locale.121 <para>Some packages beyond CLFS may also lack support for your chosen locale. 122 122 One example is the X library (part of the X Window System), which outputs 123 123 the following error message:</para> … … 161 161 require additional steps and additional patches because many applications 162 162 tend to not work properly under such conditions. These steps and patches 163 are not included in the LFS book and such locales are not yet supported164 by LFS.</para>163 are not included in the CLFS book and such locales are not yet supported 164 by CLFS.</para> 165 165 166 166 </sect1> -
BOOK/bootscripts/common/setclock.xml
r83be687 r755f44a 50 50 EOF</userinput></screen> 51 51 52 <para os="e">A good hint explaining how to deal with time on LFS is available52 <para os="e">A good hint explaining how to deal with time on CLFS is available 53 53 at <ulink url="&hints-root;time.txt"/>. It explains issues such as 54 54 time zones, UTC, and the <envar>TZ</envar> environment variable.</para> -
BOOK/bootscripts/common/udev.xml
r83be687 r755f44a 9 9 <?dbhtml filename="udev.html"?> 10 10 11 <title>Device and Module Handling on an LFS System</title>11 <title>Device and Module Handling on an CLFS System</title> 12 12 13 13 <indexterm zone="ch-scripts-udev"> -
BOOK/bootscripts/common/usage.xml
r83be687 r755f44a 19 19 different from one system to another, so it cannot be assumed that 20 20 because things worked in one particular Linux distribution, they should work 21 the same in LFS too.LFS has its own way of doing things, but it21 the same in CLFS too. CLFS has its own way of doing things, but it 22 22 respects generally accepted standards.</para> 23 23 … … 124 124 125 125 <para>Feel free to modify the way the boot process works (after all, 126 it is your own LFS system). The files given here are an example of how126 it is your own CLFS system). The files given here are an example of how 127 127 it can be done.</para> 128 128 -
BOOK/cross-tools/common/glibc.xml
r83be687 r755f44a 231 231 supported by some applications that are in the LFS and BLFS books. Because 232 232 of the various problems that arise due to application programmers making 233 assumptions that break in such locales, LFS should not be used in locales233 assumptions that break in such locales, CLFS should not be used in locales 234 234 that utilize multibyte character sets (including UTF-8) or right-to-left 235 235 writing order. Numerous unofficial and unstable patches are required to 236 fix these problems, and it has been decided by the LFS developers not to236 fix these problems, and it has been decided by the CLFS developers not to 237 237 support such complex locales at this time. This applies to the ja_JP and 238 238 fa_IR locales as well—they have been installed only for GCC and -
BOOK/final-preps/creatingdirs.xml
r83be687 r755f44a 11 11 <title>Creating Directories</title> 12 12 13 <para>It is time to create some structure in the LFS file system. Create a13 <para>It is time to create some structure in the CLFS file system. Create a 14 14 standard directory tree by issuing the following commands:</para> 15 15 -
BOOK/final-preps/settingenviron.xml
r83be687 r755f44a 45 45 LC_ALL=POSIX 46 46 PATH=${CLFS}/cross-tools/bin:/bin:/usr/bin 47 export LFS LC_ALL PATH</literal>47 export CLFS LC_ALL PATH</literal> 48 48 EOF</userinput></screen> 49 49 -
BOOK/final-system/common/e2fsprogs.xml
r83be687 r755f44a 71 71 Management System (EVMS) plugin. This plugin is not up-to-date with 72 72 the latest EVMS internal interfaces and EVMS is not installed as part 73 of a base LFS system, so the plugin is not required. See the EVMS73 of a base CLFS system, so the plugin is not required. See the EVMS 74 74 website at <ulink url="http://evms.sourceforge.net/"/> for more 75 75 information regarding EVMS.</para> -
BOOK/final-system/common/inetutils.xml
r83be687 r755f44a 86 86 <para>This disables the installation of the various network 87 87 servers included as part of the Inetutils package. These servers are 88 deemed not appropriate in a basic LFS system. Some are insecure by88 deemed not appropriate in a basic CLFS system. Some are insecure by 89 89 nature and are only considered safe on trusted networks. More 90 90 information can be found at <ulink -
BOOK/final-system/common/man.xml
r83be687 r755f44a 113 113 non-ISO 8859-1 locales. Also, it does not work with multibyte 114 114 character sets. The first problem does not currently have a solution. 115 The second issue is not of concern because the LFS installation does115 The second issue is not of concern because the CLFS installation does 116 116 not support multibyte character sets.</para> 117 117 -
BOOK/final-system/common/pkgmgt.xml
r83be687 r755f44a 222 222 Standard Base Specification</ulink>), pkg-utils, Debian's apt, and 223 223 Gentoo's Portage system. A hint describing how to adopt this style of 224 package management for LFS systems is located at <ulink224 package management for CLFS systems is located at <ulink 225 225 url="&hints-root;/fakeroot.txt"/>.</para> 226 226 -
BOOK/final-system/common/vim.xml
r83be687 r755f44a 381 381 necessary to highlight in <command>vim</command>. This script 382 382 requires the old Unix <command>spell</command> command, which 383 is provided neither in LFS nor in BLFS</para>383 is provided neither in CLFS nor in BLFS</para> 384 384 <indexterm zone="ch-system-vim vimspell.sh"> 385 385 <primary sortas="b-vimspell.sh">vimspell.sh</primary> -
BOOK/introduction/common/askforhelp.xml
r83be687 r755f44a 21 21 lists at <ulink url="&lfs-root;search.html"/>.</para> 22 22 23 <para>We also have a wonderful LFS community that is willing to offer23 <para>We also have a wonderful CLFS community that is willing to offer 24 24 assistance through the mailing lists and IRC (see the <xref 25 25 linkend="ch-intro-resources"/> section of this book). However, we … … 59 59 <note> 60 60 <para>Deviating from this book does <emphasis>not</emphasis> 61 mean that we will not help you. After all, the LFS project is61 mean that we will not help you. After all, the CLFS project is 62 62 about personal preference. Being upfront about any changes to 63 63 the established procedure helps us evaluate and determine -
BOOK/introduction/common/resources.xml
r83be687 r755f44a 14 14 <title>FAQ</title> 15 15 16 <para>If during the building of the LFS system you encounter any16 <para>If during the building of the CLFS system you encounter any 17 17 errors, have any questions, or think there is a typo in the book, 18 18 please start by consulting the Frequently Asked Questions (FAQ) … … 25 25 26 26 <para>The <uri>linuxfromscratch.org</uri> server hosts a number of 27 mailing lists used for the development of the LFS project. These lists27 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 29 FAQ does not solve the problem you are having, the next step would be to … … 49 49 <title>IRC</title> 50 50 51 <para>Several members of the LFS community offer assistance on our51 <para>Several members of the CLFS community offer assistance on our 52 52 community Internet Relay Chat (IRC) network. Before using this support, 53 please make sure that your question is not already answered in the LFS53 please make sure that your question is not already answered in the CLFS 54 54 FAQ or the mailing list archives. You can find the IRC network at 55 55 <uri>chat.freenode.net</uri>. The support channel for cross-lfs -
BOOK/materials/common/patches.xml
r83be687 r755f44a 15 15 fixed by the maintainer. The patches also make small modifications to 16 16 make the packages easier to work with. The following patches will be 17 needed to build an LFS system:</para>17 needed to build an CLFS system:</para> 18 18 19 19 <variablelist role="materials"> -
BOOK/partitioning/common/creatingfilesystem.xml
r83be687 r755f44a 20 20 21 21 <para os="b">To create an <systemitem class="filesystem">ext2</systemitem> file 22 system on the LFS partition, run the following:</para>22 system on the CLFS partition, run the following:</para> 23 23 24 24 <screen os="c"><userinput>mke2fs /dev/<replaceable>[xxx]</replaceable></userinput></screen> … … 43 43 enhancements. In that case, to avoid later problems, you should compile the 44 44 stock E2fsprogs package and use the resulting binaries to re-create the 45 filesystem on your LFS partition:</para>45 filesystem on your CLFS partition:</para> 46 46 47 47 <screen os="g"><userinput>cd /tmp -
BOOK/partitioning/common/creatingpartition.xml
r83be687 r755f44a 26 26 However, if the CLFS system is intended to be the primary Linux system, 27 27 additional software will probably be installed which will require 28 additional space (2-3 GB). The LFS system itself will not take up this28 additional space (2-3 GB). The CLFS system itself will not take up this 29 29 much room. A large portion of this requirement is to provide sufficient 30 30 free temporary storage. Compiling packages can require a lot of disk space … … 35 35 partition as swap space. This is used by the kernel to store seldom-used 36 36 data and leave more memory available for active processes. The swap 37 partition for an LFS system can be the same as the one used by the host37 partition for an CLFS system can be the same as the one used by the host 38 38 system, in which case it is not necessary to create another one.</para> 39 39 -
BOOK/partitioning/common/mounting.xml
r83be687 r755f44a 32 32 the CLFS partition.</para> 33 33 34 <para>If using multiple partitions for LFS (e.g., one for <filename34 <para>If using multiple partitions for CLFS (e.g., one for <filename 35 35 class="directory">/</filename> and another for <filename 36 36 class="directory">/usr</filename>), mount them using:</para> -
BOOK/the-end/reboot.xml
r83be687 r755f44a 21 21 book while still in our current chroot environment, you can leave 22 22 yourself in a much better position to continue on once you reboot 23 into your new LFS installation. Installing a text mode web browser,23 into your new CLFS installation. Installing a text mode web browser, 24 24 such as Lynx, you can easily view the BLFS book in one virtual terminal, 25 25 while building packages in another. The GPM package will also allow you … … 30 30 31 31 <para>Now that we have said that, lets move on to booting our shiny 32 new LFS installation for the first time! First exit from the chroot32 new CLFS installation for the first time! First exit from the chroot 33 33 environment:</para> 34 34 … … 43 43 umount $CLFS/sys</userinput></screen> 44 44 45 <para>Unmount the LFS file system itself:</para>45 <para>Unmount the CLFS file system itself:</para> 46 46 47 47 <screen><userinput>umount $CLFS</userinput></screen> … … 61 61 <emphasis>CLFS &version;</emphasis> will boot automatically.</para> 62 62 63 <para>When the reboot is complete, the LFS system is ready for use and63 <para>When the reboot is complete, the CLFS system is ready for use and 64 64 more software may be added to suit your needs.</para> 65 65 -
BOOK/the-end/whatnow.xml
r83be687 r755f44a 11 11 <title>What Now?</title> 12 12 13 <para>Thank you for reading this LFS book. We hope that you have13 <para>Thank you for reading this CLFS book. We hope that you have 14 14 found this book helpful and have learned more about the system 15 15 creation process.</para> 16 16 17 <para>Now that the LFS system is installed, you may be wondering17 <para>Now that the CLFS system is installed, you may be wondering 18 18 <quote>What next?</quote> To answer that question, we have compiled 19 19 a list of resources for you.</para> … … 25 25 26 26 <para>Bugs and security notices are reported regularly for all software. 27 Since an LFS system is compiled from source, it is up to you to keep27 Since an CLFS system is compiled from source, it is up to you to keep 28 28 abreast of such reports. There are several online resources that track 29 29 such reports, some of which are shown below:</para>
Note:
See TracChangeset
for help on using the changeset viewer.