Changeset fada431
- Timestamp:
- 08/29/2001 04:56:32 PM (23 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.0, 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, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, 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:
- 73ae3f2b
- Parents:
- bc831b5
- Files:
-
- 7 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/how.xml
rbc831b5 rfada431 15 15 packages that are statically linked and installed on the LFS partition. 16 16 These packages form a basic development suite which will be used to 17 install the actual system.</para> 17 install the actual system, and are also needed to resolve circular 18 dependencies. Examples of circular dependencies are: you need a compiler 19 to install a compiler. You need a shell in order to install a shell. And 20 so on.</para> 18 21 19 <para>Chapter 6 installs the actual base system. We use the chroot program to20 start a new shell who'sroot directory will be set to the LFS22 <para>Chapter 6 installs the actual base system. We use the chroot program 23 to start a new shell whose root directory will be set to the LFS 21 24 partition. This, in essence, is the same as rebooting and have the 22 25 kernel mount the LFS partition as the root partition. The reason that … … 24 27 still use your host system. While software is being installed you can 25 28 simply switch to a different VC (Virtual Console) or X desktop and 26 continue using your computer .</para>29 continue using your computer as you normally would.</para> 27 30 28 31 <para>When all the software is installed, chapter 7 will setup the boot 29 scripts. Chapter 8 will setup the Linux boot loader and you can finally 30 reboot your system into your new LFS-system.</para> 32 scripts. Chapter 8 will setup the Linux boot loader and in chapter 9 33 there are some pointers what you can do after you finish the book. Then 34 you can finally reboot your system into your new LFS system, and start 35 to really use it.</para> 31 36 32 37 <para>This is the process in a nutshell. Detailed information on the steps -
chapter01/versions.xml
rbc831b5 rfada431 3 3 4 4 <para>This is LFS-BOOK version &version; dated &releasedate;. If this 5 version is older than a month a newer version might be available for download 6 at the LFS homepage.</para> 5 version is older than a month a newer version is probably already available 6 for download. Check one of the mirror sites below for updated 7 versions.</para> 7 8 8 9 <para>Below is a list of our current HTTP and FTP mirror sites as 9 of August 2 7th, 2001. This list might not be accurate anymore.10 of August 29th, 2001. This list might not be accurate anymore. 10 11 The latest info can be found on our website at 11 12 <ulink url="http://www.linuxfromscratch.org">http://www.linuxfromscratch.org</ulink>.</para> -
chapter02/aboutlfs.xml
rbc831b5 rfada431 4 4 <para>Please read the following carefully: throughout this book 5 5 the variable $LFS will be used frequently. $LFS must at all times be 6 replaced bythe directory where the partition that contains the LFS system6 replaced with the directory where the partition that contains the LFS system 7 7 is mounted. How to create and where to mount the partition will be 8 explained in full detail in chapter 4. In my case, the LFS9 partition is mountedon /mnt/lfs.</para>8 explained in full detail in chapter 4. For example, let's assume that 9 the LFS partition is mounted on /mnt/lfs.</para> 10 10 11 11 <para>For example when you are told to run a command like … … 17 17 18 18 <para>A possible solution is to set the environment variable LFS. 19 This way $LFS can be entered literally instead of replacing it by19 This way $LFS can be entered literally instead of replacing it with 20 20 /mnt/lfs. This is accomplished by running <userinput>export 21 21 LFS=/mnt/lfs</userinput>.</para> -
chapter02/bootscripts.xml
rbc831b5 rfada431 2 2 <title>Download the bootscripts</title> 3 3 4 <para>Typing out all the bootscripts in chapter s 7 and 9can be a long, tedious4 <para>Typing out all the bootscripts in chapter 7can be a long, tedious 5 5 process, not to mention very error-prone.</para> 6 6 -
chapter02/commands.xml
rbc831b5 rfada431 6 6 7 7 <para>These files can be used to quickly find out which commands have 8 been changed between the different LFS versions as well. Download the8 been changed between the different LFS versions. Download the 9 9 lfs-commands tarball for this book version and the previous book 10 10 version and run a diff on the files. That way it is possible to see which … … 14 14 15 15 <para>A side effect is that these files can be used to dump to a shell and 16 install the packages, though some files need to be modified (for 17 example, when the kbd package is installed, you needed to select the 18 keyboard layout file, because it can't reliably be guessed). Keep in 19 mind, please, that these files are not checked for correctness, 20 integrity and so forth. There may be bugs in the files (since they are 21 manually created, typo's are often inevitable) so do check them and 22 don't blindly trust them.</para> 16 install the packages, though some files need to be modified (where 17 certain settings can't be guessed and depend on user preference or 18 system hardware). Keep in mind, please, that these files are not 19 thoroughly checked for correctness. There may be bugs in the files (since 20 they are manually created at the moment) so do check them and don't 21 blindly trust them.</para> 22 23 <para>If you decide to use the commands to automatically install a 24 package and it doesn't work, try reading the book's instructions 25 instead before you ask for help on the mailinglist.</para> 23 26 24 27 <para>The lfscommands can be downloaded from <ulink -
chapter02/download.xml
rbc831b5 rfada431 2 2 <title>How to download the software</title> 3 3 4 <para>Throughout this document, Iwill assume that all the4 <para>Throughout this document, we will assume that all the 5 5 packages that were downloaded are placed somewhere in $LFS/usr/src.</para> 6 6 7 <para> I use the convention ofhaving a $LFS/usr/src/sources directory.8 Under sources, I have the directory 0-9 and the directories a7 <para>A convention you could use is having a $LFS/usr/src/sources directory. 8 Under sources, you can create the directory 0-9 and the directories a 9 9 through z. A package like sysvinit-&sysvinit-version;.tar.bz2 is stored under 10 10 $LFS/usr/src/sources/s/. A package like bash-&bash-version;.tar.bz2 is stored 11 under $LFS/usr/src/sources/b/, and so forth. This convention does not have to 12 be followed, of course; I was just giving an example. It's better to keep 13 the packages out of $LFS/usr/src and move them to a subdirectory, so 14 we'll have a clean $LFS/usr/src directory in which we will unpack the 15 packages and work with them.</para> 11 under $LFS/usr/src/sources/b/, and so forth.</para> 16 12 17 13 <para>The next chapter contains the list of all the packages that need to be 18 downloaded, 19 but the partition that is going to contain our LFS system isn't created yet. 20 Therefore, the files are temporarily stored somewhere else (it's up to 21 you to decide where this 'else' is) and later moved to $LFS/usr/src/ when 22 the chapter in which the new partition is prepared has been finished.</para> 14 downloaded, but the partition that is going to contain our LFS system isn't 15 created yet. Therefore, you should store the files somewhere else and later 16 moved to $LFS/usr/src/ when the chapter in which the new partition is 17 prepared has been finished.</para> 23 18 24 19 </sect1> -
chapter02/install.xml
rbc831b5 rfada431 9 9 <para>Before you can actually start doing something with a package, you need 10 10 to unpack it first. Often the package files are tar'ed and 11 gzip'ed or bzip2'ed. I'mnot going to write down every time how to12 unpack an archive. I will explain how to do that once, in this11 gzip'ed or bzip2'ed. We're not going to write down every time how to 12 unpack an archive. We'll explain how to do that once, in this 13 13 section.</para> 14 14 … … 59 59 <para><screen><userinput>bunzip2 filename.bz2</userinput></screen></para> 60 60 61 <para>After a package has been installed, two things can be done with it: 62 either the directory that contains the sources can be deleted, 63 or it can be kept. If it is kept, that's fine with me, but if the 64 same package is needed again in a later chapter, the directory 65 needs to be deleted first before using it again. If this is not done, 66 you might end up in trouble because old settings will be used (settings 67 that apply to the host system but which don't always apply to 68 the LFS system). Doing a simple make clean or make distclean does not 69 always guarantee a totally clean source tree.</para> 61 <para>After a package has been installed, two things can be done with 62 it: either the directory that contains the sources can be deleted, or it 63 can be kept. We highly recommend deleting it. If you don't do this and 64 try to re-use the same source later on in the book (for example re-using 65 the source trees from chapter 5 for use in chapter 6), it may not work 66 as you expect it to. Source trees from chapter 5 will have your host 67 distribution's settings, which don't always apply to the LFS system 68 after you enter the chroot'ed environment. Even running something like 69 <emphasis>make clean</emphasis> doesn't always guarantee a clean source 70 tree.</para> 70 71 71 72 <para>So, save yourself a lot of hassle and just remove the source directory
Note:
See TracChangeset
for help on using the changeset viewer.