Changeset fb40919
- Timestamp:
- Jun 21, 2006, 9:53:33 PM (18 years ago)
- Branches:
- clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- a702d3f
- Parents:
- 0de816f8
- Location:
- BOOK
- Files:
-
- 60 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/appendices/dependencies/common.xml
r0de816f8 rfb40919 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 purpose19 of this page is to document the dependencies of each package built in LFS.</para>18 order in which packages are built in CLFS is very important. The purpose 19 of this page is to document the dependencies of each package built in CLFS.</para> 20 20 21 21 <para>For each package we build, we have listed three types of dependencies. … … 76 76 <seg>Binutils, Bison, Bzip2, DejaGNU, Diffutils, Expect, Findutils, 77 77 Flex, GCC, Gettext, Gzip, Libtool and Tar. Can also use several 78 other packages that are not installed in LFS.</seg>78 other packages that are not installed in CLFS.</seg> 79 79 </seglistitem> 80 80 </segmentedlist> -
BOOK/boot/common/creatingdirs.xml
r0de816f8 rfb40919 11 11 <title>Creating Directories</title> 12 12 13 <para os="a">It is time to create some structure in the LFS file system. Create a13 <para os="a">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/boot/common/introduction.xml
r0de816f8 rfb40919 17 17 <para>There are a few additional packages that will need to be 18 18 installed to allow you to boot the minimal system. Some of these 19 packages will be installed onto the root or in /usr on the LFS19 packages will be installed onto the root or in /usr on the CLFS 20 20 partition ($LFS/bin, $LFS/usr/lib, etc...), rather than /tools, using the 21 21 "DESTDIR" option with make. This will require the -
BOOK/boot/x86_64-64/lilo.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="lilo.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-boot-lilo"> -
BOOK/bootable/alpha-chapter.xml
r0de816f8 rfb40919 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/alpha/aboot.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="aboot.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-bootable-aboot"> -
BOOK/bootable/common/introduction.xml
r0de816f8 rfb40919 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/bootable/mips-chapter.xml
r0de816f8 rfb40919 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/mips/arcload.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="arcload.html"?> 10 10 11 <title>Making the LFS System Bootable via Arcload</title>11 <title>Making the CLFS System Bootable via Arcload</title> 12 12 13 13 <indexterm zone="ch-bootable-arcload"> -
BOOK/bootable/mips/colo.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="colo.html"?> 10 10 11 <title>Making the LFS System Bootable via Colo</title>11 <title>Making the CLFS System Bootable via Colo</title> 12 12 13 13 <indexterm zone="ch-bootable-colo"> … … 21 21 </note> 22 22 23 <para os="c">Your shiny new LFS system is almost complete. One of the last23 <para os="c">Your shiny new CLFS system is almost complete. One of the last 24 24 things to do is ensure you can boot it. The instructions below apply 25 25 only to Cobalt RaQ1/RaQ2/Cube2 servers. Information on <quote>boot -
BOOK/bootable/mips64-chapter.xml
r0de816f8 rfb40919 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/mips64/arcload.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="arcload.html"?> 10 10 11 <title>Making the LFS System Bootable via Arcload</title>11 <title>Making the CLFS System Bootable via Arcload</title> 12 12 13 13 <indexterm zone="ch-bootable-arcload"> -
BOOK/bootable/ppc-chapter.xml
r0de816f8 rfb40919 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/ppc/yaboot.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="yaboot.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-bootable-yaboot"> … … 15 15 <secondary>configuring</secondary></indexterm> 16 16 17 <para os="a">Your shiny new LFS system is almost complete. One of the last17 <para os="a">Your shiny new CLFS system is almost complete. One of the last 18 18 things to do is to ensure that the system can be properly booted. The 19 19 instructions below apply only to NewWorld Macintoshes.</para> … … 107 107 fgcolor=light-green 108 108 109 # The first entry is for LFS.109 # The first entry is for CLFS. 110 110 # For all images, the pathname is relative to the filesystem 111 111 # on which they are situated and can include at most one -
BOOK/bootable/ppc64-chapter.xml
r0de816f8 rfb40919 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/sparc-chapter.xml
r0de816f8 rfb40919 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/sparc/silo.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="silo.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-bootable-silo"> -
BOOK/bootable/x86-chapter.xml
r0de816f8 rfb40919 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/x86/grub.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="grub.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-bootable-grub"> … … 16 16 </indexterm> 17 17 18 <para os="a">Your shiny new LFS system is almost complete. One of the last18 <para os="a">Your shiny new CLFS system is almost complete. One of the last 19 19 things to do is to ensure that the system can be properly booted. The 20 20 instructions below apply only to computers of IA-32 architecture, … … 71 71 a third party boot manager to manage the Master Boot Record (MBR). 72 72 In this scenario, it would make more sense to install GRUB into the 73 <quote>boot sector</quote> of the LFS partition. In this case, this73 <quote>boot sector</quote> of the CLFS partition. In this case, this 74 74 next command would become <userinput>setup (hd0,3)</userinput>.</para> 75 75 </warning> … … 101 101 color green/black light-green/black 102 102 103 # The first entry is for LFS.104 title LFS &version;103 # The first entry is for CLFS. 104 title CLFS &version; 105 105 root (hd0,3) 106 106 kernel /boot/lfskernel-&linux-version; root=/dev/hda4</literal> -
BOOK/bootable/x86/kernel.xml
r0de816f8 rfb40919 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 … … 144 144 <filename class="symlink">/usr/src/linux</filename> pointing to the 145 145 kernel source directory. This is specific to kernels prior to the 146 2.6 series and <emphasis>must not</emphasis> be created on a nLFS146 2.6 series and <emphasis>must not</emphasis> be created on a CLFS 147 147 system as it can cause problems for packages you may wish to build 148 once your base LFS system is complete.</para>148 once your base CLFS system is complete.</para> 149 149 150 150 <para>Also, the headers in the system's <filename -
BOOK/bootable/x86_64-64-chapter.xml
r0de816f8 rfb40919 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/x86_64-64/lilo.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="lilo.html"?> 10 10 11 <title>Making the LFS System Bootable</title>11 <title>Making the CLFS System Bootable</title> 12 12 13 13 <indexterm zone="ch-bootable-lilo"> … … 16 16 </indexterm> 17 17 18 <para os="a">Your shiny new LFS system is almost complete. One of the18 <para os="a">Your shiny new CLFS system is almost complete. One of the 19 19 last things to do is to ensure that the system can be properly 20 20 booted. The instructions below apply only to computers using lilo, -
BOOK/bootable/x86_64-chapter.xml
r0de816f8 rfb40919 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/bootscripts/common/console.xml
r0de816f8 rfb40919 27 27 url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. A pre-made 28 28 <filename>/etc/sysconfig/console</filename> file with known settings for 29 several countries was installed with the LFS-Bootscripts package, so the29 several countries was installed with the CLFS-Bootscripts package, so the 30 30 relevant section can be uncommented if the country is supported. If still 31 31 in doubt, look in the <filename class="directory">/usr/share/kbd</filename> -
BOOK/bootscripts/common/introduction.xml
r0de816f8 rfb40919 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/network.xml
r0de816f8 rfb40919 58 58 59 59 <para>The <envar>SERVICE</envar> variable defines the method used for 60 obtaining the IP address. The LFS-Bootscripts package has a modular IP60 obtaining the IP address. The CLFS-Bootscripts package has a modular IP 61 61 assignment format, and creating additional files in the <filename 62 62 class="directory">/etc/sysconfig/network-devices/services</filename> -
BOOK/bootscripts/common/profile.xml
r0de816f8 rfb40919 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/udev.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="udev.html"?> 10 10 11 <title>Device and Module Handling on a nLFS System</title>11 <title>Device and Module Handling on a CLFS System</title> 12 12 13 13 <indexterm zone="ch-scripts-udev"> … … 99 99 the rules specified in the files within the <filename 100 100 class="directory">/etc/udev/rules.d/</filename> directory. These are 101 numbered in a similar fashion to the LFS-Bootscripts package. If101 numbered in a similar fashion to the CLFS-Bootscripts package. If 102 102 <command>udev</command> can't find a rule for the device it is creating, 103 103 it will default permissions to <emphasis>660</emphasis> and ownership to … … 129 129 this method will not work because the device node does not exist until 130 130 the module is loaded. To solve this, the <command>S05modules</command> 131 bootscript was added to the LFS-Bootscripts package, along with the131 bootscript was added to the CLFS-Bootscripts package, along with the 132 132 <filename>/etc/sysconfig/modules</filename> file. By adding module 133 133 names to the <filename>modules</filename> file, these modules will be -
BOOK/bootscripts/common/usage.xml
r0de816f8 rfb40919 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/bootscripts/mips/bootscripts.xml
r0de816f8 rfb40919 9 9 <?dbhtml filename="bootscripts.html"?> 10 10 11 <title> LFS-Bootscripts-&lfs-bootscripts-version;</title>11 <title>CLFS-Bootscripts-&lfs-bootscripts-version;</title> 12 12 13 13 <indexterm zone="ch-scripts-bootscripts"> … … 20 20 21 21 <sect2 role="installation"> 22 <title>Installation of LFS-Bootscripts</title>22 <title>Installation of CLFS-Bootscripts</title> 23 23 24 24 <para>Need to update the current bootscripts to handle LCD -
BOOK/chroot/common/changingowner.xml
r0de816f8 rfb40919 17 17 class="directory">/tools</filename> and <filename 18 18 class="directory">/cross-tools</filename> directories can be deleted 19 once the LFS system has been finished, they can be retained to build20 additional LFS systems. If the <filename class="directory">/tools</filename>19 once the CLFS system has been finished, they can be retained to build 20 additional CLFS systems. If the <filename class="directory">/tools</filename> 21 21 and <filename class="directory">/cross-tools</filename> directories are 22 22 kept as is, the files are owned by a user ID without a corresponding … … 27 27 28 28 <para os="b">To avoid this issue, add the <systemitem 29 class="username">lfs</systemitem> user to the new LFS system later when29 class="username">lfs</systemitem> user to the new CLFS system later when 30 30 creating the <filename>/etc/passwd</filename> file, taking care to assign 31 31 it the same user and group IDs as on the host system. Alternatively, -
BOOK/chroot/common/chroot.xml
r0de816f8 rfb40919 12 12 13 13 <para>It is time to enter the chroot environment to begin building 14 and installing the final LFS system. As user <systemitem14 and installing the final CLFS system. As user <systemitem 15 15 class="username">root</systemitem>, run the following command to 16 16 enter the realm that is, at the moment, populated with only the … … 37 37 <para>From this point on, there is no need to use the 38 38 <envar>LFS</envar> variable anymore, because all work will be 39 restricted to the LFS file system. This is because the Bash shell is39 restricted to the CLFS file system. This is because the Bash shell is 40 40 told that <filename class="directory">$LFS</filename> is now the root 41 41 (<filename class="directory">/</filename>) directory.</para> -
BOOK/chroot/common/kernfs.xml
r0de816f8 rfb40919 30 30 mount -vt sysfs sysfs $LFS/sys</userinput></screen> 31 31 32 <para>Remember that if for any reason you stop working on the LFS system32 <para>Remember that if for any reason you stop working on the CLFS system 33 33 and start again later, it is important to check that these file systems 34 34 are mounted again before entering the chroot environment.</para> … … 44 44 nodes are created by the Udev package. Since this package is not 45 45 available to us right now, we must take other steps to provide device 46 nodes under on the LFS filesystem. We will use the <quote>bind</quote>46 nodes under on the CLFS filesystem. We will use the <quote>bind</quote> 47 47 option in the mount command to make our host system's /dev structure 48 appear in the new LFS filesystem:</para>48 appear in the new CLFS filesystem:</para> 49 49 50 50 <screen><userinput>/tools/bin/mount -o bind /dev $LFS/dev</userinput></screen> -
BOOK/final-preps/creatingtoolsdir.xml
r0de816f8 rfb40919 28 28 <para>The next step is to create a <filename class="symlink">/tools</filename> 29 29 symlink on the host system. This will point to the newly-created directory 30 on the LFS partition. Run this command as <systemitem30 on the CLFS partition. Run this command as <systemitem 31 31 class="username">root</systemitem> as well:</para> 32 32 -
BOOK/final-system/common/coreutils.xml
r0de816f8 rfb40919 81 81 ln -svf ../../bin/install /usr/bin</userinput></screen> 82 82 83 <para os="t">Some of the scripts in the LFS-Bootscripts package depend on83 <para os="t">Some of the scripts in the CLFS-Bootscripts package depend on 84 84 <command>head</command> and <command>sleep</command>. As <filename 85 85 class="directory">/usr</filename> may not be available during the early -
BOOK/final-system/common/e2fsprogs.xml
r0de816f8 rfb40919 70 70 Management System (EVMS) plugin. This plugin is not up-to-date with 71 71 the latest EVMS internal interfaces and EVMS is not installed as part 72 of a base LFS system, so the plugin is not required. See the EVMS72 of a base CLFS system, so the plugin is not required. See the EVMS 73 73 website at <ulink url="http://evms.sourceforge.net/"/> for more 74 74 information regarding EVMS.</para> -
BOOK/final-system/common/glibc.xml
r0de816f8 rfb40919 125 125 </listitem> 126 126 <listitem> 127 <para>If you have mounted the LFS partition with the127 <para>If you have mounted the CLFS partition with the 128 128 <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test 129 129 will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>, 130 130 do not use the <parameter>noatime</parameter> option while building 131 LFS.</para>131 CLFS.</para> 132 132 </listitem> 133 133 <listitem> … … 186 186 <para>Some locales installed by the <command>make 187 187 localedata/install-locales</command> command above are not properly 188 supported by some applications that are in the LFS and BLFS books. Because188 supported by some applications that are in the CLFS and BLFS books. Because 189 189 of the various problems that arise due to application programmers making 190 assumptions that break in such locales, LFS should not be used in locales190 assumptions that break in such locales, CLFS should not be used in locales 191 191 that utilize multibyte character sets (including UTF-8) or right-to-left 192 192 writing order. Numerous unofficial and unstable patches are required to 193 fix these problems, and it has been decided by the LFS developers not to193 fix these problems, and it has been decided by the CLFS developers not to 194 194 support such complex locales at this time. This applies to the ja_JP and 195 195 fa_IR locales as well—they have been installed only for GCC and -
BOOK/final-system/common/inetutils.xml
r0de816f8 rfb40919 79 79 <para>This disables the installation of the various network 80 80 servers included as part of the Inetutils package. These servers are 81 deemed not appropriate in a basic LFS system. Some are insecure by81 deemed not appropriate in a basic CLFS system. Some are insecure by 82 82 nature and are only considered safe on trusted networks. More 83 83 information can be found at <ulink -
BOOK/final-system/common/iproute2.xml
r0de816f8 rfb40919 49 49 <filename class="directory">/sbin</filename>. This is the correct 50 50 location according to the FHS, because some of the IPRoute2 binaries 51 are used by the LFS-Bootscripts package.</para>51 are used by the CLFS-Bootscripts package.</para> 52 52 </listitem> 53 53 </varlistentry> -
BOOK/final-system/common/kbd.xml
r0de816f8 rfb40919 296 296 <listitem> 297 297 <para>Puts the keyboard and console in UNICODE mode. Never use it on 298 LFS, because applications are not configured to support UNICODE.</para>298 CLFS, because applications are not configured to support UNICODE.</para> 299 299 <indexterm zone="ch-system-kbd unicode_start"> 300 300 <primary sortas="b-unicode_start">unicode_start</primary> -
BOOK/final-system/common/man.xml
r0de816f8 rfb40919 103 103 non-ISO 8859-1 locales. Also, it does not work with multibyte 104 104 character sets. The first problem does not currently have a solution. 105 The second issue is not of concern because the LFS installation does105 The second issue is not of concern because the CLFS installation does 106 106 not support multibyte character sets.</para> 107 107 -
BOOK/final-system/common/psmisc.xml
r0de816f8 rfb40919 40 40 <filename class="directory">/usr/bin</filename>. This is the 41 41 correct location according to the FHS, because some of the Psmisc 42 binaries are used by the LFS-Bootscripts package.</para>42 binaries are used by the CLFS-Bootscripts package.</para> 43 43 </listitem> 44 44 </varlistentry> -
BOOK/final-system/common/sysvinit.xml
r0de816f8 rfb40919 98 98 character set to a user-defined one, which can be modified by running 99 99 the <command>setfont</command> program. The <command>console</command> 100 initscript from the LFS-Bootscripts package calls the100 initscript from the CLFS-Bootscripts package calls the 101 101 <command>setfont</command> program during system startup. Sending this 102 102 escape sequence is necessary for people who use non-ISO 8859-1 screen -
BOOK/final-system/common/udev.xml
r0de816f8 rfb40919 177 177 <para>Simulates a <command>udev</command> run for the given device, 178 178 and prints out the name of the node the real <command>udev</command> 179 would have created or (not in LFS) the name of the renamed network179 would have created or (not in CLFS) the name of the renamed network 180 180 interface</para> 181 181 <indexterm zone="ch-system-udev udevtest"> -
BOOK/final-system/common/util-linux.xml
r0de816f8 rfb40919 91 91 <para os="g">Install the package and move the <command>logger</command> binary 92 92 to <filename class="directory">/bin</filename> as it is needed by the 93 LFS-Bootscripts package:</para>93 CLFS-Bootscripts package:</para> 94 94 95 95 <screen os="h"><userinput>make HAVE_KILL=yes HAVE_SLN=yes install -
BOOK/final-system/common/vim.xml
r0de816f8 rfb40919 100 100 <screen os="o"><userinput>ln -sv ../vim/vim&vim-version2;/doc /usr/share/doc/vim-&vim-version;</userinput></screen> 101 101 102 <para os="p">If an X Window System is going to be installed on the LFS102 <para os="p">If an X Window System is going to be installed on the CLFS 103 103 system, you may want to recompile Vim after installing X. Vim 104 104 comes with a GUI version of the editor that requires X and some … … 376 376 necessary to highlight in <command>vim</command>. This script 377 377 requires the old Unix <command>spell</command> command, which 378 is provided neither in LFS nor in BLFS</para>378 is provided neither in CLFS nor in BLFS</para> 379 379 <indexterm zone="ch-system-vim vimspell.sh"> 380 380 <primary sortas="b-vimspell.sh">vimspell.sh</primary> -
BOOK/final-system/multilib/glibc-64bit.xml
r0de816f8 rfb40919 124 124 </listitem> 125 125 <listitem> 126 <para>If you have mounted the LFS partition with the126 <para>If you have mounted the CLFS partition with the 127 127 <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test 128 128 will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>, 129 129 do not use the <parameter>noatime</parameter> option while building 130 LFS.</para>130 CLFS.</para> 131 131 </listitem> 132 132 <listitem> -
BOOK/final-system/ppc64/glibc-64bit.xml
r0de816f8 rfb40919 135 135 </listitem> 136 136 <listitem> 137 <para>If you have mounted the LFS partition with the137 <para>If you have mounted the CLFS partition with the 138 138 <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test 139 139 will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>, 140 140 do not use the <parameter>noatime</parameter> option while building 141 LFS.</para>141 CLFS.</para> 142 142 </listitem> 143 143 <listitem> -
BOOK/introduction/common/askforhelp.xml
r0de816f8 rfb40919 44 44 <listitem> 45 45 <para>The host distribution and version being used to 46 create LFS</para>46 create CLFS</para> 47 47 </listitem> 48 48 <listitem> -
BOOK/introduction/common/changelog.xml
r0de816f8 rfb40919 37 37 --> 38 38 39 <listitem> 40 <para>June 21, 2006</para> 41 <itemizedlist> 42 <listitem> 43 <para>[Chris] - Text updates to the book, including replacing 44 "LFS" with "CLFS".</para> 45 </listitem> 46 </itemizedlist> 47 </listitem> 39 48 40 49 <listitem> -
BOOK/introduction/common/resources.xml
r0de816f8 rfb40919 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) -
BOOK/materials/common/patches.xml
r0de816f8 rfb40919 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"> … … 299 299 300 300 <para>In addition to the above required patches, there exist a number of 301 optional patches created by the LFS community. These optional patches301 optional patches created by the CLFS community. These optional patches 302 302 solve minor problems or enable functionality that is not enabled by 303 303 default. Feel free to peruse the patches database located at -
BOOK/partitioning/common/creatingfilesystem.xml
r0de816f8 rfb40919 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> 25 25 26 <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the LFS26 <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the CLFS 27 27 partition (<filename class="devicefile">hda5</filename> in our previous 28 28 example).</para> … … 31 31 <para>Some host distributions use custom features in their filesystem 32 32 creation tools (E2fsprogs). This can cause problems when booting into 33 your new LFS, as those features will not be supported by the LFS-installed34 E2fsprogs; you will get an error similar to <computeroutput>unsupported35 filesystem features, upgrade your e2fsprogs</computeroutput>. To check36 if your host system uses custom enhancements, run the following37 command:</para>33 your new CLFS system, as those features will not be supported by the 34 CLFS-installed E2fsprogs; you will get an error similar to 35 <computeroutput>unsupported filesystem features, upgrade your 36 e2fsprogs</computeroutput>. To check if your host system uses custom 37 enhancements, run the following command:</para> 38 38 39 39 <screen os="f"><userinput>debugfs -R feature /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
r0de816f8 rfb40919 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
r0de816f8 rfb40919 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/prologue/common/errata.xml
r0de816f8 rfb40919 13 13 <para>The software used to create a CLFS system is constantly being 14 14 updated and enhanced. Security warnings and bug fixes may become 15 available after the LFS book has been released. To check whether the 16 package versions or instructions in this release of CLFS need any 17 modifications to accommodate security vulnerabilities or other bug fixes, 18 please visit <ulink url="&errata;"/> before proceeding with your build. 19 You should note any changes shown and apply them to the relevant section 20 of the book as you progress with building the LFS system.</para> 15 available after the CLFS book has been released. Some host systems may 16 also have problems building CLFS. To check whether the package versions 17 or instructions in this release of CLFS need any modifications to 18 accommodate security vulnerabilities, other bug fixes, or host-specific 19 issues, please visit <ulink url="&errata;"/> before proceeding with your 20 build. You should note any changes shown and apply them to the relevant 21 section of the book as you progress with building the CLFS system.</para> 21 22 22 23 </sect1> -
BOOK/prologue/common/prerequisites.xml
r0de816f8 rfb40919 23 23 24 24 <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic 25 level of skill, the various LFS support forums are unlikely to be able to25 level of skill, the various CLFS support forums are unlikely to be able to 26 26 provide you with much assistance; you will find that your questions regarding 27 27 such basic knowledge will likely go unanswered, or you will simply be referred -
BOOK/prologue/common/typography.xml
r0de816f8 rfb40919 13 13 <para>To make things easier to follow, there are a few typographical 14 14 conventions used throughout this book. This section contains some 15 examples of the typographical format found throughout Linux From16 Scratch.</para>15 examples of the typographical format found throughout Cross-Compiled 16 Linux From Scratch.</para> 17 17 18 18 <screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen> … … 36 36 <para><ulink url="&lfs-root;"/></para> 37 37 38 <para>This format is used for hyperlinks, both within the LFS38 <para>This format is used for hyperlinks, both within the CLFS 39 39 community and to external pages. It includes HOWTOs, download locations, 40 40 and websites.</para> … … 62 62 referred to simply as a <quote>man</quote> page). The number inside 63 63 parentheses indicates a specific section inside of <command>man</command>. 64 For example, <command>passwd</command> has two man pages. Per LFS64 For example, <command>passwd</command> has two man pages. Per CLFS 65 65 installation instructions, those two man pages will be located at 66 66 <filename>/usr/share/man/man1/passwd.1</filename> and -
BOOK/the-end/reboot.xml
r0de816f8 rfb40919 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 $LFS/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 $LFS</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
r0de816f8 rfb40919 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 a nLFS system is compiled from source, it is up to you to keep27 Since a 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> … … 65 65 66 66 <para>The Beyond Linux From Scratch book covers installation 67 procedures for a wide range of software beyond the scope of the LFS67 procedures for a wide range of software beyond the scope of the CLFS 68 68 Book. The BLFS project is located at <ulink url="&blfs-root;"/>.</para> 69 69 </listitem>
Note:
See TracChangeset
for help on using the changeset viewer.