source: chapter03/introduction.xml@ afcfd74

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 9.1 9.1-rc1 arm cross-chap5 ml-11.0 multilib old-trunk s6-init trunk xry111/arm64 xry111/clfs-ng xry111/git-transition xry111/glibc-2.34 xry111/glibc-2.37 xry111/kcfg-revise xry111/lfs-next xry111/pip3 xry111/queue-11.3 xry111/rust-wip-20221008 xry111/tester-nohack xry111/usr-move
Last change on this file since afcfd74 was afcfd74, checked in by Pierre Labastie <pieere@…>, 3 years ago

Remove unused files and make
idref's more regular

git-svn-id: 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.1 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<sect1 id="ch-materials-introduction">
9 <?dbhtml filename="introduction.html"?>
11 <title>Introduction</title>
13 <para>This chapter includes a list of packages that need to be downloaded in
14 order to build a basic Linux system. The listed version numbers correspond to
15 versions of the software that are known to work, and this book is based on
16 their use. We highly recommend against using newer versions because the build
17 commands for one version may not work with a newer version. The newest package
18 versions may also have problems that require work-arounds. These work-arounds
19 will be developed and stabilized in the development version of the
20 book.</para>
22 <para>Download locations may not always be accessible. If a download
23 location has changed since this book was published, Google (<ulink
24 url=""/>) provides a useful search engine for
25 most packages. If this search is unsuccessful, try one of the
26 alternative means of downloading discussed at <ulink
27 url="&lfs-root;lfs/packages.html#packages"/>. </para>
29 <para>Downloaded packages and patches will need to be stored somewhere
30 that is conveniently available throughout the entire build. A working
31 directory is also required to unpack the sources and build them.
32 <filename class="directory">$LFS/sources</filename> can be used both
33 as the place to store the tarballs and patches and as a working
34 directory. By using this directory, the required elements will be
35 located on the LFS partition and will be available during all stages
36 of the building process.</para>
38 <para>To create this directory, execute the following command, as user
39 <systemitem class="username">root</systemitem>, before starting the download
40 session:</para>
42<screen role="nodump"><userinput>mkdir -v $LFS/sources</userinput></screen>
44 <para>Make this directory writable and sticky. <quote>Sticky</quote>
45 means that even if multiple users have write permission on a
46 directory, only the owner of a file can delete the file within a
47 sticky directory. The following command will enable the write and
48 sticky modes:</para>
50<screen role="nodump"><userinput>chmod -v a+wt $LFS/sources</userinput></screen>
52 <para>An easy way to download all of the packages and patches is by using
53 <ulink url="../wget-list">wget-list</ulink> as an input to
54 <command>wget</command>. For example:</para>
56<screen role="nodump"><userinput>wget --input-file=wget-list --continue --directory-prefix=$LFS/sources</userinput></screen>
58 <para>Additionally, starting with LFS-7.0, there is a separate file,
59 <ulink url="../md5sums">md5sums</ulink>, which can be used to verify that all
60 the correct packages are available before proceeding. Place that file in
61 <filename class="directory">$LFS/sources</filename> and run:</para>
63<screen role="nodump"><userinput>pushd $LFS/sources
64md5sum -c md5sums
Note: See TracBrowser for help on using the repository browser.