Changeset 6dc64f6
- Timestamp:
- 03/23/2001 03:03:02 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:
- 0375b34
- Parents:
- ff9fe017
- Location:
- chapter03
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/creatingfs.xml
rff9fe017 r6dc64f6 6 6 that partition. To create an ext2 file system, the mke2fs command is the 7 7 correct choice. To create a reiser file system, the mkreiserfs command 8 should be used. To create a different kind of file system, the 9 appropriate command needs to be executed. The new partition is used 10 as the only option to the 11 command and the file system is created. If the partition is hda2 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 12 10 and ext2 is to be created, the user would run: 13 11 </para> … … 15 13 <blockquote><literallayout> 16 14 17 <userinput>mke2fs /dev/hda 2</userinput>15 <userinput>mke2fs /dev/hda11</userinput> 18 16 19 17 </literallayout></blockquote> 20 18 21 19 <para> 22 To use reiserfsthe user would run:20 To create a reiser file system the user would run: 23 21 </para> 24 22 25 23 <blockquote><literallayout> 26 24 27 <userinput>mkreiserfs /dev/hda 2</userinput>25 <userinput>mkreiserfs /dev/hda11</userinput> 28 26 29 27 </literallayout></blockquote> -
chapter03/creatingpart.xml
rff9fe017 r6dc64f6 5 5 Before we can build our new Linux system, we need to have an empty Linux 6 6 partition on which we can build our new system. I recommend a partition size 7 of a round750 MB. This gives enough space to store all the tarballs and7 of at least 750 MB. This gives enough space to store all the tarballs and 8 8 to compile all packages without worrying about running out of the necessary 9 temporary disk space. If a Linux Native partition is already available, 10 this subsection can be skipped. 9 temporary disk space. But you probably want more space than that if you 10 plan to use the LFS system as your primary Linux system. If that's the 11 case you'd want more space so you can install additional software. If a 12 Linux Native partition is already available, this subsection can be skipped. 11 13 </para> 12 14 13 15 <para> 14 16 The cfdisk program (or another fdisk like program the user prefers) is 15 started with the 16 appropriate hard disk as the option (like /dev/hda if the gentle reader 17 wants to create a 18 new partition on the primary master IDE disk). It is used to create a Linux 19 Native partition, write the partition table and exit the cfdisk program. 20 The new partition's designation should be remembered. It could be something 21 like hda11 (as it is in my case). This newly created partition will be 22 referred to as the LFS partition in this book. 17 started with the appropriate hard disk as the option (like /dev/hda if a 18 new partition is to be created on the primary master IDE disk). It is used 19 to create a Linux Native partition, write the partition table and exit the 20 cfdisk program. The new partition's designation should be remembered. It 21 could be something like hda11 (as it is in my case). This newly created 22 partition will be referred to as the LFS partition in this book. 23 23 </para> 24 24
Note:
See TracChangeset
for help on using the changeset viewer.