- Timestamp:
- Jul 20, 2006, 1:22:52 PM (18 years ago)
- Branches:
- master
- Children:
- cc23f19
- Parents:
- beea2b3
- Location:
- BOOK
- Files:
-
- 19 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/appendices/dependencies/common.xml
rbeea2b3 r1a09536 17 17 which in turn depends on the first. Because of these dependencies, the 18 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 LFS.</para>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/bootable/arm/kernel.xml
rbeea2b3 r1a09536 126 126 <filename class="symlink">/usr/src/linux</filename> pointing to the 127 127 kernel source directory. This is specific to kernels prior to the 128 2.6 series and <emphasis>must not</emphasis> be created on an LFS128 2.6 series and <emphasis>must not</emphasis> be created on an CLFS 129 129 system as it can cause problems for packages you may wish to build 130 130 once your base CLFS system is complete.</para> -
BOOK/bootable/common/chowning.xml
rbeea2b3 r1a09536 26 26 27 27 <para>Make <systemitem class="username">root</systemitem> the owner of the 28 entire lfssystem.</para>28 entire CLFS system.</para> 29 29 30 30 <screen><userinput>chown -Rv root:root ${CLFS}</userinput></screen> -
BOOK/bootscripts/common/console.xml
rbeea2b3 r1a09536 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/network.xml
rbeea2b3 r1a09536 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/udev.xml
rbeea2b3 r1a09536 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/final-preps/addinguser.xml
rbeea2b3 r1a09536 61 61 62 62 <varlistentry> 63 <term><parameter> lfs</parameter></term>63 <term><parameter>clfs</parameter></term> 64 64 <listitem> 65 65 <para>This is the actual name for the created group and user.</para> … … 80 80 <para>Grant <systemitem class="username">clfs</systemitem> full access to 81 81 <filename class="directory">$CLFS</filename> by making <systemitem 82 class="username"> lfs</systemitem> the directory's owner:</para>82 class="username">clfs</systemitem> the directory's owner:</para> 83 83 84 84 <screen><userinput>chown -Rv clfs $CLFS</userinput></screen> -
BOOK/final-system/arm/kbd.xml
rbeea2b3 r1a09536 319 319 <listitem> 320 320 <para>Puts the keyboard and console in UNICODE mode. Never use it on 321 LFS, because applications are not configured to support UNICODE.</para>321 CLFS, because applications are not configured to support UNICODE.</para> 322 322 <indexterm zone="ch-system-kbd unicode_start"> 323 323 <primary sortas="b-unicode_start">unicode_start</primary> -
BOOK/final-system/common/iproute2.xml
rbeea2b3 r1a09536 57 57 <filename class="directory">/sbin</filename>. This is the correct 58 58 location according to the FHS, because some of the IPRoute2 binaries 59 are used by the LFS-Bootscripts package.</para>59 are used by the CLFS-Bootscripts package.</para> 60 60 </listitem> 61 61 </varlistentry> -
BOOK/final-system/common/psmisc.xml
rbeea2b3 r1a09536 41 41 <filename class="directory">/usr/bin</filename>. This is the 42 42 correct location according to the FHS, because some of the Psmisc 43 binaries are used by the LFS-Bootscripts package.</para>43 binaries are used by the CLFS-Bootscripts package.</para> 44 44 </listitem> 45 45 </varlistentry> -
BOOK/final-system/common/shadow.xml
rbeea2b3 r1a09536 111 111 dictionary:</para> 112 112 113 <screen role="nodump"><userinput>cp {LFS}/etc/login.defs login.defs.orig113 <screen role="nodump"><userinput>cp ${CLFS}/etc/login.defs login.defs.orig 114 114 sed 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@' login.defs.orig > ${CLFS}/etc/login.defs</userinput></screen> 115 115 </note> -
BOOK/final-system/common/sysvinit.xml
rbeea2b3 r1a09536 108 108 character set to a user-defined one, which can be modified by running 109 109 the <command>setfont</command> program. The <command>console</command> 110 initscript from the LFS-Bootscripts package calls the110 initscript from the CLFS-Bootscripts package calls the 111 111 <command>setfont</command> program during system startup. Sending this 112 112 escape sequence is necessary for people who use non-ISO 8859-1 screen -
BOOK/final-system/common/udev.xml
rbeea2b3 r1a09536 155 155 <para>Simulates a <command>udev</command> run for the given device, 156 156 and prints out the name of the node the real <command>udev</command> 157 would have created or (not in LFS) the name of the renamed network157 would have created or (not in CLFS) the name of the renamed network 158 158 interface</para> 159 159 <indexterm zone="ch-system-udev udevtest"> -
BOOK/final-system/common/util-linux.xml
rbeea2b3 r1a09536 118 118 <para os="f">Install the package and move the <command>logger</command> binary 119 119 to <filename class="directory">/bin</filename> as it is needed by the 120 LFS-Bootscripts package:</para>120 CLFS-Bootscripts package:</para> 121 121 122 122 <screen os="g"><userinput>make HAVE_KILL=yes HAVE_SLN=yes \ -
BOOK/final-system/common/vim.xml
rbeea2b3 r1a09536 104 104 <screen os="n"><userinput>ln -sv ../vim/vim&vim-version2;/doc ${CLFS}/usr/share/doc/vim-&vim-version;</userinput></screen> 105 105 106 <para os="o">If an X Window System is going to be installed on the LFS106 <para os="o">If an X Window System is going to be installed on the CLFS 107 107 system, you may want to recompile Vim after installing X. Vim 108 108 comes with a GUI version of the editor that requires X and some -
BOOK/partitioning/common/creatingfilesystem.xml
rbeea2b3 r1a09536 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-installed33 your new CLFS, as those features will not be supported by the LFS-installed 34 34 E2fsprogs; you will get an error similar to <computeroutput>unsupported 35 35 filesystem features, upgrade your e2fsprogs</computeroutput>. To check -
BOOK/partitioning/common/mounting.xml
rbeea2b3 r1a09536 18 18 to you.</para> 19 19 20 <para>Choose a mount point and assign it to the <envar> LFS</envar>20 <para>Choose a mount point and assign it to the <envar>CLFS</envar> 21 21 environment variable by running:</para> 22 22 -
BOOK/prologue/common/errata.xml
rbeea2b3 r1a09536 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 the15 available after the CLFS book has been released. To check whether the 16 16 package versions or instructions in this release of CLFS need any 17 17 modifications to accommodate security vulnerabilities or other bug fixes, 18 18 please visit <ulink url="&errata;"/> before proceeding with your build. 19 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>20 of the book as you progress with building the CLFS system.</para> 21 21 22 22 </sect1> -
BOOK/prologue/common/typography.xml
rbeea2b3 r1a09536 36 36 <para><ulink url="&clfs-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
Note:
See TracChangeset
for help on using the changeset viewer.