Changeset 728ea56
- Timestamp:
- 03/23/2001 03:13: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:
- 4848808
- Parents:
- 0375b34
- Location:
- chapter03
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/creatingdirs.xml
r0375b34 r728ea56 3 3 4 4 <para> 5 Let's create the directory tree on the LFS partition according tothe FHS5 Let's create the directory tree on the LFS partition based on the FHS 6 6 standard, which can be found at <ulink 7 7 url="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</ulink>. 8 Issuing the following commands will create the necessary directories:8 Issuing the following commands will create a default directory layout: 9 9 </para> 10 10 … … 37 37 <para> 38 38 Normally, directories are created with permission mode 755, which isn't 39 desired for all directories. I haven't checked if the FHS suggests 40 default modes for certain directories, so I'll just change the modes for 41 a few directories that make sense to change. The first change is a mode 42 0750 for the $LFS/root directory. This is to make sure that not just 43 everybody can enter the /root directory (the same a user would do with 44 /home/username directories). The second change is a mode 1777 for the tmp 45 directories. This way, any user can write stuff to the /tmp directory when 46 needed. The sticky (1) bit makes sure users can't delete other 47 users' files which they normally can do, because the directory is set in 48 such a way that everybody (owner, group, world) can write to that directory. 39 desired for all directories. The first change is a mode 0750 for the 40 $LFS/root directory. This is to make sure that not just everybody can 41 enter the /root directory (the same a user would do with /home/username 42 directories). The second change is a mode 1777 for the tmp 43 directories. This way, any user can write data to the /tmp directory when 44 needed. The sticky bit (the first bit in the 1777 mask) makes sure 45 users can't delete other users files which they normally can do, 46 because the directory is set in such a way that everybody (owner, group, 47 world) can write to that directory (the 777 in the bit mask) 49 48 </para> 50 49 … … 59 58 <para> 60 59 Now that the directories are created, copy the source files that were 61 downloaded in chapter 3 to some subdirectory under $LFS/usr/src ( this62 directory still needs to be created yet).60 downloaded in chapter 3 to some subdirectory under $LFS/usr/src (you 61 will need to create the desired directory yourself). 63 62 </para> 64 63 -
chapter03/creatingfs.xml
r0375b34 r728ea56 4 4 <para> 5 5 Once the partition is created, we have to create a new file system on 6 that partition. To create an ext2 file system, the mke2fs command is the7 correct choice. To create a reiser file system, the mkreiserfs command 8 should be used. The new partition is used as the only option to the 9 command and the file system is created. If the partition is hda11 10 and ext2 is to be created, the user would run:6 that partition. To create an ext2 file system, use the mke2fs command. 7 To create a reiser file system, the mkreiserfs command should be used. 8 The new partition is used as the only option to the command and the file 9 system is created. If the partition is hda11 and ext2 is to be created, 10 run the following: 11 11 </para> 12 12 … … 18 18 19 19 <para> 20 To create a reiser file system the user would run:20 To create a reiser file system, run the following: 21 21 </para> 22 22 -
chapter03/mounting.xml
r0375b34 r728ea56 1 <sect1 id="ch04-mounting part">1 <sect1 id="ch04-mounting"> 2 2 <title>Mounting the new partition</title> 3 3 4 4 <para> 5 Now that we have created the ext2 file system, it is ready for use. All we have 6 to do to be able to access it (as in reading from and writing date to it) is 7 mounting it. If it is mounted under /mnt/lfs, this partition can be accessed 8 by going to the /mnt/lfs directory and then doing whatever needed to do. This 9 book will assume that the partition was mounted on a subdirectory 10 under /mnt. It doesn't matter which directory is chosen, the user just has 11 to make sure 12 that he remembers what he chose. 5 Now that we have created a file system, it is ready for use. All we have 6 to do to be able to access it (as in reading data from and writing data to 7 it) is mounting 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 needed to do. This book will assume that the partition was mounted 10 under /mnt/lfs. It doesn't matter which directory is chosen, the 11 user just has to make sure that he remembers what he chose. 13 12 </para> 14 13 … … 34 33 35 34 <para> 36 Replace <quote>xxx</quote> by the partition's designation .35 Replace <quote>xxx</quote> by the partition's designation (like hda11). 37 36 </para> 38 37 39 38 <para> 40 This directory (/mnt/lfs) is the $LFS variable I have written about earlier. 41 So if the user somewhere reads to "cp inittab $LFS/etc" he actually will type 42 <quote>cp inittab /mnt/lfs/etc</quote>. Or if he wants to use the $LFS 43 environment variable, <userinput>export LFS=/mnt/lfs</userinput> has to be 44 executed now. </para> 39 This directory (/mnt/lfs) is the $LFS variable you have read about earlier. 40 If you were planning to make use of the $LFS environment variable, 41 <userinput>export LFS=/mnt/lfs</userinput> has to be executed now. 42 </para> 45 43 46 44 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.