From efcb3933433838b71f3a4a53ec1ac6d899aaec0b Mon Sep 17 00:00:00 2001 From: Pierre Labastie Date: Sun, 3 May 2020 21:02:51 +0000 Subject: Make the new book git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross-chap5@11831 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter02/stages.xml | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) (limited to 'chapter02') diff --git a/chapter02/stages.xml b/chapter02/stages.xml index 30e820213..6ca265991 100644 --- a/chapter02/stages.xml +++ b/chapter02/stages.xml @@ -25,9 +25,9 @@ - Procedures done as the root user after Section 2.4 need to - have the LFS environment variable set FOR THE ROOT - USER. + Procedures done as the root user after Section 2.4 need to + have the LFS environment variable set FOR THE ROOT + USER. @@ -37,14 +37,20 @@ - The /mnt/lfs partition must be mounted. + The /mnt/lfs partition must be mounted. - ALL instructions in Chapter 5 - must be done by user lfs. - A su - lfs needs to be done before any - task in Chapter 5. + This chapter includes three parts. The first one, from + Binutils Pass1 to Stripping + must be done by user lfs. A + su - lfs needs to be done before any task in this + part. The second part, from Changing Ownership to + Entering the Chroot Environment must be done as the + root user, with LFS set for the root user. The third part, from + Creating Directories to the end of the chapter, is done + in the chroot environment. The same procedures as for chapter 6 + apply. -- cgit v1.2.3-54-g00ecf From eb8890f68b9d1fa49c48b6d0f0c2a58ac7a6e0cd Mon Sep 17 00:00:00 2001 From: Pierre Labastie Date: Mon, 8 Jun 2020 19:36:30 +0000 Subject: Update "building LFS in Stages" for the new layout git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11904 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter02/stages.xml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'chapter02') diff --git a/chapter02/stages.xml b/chapter02/stages.xml index 6ca265991..25de52632 100644 --- a/chapter02/stages.xml +++ b/chapter02/stages.xml @@ -33,7 +33,7 @@ - Chapter 5 + Chapter 5–6 @@ -41,16 +41,10 @@ - This chapter includes three parts. The first one, from - Binutils Pass1 to Stripping - must be done by user lfs. A - su - lfs needs to be done before any task in this - part. The second part, from Changing Ownership to - Entering the Chroot Environment must be done as the - root user, with LFS set for the root user. The third part, from - Creating Directories to the end of the chapter, is done - in the chroot environment. The same procedures as for chapter 6 - apply. + Those two chapters must be done as user lfs. + A su - lfs needs to be done before any task in this + part. Failing to do that, you are at risk of installing packages to the + host, and render it unusable. @@ -64,16 +58,22 @@ - Chapters 6–8 + Chapter 7–10 The /mnt/lfs partition must be mounted. + + A few operations, from Changing Ownership to + Entering the Chroot Environment must be done as the + root user, with LFS set for the root user. + + When entering chroot, the LFS environment variable must be set - for root. The LFS variable is not used otherwise. + for root. The LFS variable is not used afterwards. -- cgit v1.2.3-54-g00ecf From b99b7d3a6e77c4728dcf9903f71f2e3fdd95daca Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Tue, 9 Jun 2020 17:25:59 +0000 Subject: Update text in cross2 branch Chapter 2. git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11912 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter02/creatingfilesystem.xml | 35 +------------------------------ chapter02/creatingpartition.xml | 45 +++++++++++++++++----------------------- chapter02/stages.xml | 14 ++++++------- 3 files changed, 27 insertions(+), 67 deletions(-) (limited to 'chapter02') diff --git a/chapter02/creatingfilesystem.xml b/chapter02/creatingfilesystem.xml index 4a722efe0..f01b745e9 100644 --- a/chapter02/creatingfilesystem.xml +++ b/chapter02/creatingfilesystem.xml @@ -52,42 +52,9 @@ mkfs -v -t ext4 /dev/<xxx> - If you are using an existing swap partition, there is no need to format it. If a new swap partition was created, diff --git a/chapter02/creatingpartition.xml b/chapter02/creatingpartition.xml index 02d6528b1..672c2efb5 100644 --- a/chapter02/creatingpartition.xml +++ b/chapter02/creatingpartition.xml @@ -15,21 +15,6 @@ is to use an available empty partition or, if you have enough unpartitioned space, to create one. - - A minimal system requires a partition of around 10 gigabytes (GB). This is enough to store all the source tarballs and compile the packages. However, if the LFS system is intended to be the primary Linux system, @@ -77,7 +62,7 @@ Other Partition Issues Requests for advice on system partitioning are often posted on the LFS mailing - lists. This is a highly subjective topic. The default for most distributions + lists. This is a highly subjective topic. The default for most distributions is to use the entire drive with the exception of one small swap partition. This is not optimal for LFS for several reasons. It reduces flexibility, makes sharing of data across multiple distributions or LFS builds more difficult, makes @@ -89,7 +74,7 @@ A root LFS partition (not to be confused with the /root directory) of - ten gigabytes is a good compromise for most systems. It provides enough + twenty gigabytes is a good compromise for most systems. It provides enough space to build LFS and most of BLFS, but is small enough so that multiple partitions can be easily created for experimentation. @@ -102,13 +87,21 @@ hold the swap partition to two gigabytes and monitor the amount of disk swapping. - Swapping is never good. Generally you can tell if a system is - swapping by just listening to disk activity and observing how the system - reacts to commands. The first reaction to swapping should be to check for - an unreasonable command such as trying to edit a five gigabyte file. If - swapping becomes a normal occurrence, the best solution is to purchase more - RAM for your system. - + If you want to use the hibernation feature (suspend-to-disk) of Linux, + it writes out the contents of RAM to the swap partition before turning off + the machine. In this case the size of the swap partition should be at + least as large as the system's installed RAM. + + Swapping is never good. For mechanical hard drives you can generally + tell if a system is swapping by just listening to disk activity and + observing how the system reacts to commands. For an SSD drive you will not + be able to hear swapping but you can tell how much swap space is being used + by the top or free programs. Use of + an SSD drive for a swap partition should be avoided if possible. The first + reaction to swapping should be to check for an unreasonable command such as + trying to edit a five gigabyte file. If swapping becomes a normal + occurrence, the best solution is to purchase more RAM for your + system. The Grub Bios Partition @@ -140,7 +133,7 @@ /boot – Highly recommended. Use this partition to store kernels and other booting information. To minimize potential boot problems with larger disks, make this the first physical partition on - your first disk drive. A partition size of 100 megabytes is quite + your first disk drive. A partition size of 200 megabytes is quite adequate. /home – Highly recommended. Share your home @@ -150,7 +143,7 @@ /usr – A separate /usr partition is generally used if providing a server for a thin client or diskless workstation. It is - normally not needed for LFS. A size of five gigabytes will handle most + normally not needed for LFS. A size of ten gigabytes will handle most installations. /opt – This directory is most useful for diff --git a/chapter02/stages.xml b/chapter02/stages.xml index 25de52632..0d513383d 100644 --- a/chapter02/stages.xml +++ b/chapter02/stages.xml @@ -41,17 +41,17 @@ - Those two chapters must be done as user lfs. - A su - lfs needs to be done before any task in this - part. Failing to do that, you are at risk of installing packages to the - host, and render it unusable. + Threse two chapters must be done as user lfs. + A su - lfs needs to be done before any task in these + chapters. Failing to do that, you are at risk of installing packages to the + host, and potentially rendering it unusable. The procedures in are critical. If there is any doubt about installing a package, ensure any previously expanded - tarballs are removed, re-extract the package files, and complete all + tarballs are removed, then re-extract the package files, and complete all instructions in that section. @@ -67,8 +67,8 @@ A few operations, from Changing Ownership to - Entering the Chroot Environment must be done as the - root user, with LFS set for the root user. + Entering the Chroot Environment must be done as the + root user, with the LFS envirnment variable set for the root user. -- cgit v1.2.3-54-g00ecf