Changeset 55ffe68
- Timestamp:
- 03/25/2001 08:17:59 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:
- c85f976
- Parents:
- 08463b5b
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/introduction.xml
r08463b5b r55ffe68 3 3 4 4 <para> 5 In this chapter the partition that is going to host the LFS system is5 In this chapter, the partition that is going to host the LFS system is 6 6 going to be prepared. A new partition will be created, a file 7 system will be created on it and the directory structure will be7 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 9 9 building a new Linux system from scratch. -
chapter03/mounting.xml
r08463b5b r55ffe68 5 5 Now that we have created a file system, it is ready for use. All we have 6 6 to do to be able to access it (as in reading data from and writing data to 7 it) is mount ingit. If it is mounted under /mnt/lfs, this partition can8 be accessed by going to the /mnt/lfs directory and then doing whatever 7 it) is mount it. If it is mounted under /mnt/lfs, this partition can 8 be accessed by going to the /mnt/lfs directory and then doing whatever 9 9 needed to do. This book will assume that the partition was mounted 10 10 under /mnt/lfs. It doesn't matter which directory is chosen, the -
chapter05/bash-exp.xml
r08463b5b r55ffe68 45 45 <para> 46 46 The <userinput>&&</userinput>'s at the end of every line cause 47 the next command only to be executed whenthe previous command exists47 the next command to be executed only if the previous command exists 48 48 with a return value of 0 indicating success. In case all of these 49 49 commands are copy&pasted 50 on the shell is is important to be ensured that if51 ./configure fails, make isn't being executed and likewise if make fails50 on the shell, is is important to be ensured that if 51 ./configure fails, make isn't being executed and, likewise, if make fails, 52 52 that make install isn't being executed, and so forth. 53 53 </para>
Note:
See TracChangeset
for help on using the changeset viewer.