Ignore:
Timestamp:
06/16/2020 11:56:28 AM (4 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, 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:
9a05e45
Parents:
560065f (diff), 1cd5961 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Split Chapter 5 into three separate chapters.
Implement a new method of cross-building the LFS tool chain
and other tools to simplify the method of isolating the
new system from the original host. This will be the start of
LFS-10.0.

Move old trunk/BOOK to branches/old-trunk.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11946 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter02/creatingpartition.xml

    r560065f r675606b  
    1515  is to use an available empty partition or, if you have enough unpartitioned
    1616  space, to create one.</para>
    17 
    18 <!--
    19 
    20   <para>It is possible to install an LFS system (in fact even multiple LFS
    21   systems) on a partition already occupied by another
    22   operating system and the different systems will co-exist peacefully. The
    23   document <ulink url="&hints-root;lfs_next_to_existing_systems.txt"/>
    24   contains notes on how to implement this. This document was last updated
    25   in 2004. It has not been updated since and it has not been tested with
    26   recent versions of this LFS book. The document is more than likely not
    27   usable as-is and you will need to account for changes made to the LFS
    28   procedures since it was written. This is only recommended for expert LFS
    29   users.</para>
    30 
    31 -->
    3217
    3318  <para>A minimal system requires a partition of around 10 gigabytes (GB).
    … …  
    7863
    7964  <para>Requests for advice on system partitioning are often posted on the LFS mailing
    80   lists.  This is a highly subjective topic.  The default for most distributions
     65  lists. This is a highly subjective topic.  The default for most distributions
    8166  is to use the entire drive with the exception of one small swap partition.  This
    8267  is not optimal for LFS for several reasons.  It reduces flexibility, makes
    … …  
    9075    <para>A root LFS partition (not to be confused with the
    9176    <filename class="directory">/root</filename> directory) of
    92     ten gigabytes is a good compromise for most systems.  It provides enough
     77    twenty gigabytes is a good compromise for most systems.  It provides enough
    9378    space to build LFS and most of BLFS, but is small enough so that multiple
    9479    partitions can be easily created for experimentation.</para> </sect3>
    … …  
    10388    swapping.</para>
    10489
    105     <para>Swapping is never good.  Generally you can tell if a system is
    106     swapping by just listening to disk activity and observing how the system
    107     reacts to commands.  The first reaction to swapping should be to check for
    108     an unreasonable command such as trying to edit a five gigabyte file.  If
    109     swapping becomes a normal occurrence, the best solution is to purchase more
    110     RAM for your system.</para>
    111     </sect3>
     90    <para>If you want to use the hibernation feature (suspend-to-disk) of Linux,
     91    it writes out the contents of RAM to the swap partition before turning off
     92    the machine. In this case the size of the swap partition should be at
     93    least as large as the system's installed RAM.</para>
     94
     95    <para>Swapping is never good. For mechanical hard drives you can generally
     96    tell if a system is swapping by just listening to disk activity and
     97    observing how the system reacts to commands.  For an SSD drive you will not
     98    be able to hear swapping but you can tell how much swap space is being used
     99    by the <command>top</command> or <command>free</command> programs.  Use of
     100    an SSD drive for a swap partition should be avoided if possible.  The first
     101    reaction to swapping should be to check for an unreasonable command such as
     102    trying to edit a five gigabyte file. If swapping becomes a normal
     103    occurrence, the best solution is to purchase more RAM for your
     104    system.</para> </sect3>
    112105
    113106    <sect3>
    … …  
    141134      store kernels and other booting information.  To minimize potential boot
    142135      problems with larger disks, make this the first physical partition on
    143       your first disk drive.  A partition size of 100 megabytes is quite
     136      your first disk drive.  A partition size of 200 megabytes is quite
    144137      adequate.</para></listitem>
    145138
    … …  
    151144      <listitem><para>/usr &ndash; A separate /usr partition is generally used
    152145      if providing a server for a thin client or diskless workstation.  It is
    153       normally not needed for LFS.  A size of five gigabytes will handle most
     146      normally not needed for LFS.  A size of ten gigabytes will handle most
    154147      installations.</para></listitem>
    155148
Note: See TracChangeset for help on using the changeset viewer.