Changeset 4642c89 for chapter03/introduction.xml
- Timestamp:
- 01/30/2005 10:28:53 AM (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:
- 155d6d1
- Parents:
- d7ea6f24
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/introduction.xml
rd7ea6f24 r4642c89 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <!-- 11 <para>Below is a list of packages you need to download for building a basic 12 Linux system. The listed version numbers correspond to versions of the 13 software that are <emphasis>known</emphasis> to work, and this book is 14 based upon them. Unless you are an experienced LFS builder, we highly 15 recommend not to try out newer versions, as the build commands for one 16 version may not work with a newer version. Also, there is often a good 17 reason for not using the latest version due to known problems that haven't 18 been worked around yet.</para> 19 20 <para>All the URLs, when possible, refer to the project's page at 21 <ulink url="http://www.freshmeat.net/"/>. The Freshmeat 22 pages will give you easy access to the official download sites as well as 23 project websites, mailing lists, FAQs, changelogs and more.</para> 24 25 <para>We can't guarantee that these download locations are always available. 26 In case a download location has changed since this book was published, please 27 try to google for the package. Should you remain unsuccessful with this, 28 try one of the alternative means of downloading listed on 29 <ulink url="&lfs-root;lfs/packages.html"/>.</para> 30 31 <para>You'll need to store all the downloaded packages and patches somewhere 32 that is conveniently available throughout the entire build. You'll also need a 33 working directory in which to unpack the sources and build them. A scheme that 34 works well is to use <filename class="directory">$LFS/sources</filename> as the place to store 35 the tarballs and patches, <emphasis>and</emphasis> as a working directory. 36 This way everything you need will be located on the LFS partition and available 37 during all stages of the building process.</para> 38 39 <para>So you may want to execute, as <emphasis>root</emphasis>, the following 40 command before starting your download session:</para> 41 --> 10 <para>Create a dir for the sources:</para> 42 11 43 12 <screen><userinput>mkdir $LFS/sources</userinput></screen> 44 13 45 <!-- 46 <para>And make this directory writable (and sticky) for your normal user - as 47 you won't do the downloading as <emphasis>root</emphasis>, we guess:</para> 48 --> 14 <para>Set the permissions of that dir:</para> 49 15 50 16 <screen><userinput>chmod a+wt $LFS/sources</userinput></screen> 51 17 52 <!--53 <para>For your convenience the top of the list contains a link to a file54 you can use with the <ulink url="http://wget.sunsite.dk">wget</ulink>55 program. Using this file and the <command>wget</command> program will56 make it easy to download all the files at once, rather than downloading each57 and every individual file manually.</para>58 -->59 60 18 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.