Changeset 81fd230 for chapter03/introduction.xml
- Timestamp:
- 02/19/2005 10:16:42 PM (19 years ago)
- 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
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/introduction.xml
r2f9131f r81fd230 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <para>Create a dir for the sources:</para> 10 <para>This chapter includes a list of packages that need to be 11 downloaded 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 18 <para>All the URLs, when possible, refer to the package's information 19 page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages 20 provide easy access to official download sites, as well as project 21 websites, mailing lists, FAQ, changelogs, and more.</para> 22 23 <para>Download locations may not always be accessible. If a download 24 location has changed since this book was published, Google (<ulink 25 url="http://www.google.com"/>) provides a useful search engine for 26 most packages. If this search is unsuccessful, try one of the 27 alternate means of downloading discussed at <ulink 28 url="&lfs-root;lfs/packages.html"/>.</para> 29 30 <para>Downloaded packages and patches will need to be stored somewhere 31 that is conveniently available throughout the entire build. A working 32 directory is also required to unpack the sources and build them. 33 <filename class="directory">$LFS/sources</filename> can be used both 34 as the place to store the tarballs and patches and as a working 35 directory. By using this directory, the required elements will be 36 located on the LFS partition and will be available during all stages 37 of the building process.</para> 38 39 <para>To create this directory, execute, as user 40 <emphasis>root</emphasis>, the following command before starting the 41 download session:</para> 11 42 12 43 <screen><userinput>mkdir $LFS/sources</userinput></screen> 13 44 14 <para>Set the permissions of that dir:</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> 15 50 16 51 <screen><userinput>chmod a+wt $LFS/sources</userinput></screen> 17 52 18 53 </sect1> 54
Note:
See TracChangeset
for help on using the changeset viewer.