- Timestamp:
- 08/29/2004 06:36:34 PM (20 years ago)
- Branches:
- 6.0
- Children:
- 8b320e7
- Parents:
- ec0a37e6
- Location:
- chapter03
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/introduction.xml
rec0a37e6 r69993f4 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <para> Below is a list of packages that need to be download for building a11 basic Linux system. The listed version numbers correspond to versions12 of the software that are known to work, and this book is based on 13 th eir use. We highly recommend not using newer versions, as the build14 commands for one version may not work with a newer version. The newest 15 package versions may also have problems that work-arounds have 16 not been developed for yet.</para>10 <para>This chapter includes a list of packages that need to be 11 download for building a basic Linux system. The listed version numbers 12 correspond to versions of the software that are known to work, and 13 this book is based on their use. We highly recommend not using newer 14 versions because the build commands for one version may not work with 15 a newer version. The newest package versions may also have problems 16 that work-arounds have not been developed for yet.</para> 17 17 18 18 <para>All the URLs, when possible, refer to the package's information 19 19 page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages 20 20 provide easy access to official download sites, as well as project 21 websites, mailing lists, FAQ s, changelogs, and more.</para>21 websites, mailing lists, FAQ, changelogs, and more.</para> 22 22 23 23 <para>Download locations may not always be accessible. If a download … … 28 28 url="&lfs-root;lfs/packages.html"/>.</para> 29 29 30 <para>Downloaded packages and patches will need to be store ssomewhere30 <para>Downloaded packages and patches will need to be stored somewhere 31 31 that is conveniently available throughout the entire build. A working 32 32 directory is also required to unpack the sources and build them. … … 43 43 <screen><userinput>mkdir $LFS/sources</userinput></screen> 44 44 45 <para>Make this directory writable (and sticky -- which basically 46 means that eventhough a user may have write permissions on a 47 directory, the sticky tag prevents users from removing files they do 48 not own as normally write permission on a directory means the owner of 49 the directory can remove all files in it, even if he does not own the 50 file) for your normal user -- as you won't do the downloading as root, we 51 guess:</para> 45 <para>Make this directory writable and sticky. <quote>Sticky</quote> 46 means that even if multiple users have write permission on a 47 directory, only the owner of a file can delete the file within a 48 sticky directory. The following command will enable the write and 49 sticky modes:</para> 52 50 53 51 <screen><userinput>chmod a+wt $LFS/sources</userinput></screen> -
chapter03/packages.xml
rec0a37e6 r69993f4 11 11 12 12 <variablelist role="materials"> 13 <bridgehead renderas="sect3">Packages</bridgehead> 14 15 <varlistentry> 16 <term>Autoconf (&autoconf-version;) - 903 KB:</term> 13 14 <varlistentry> 15 <term>Autoconf (&autoconf-version;) - 903 kilobytes (KB):</term> 17 16 <listitem> 18 17 <para><ulink url="&freshmeat;autoconf/"/></para> … … 91 90 92 91 <varlistentry> 93 <term>File (&file-version;) - 356 KB: -- <emphasis>(see Note 1 below)</emphasis></term>92 <term>File (&file-version;) - 356 KB: <emphasis>(see Note 1)</emphasis></term> 94 93 <listitem> 95 94 <para><ulink url="&freshmeat;file/"/></para> … … 119 118 120 119 <varlistentry> 121 <term>GCC (&gcc-version;) - ~27,000KB:</term>120 <term>GCC (&gcc-version;) - 27,000 KB:</term> 122 121 <listitem> 123 122 <para><ulink url="&freshmeat;gcc/"/></para> … … 133 132 134 133 <varlistentry> 135 <term>Glibc (&glibc-version;) - 13,101 KB: -- <emphasis>(see Note 2 below)</emphasis></term>134 <term>Glibc (&glibc-version;) - 13,101 KB: <emphasis>(see Note 2)</emphasis></term> 136 135 <listitem> 137 136 <para><ulink url="&freshmeat;glibc/"/></para> … … 424 423 425 424 <note><para>2) Released packages of Glibc are not new enough for our 426 purposes, so create a tarball of an appropriate CVS with the following 425 purposes, so create a tarball of an appropriate Concurrent Versions 426 System (CVS) snapshot with the following 427 427 commands:</para> 428 428 … … 433 433 tar jcvf glibc-2.3.4-20040701.tar.bz2 glibc-2.3.4-20040701</userinput></screen> 434 434 435 <para> 436 Alternatively, the LFS team developed a tarball which can be 437 downloaded from any of the FTP mirrors listed on the LFS Website at 438 <ulink url="&lfs-root;lfs/packages.html#http"/>. It 439 is located under the <filename 440 class="directory">/pub/lfs/packages/conglomeration/glibc</filename> directory. 441 The tarball is signed using GPG, and it is strongly recommended that 442 its authenticity be verified before use. Instructions for installing 443 GnuPG, which enables verification, are provided in the BLFS 444 book at <ulinkurl="&lfs-root;blfs/view/stable/postlfs/gnupg.html"/>.</para></note>435 <para> Alternatively, the LFS team developed a tarball which can be 436 downloaded from any of the File Transfer Protocol (FTP) mirrors listed 437 on the LFS Website at <ulink url="&lfs-root;lfs/packages.html#http"/>. 438 It is located under the <filename 439 class="directory">/pub/lfs/packages/conglomeration/glibc</filename> 440 directory. The tarball is signed using GNU Privacy Guard (GPG), and 441 it is strongly recommended that its authenticity be verified before 442 use. Instructions for installing GPG, which enables verification, are 443 provided in the Beyond Linux From Scratch (BLFS) book at <ulink 444 url="&lfs-root;blfs/view/stable/postlfs/gnupg.html"/>.</para></note> 445 445 446 446 </sect1> -
chapter03/patches.xml
rec0a37e6 r69993f4 5 5 ]> 6 6 <sect1 id="materials-patches"> 7 <title>Needed patches</title>7 <title>Needed Patches</title> 8 8 <?dbhtml filename="patches.html"?> 9 9 … … 15 15 16 16 <variablelist role="materials"> 17 <bridgehead renderas="sect3">Patches</bridgehead>18 17 19 18 <varlistentry>
Note:
See TracChangeset
for help on using the changeset viewer.