Changeset ff9fe017
- Timestamp:
- 03/23/2001 02:56:31 AM (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:
- 6dc64f6
- Parents:
- 97f1db3
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/aboutlfs.xml
r97f1db3 rff9fe017 7 7 replaced by the directory where the partition that contains the LFS system 8 8 is mounted. How to create and where to mount the partition will be 9 explain d in full detail in chapter 4. In my case, the LFS9 explained in full detail in chapter 4. In my case, the LFS 10 10 partition is mounted on /mnt/lfs. 11 11 </para> … … 13 13 <para> 14 14 For example when you are told to run a command like 15 <userinput>./configure --prefix=$LFS</userinput> you will actually run16 <userinput>./configure --prefix=/mnt/lfs</userinput>15 <userinput>./configure --prefix=$LFS</userinput> you actually have to 16 run <userinput>./configure --prefix=/mnt/lfs</userinput> 17 17 </para> 18 18 … … 33 33 --prefix=$LFS</userinput> you can type that literally. Your shell will 34 34 replace $LFS with /mnt/lfs when it processes the command line (meaning 35 when you hit enter ).35 when you hit enter after having typed the command). 36 36 </para> 37 37 -
chapter02/install.xml
r97f1db3 rff9fe017 3 3 4 4 <para> 5 Before a user can actually start doing something with a package, he needs5 Before you can actually start doing something with a package, you need 6 6 to unpack it first. Often the package files are tar'ed and 7 gzip'ed. (That can determined by looking at the extension of the file.7 gzip'ed. (That can be determined by looking at the extension of the file. 8 8 Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for 9 9 example.) I'm not going to write down every time how to ungzip and how … … 11 11 There is also the possibility that a .tar.bz2 file could be downloaded. 12 12 Such a file would be tar'ed and compressed with the bzip2 program. 13 Bzip2 achieves a better compression than the commonly used gzip does. In14 order to use bz2 archives, the bzip2 program needs to be installed.13 Bzip2 achieves a better compression than the more commonly used gzip does. 14 In order to use bz2 archives, the bzip2 program needs to be installed. 15 15 Most if not every distribution comes with this program, so chances are 16 high it is already installed on the host system. If not, it's installed using17 the distribution's installation tool.16 high it is already installed on the host system. If not, it's installed 17 using the distribution's installation tool. 18 18 </para> 19 19 … … 31 31 If a file is tar'ed and gzip'ed, it is unpacked by 32 32 running either one of the following two commands, depending on the 33 filename format:33 filename: 34 34 </para> 35 35 … … 57 57 slightly modified to be able to use bzip2 files directly using either 58 58 the I or the y tar parameter, which works the same as the z tar parameter 59 to handle gzip archives. 59 to handle gzip archives. The above construction works no matter how 60 your host system decided to patch bzip2. 60 61 </para> 61 62 … … 73 74 When the archive is unpacked, a new directory will be created under the 74 75 current directory (and this document assumes that the archives are unpacked 75 under the $LFS/usr/src directory). A user has to enter that new directory 76 before continuing with the installation instructions. So, every time the 77 book is going to install a program, it's up to the user to unpack the source 78 archive. 76 under the $LFS/usr/src directory). Please enter that new directory 77 before continuing with the installation instructions. Again, every time 78 this book is going to install a package, it's up to you to unpack the source 79 archive and cd into the newly created directory. 80 </para> 81 82 <para> 83 From time to time you will be dealing with single files such as patch 84 files. These files are generally gzip'ed or bzip2'ed. Before such files 85 can be used they need to be uncompressed first. 79 86 </para> 80 87 … … 90 97 91 98 <para> 99 If a file is bzip2'ed, it is unpacked by running: 100 </para. 101 102 <blockquote><literallayout> 103 104 <userinput>bunzip2 filename.bz2</userinput> 105 106 </literallayout></blockquote> 107 108 <para> 92 109 After a package is installed, two things can be done with it: 93 110 either the directory that contains the sources can be deleted, 94 either it can be kept. 95 If it is kept, that's fine with me, but if the same package is needed 96 again in a later chapter, the directory needs to be deleted first before using 97 it again. If this is not done, it might end up in trouble because old 98 settings will be used (settings that apply to the normal Linux system but 99 which don't always apply to the LFS system). Doing a simple make clean 100 or make distclean does not always guarantee a totally clean source tree. 101 The configure script can also have files lying around in various 102 subdirectories which aren't always removed by a make clean process. 111 either it can be kept. If it is kept, that's fine with me, but if the 112 same package is needed again in a later chapter, the directory 113 needs to be deleted first before using it again. If this is not done, 114 you might end up in trouble because old settings will be used (settings 115 that apply to the normal Linux system but which don't always apply to 116 the LFS system). Doing a simple make clean or make distclean does not 117 always guarantee a totally clean source tree. 103 118 </para> 104 119 -
chapter03/introduction.xml
r97f1db3 rff9fe017 4 4 <para> 5 5 In this chapter the partition that is going to host the LFS system is 6 going to be prepared. A new partition will be created, a n ext2file6 going to be prepared. A new partition will be created, a file 7 7 system will be created on it and the directory structure will be 8 8 created. When this is done, we can move on to the next chapter and start
Note:
See TracChangeset
for help on using the changeset viewer.