Ignore:
Timestamp:
02/19/2005 10:16:42 PM (19 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
3d31fc4
Parents:
2f9131f
Message:

Trunk is now identical to Testing

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4648 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter03/introduction.xml

    r2f9131f r81fd230  
    88<?dbhtml filename="introduction.html"?>
    99
    10 <para>Create a dir for the sources:</para>
     10<para>This chapter includes a list of packages that need to be
     11downloaded for building a basic Linux system. The listed version numbers
     12correspond to versions of the software that are known to work, and
     13this book is based on their use. We highly recommend not using newer
     14versions because the build commands for one version may not work with
     15a newer version. The newest package versions may also have problems
     16that work-arounds have not been developed for yet.</para>
     17
     18<para>All the URLs, when possible, refer to the package's information
     19page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages
     20provide easy access to official download sites, as well as project
     21websites, mailing lists, FAQ, changelogs, and more.</para>
     22
     23<para>Download locations may not always be accessible. If a download
     24location has changed since this book was published, Google (<ulink
     25url="http://www.google.com"/>) provides a useful search engine for
     26most packages. If this search is unsuccessful, try one of the
     27alternate means of downloading discussed at <ulink
     28url="&lfs-root;lfs/packages.html"/>.</para>
     29
     30<para>Downloaded packages and patches will need to be stored somewhere
     31that is conveniently available throughout the entire build. A working
     32directory is also required to unpack the sources and build them.
     33<filename class="directory">$LFS/sources</filename> can be used both
     34as the place to store the tarballs and patches and as a working
     35directory. By using this directory, the required elements will be
     36located on the LFS partition and will be available during all stages
     37of the building process.</para>
     38
     39<para>To create this directory, execute, as user
     40<emphasis>root</emphasis>, the following command before starting the
     41download session:</para>
    1142
    1243<screen><userinput>mkdir $LFS/sources</userinput></screen>
    1344
    14 <para>Set the permissions of that dir:</para>
     45<para>Make this directory writable and sticky. <quote>Sticky</quote>
     46means that even if multiple users have write permission on a
     47directory, only the owner of a file can delete the file within a
     48sticky directory. The following command will enable the write and
     49sticky modes:</para>
    1550
    1651<screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
    1752
    1853</sect1>
     54
Note: See TracChangeset for help on using the changeset viewer.