Changeset 2ca8941 for chapter02

Timestamp:

02/11/2013 08:09:22 PM (11 years ago)

Author:

Matthew Burgess <matthew@…>

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, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 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, 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:

c1ec480

Parents:

c0220ed

Message:

Remove trailing whitespace from all files.

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

File:

• chapter02/creatingpartition.xml (modified) (7 diffs)

chapter02/creatingpartition.xml

@@ -76 +76 @@
   <title>Other Partition Issues</title>
 
-  <para>Requests for advice on system partitioning are often posted on the LFS mailing 
+  <para>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
   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 
+  is not optimal for LFS for several reasons.  It reduces flexibility, makes
   sharing of data across multiple distributions or LFS builds more difficult, makes
-  backups more time consuming, and can waste disk space through inefficient 
+  backups more time consuming, and can waste disk space through inefficient
   allocation of file system structures.</para>
 
     <sect3>
     <title>The Root Partition</title>
-   
+
     <para>A root LFS partition (not to be confused with the
     <filename class="directory">/root</filename> directory) of
@@ -92 +92 @@
     space to build LFS and most of BLFS, but is small enough so that multiple
     partitions can be easily created for experimentation.</para> </sect3>
-   
+
     <sect3>
     <title>The Swap Partition</title>
-   
+
     <para>Most distributions automatically create a swap partition.  Generally
     the recommended size of the swap partition is about twice the amount of
@@ -101 +101 @@
     hold the swap partition to two gigabytes and monitor the amount of disk
     swapping.</para>
-   
+
     <para>Swapping is never good.  Generally you can tell if a system is
     swapping by just listening to disk activity and observing how the system
@@ -108 +108 @@
     swapping becomes a normal occurrence, the best solution is to purchase more
     RAM for your system.</para> </sect3>
-   
+
     <sect3>
     <title>Convenience Partitions</title>
-   
+
     <para>There are several other partitions that are not required, but should
     be considered when designing a disk layout.  The following list
     is not comprehensive, but is meant as a guide.</para>
-   
+
     <itemizedlist>
-      
+
       <listitem><para>/boot &ndash; Highly recommended.  Use this partition to
       store kernels and other booting information.  To minimize potential boot
@@ -123 +123 @@
       your first disk drive.  A partition size of 100 megabytes is quite
       adequate.</para></listitem>
-      
+
       <listitem><para>/home &ndash; Highly recommended.  Share your home
       directory and user customization across multiple distributions or LFS
       builds.  The size is generally fairly large and depends on available disk
       space.</para></listitem>
-      
+
       <listitem><para>/usr &ndash; 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
       installations.</para></listitem>
-      
+
       <listitem><para>/opt &ndash; This directory is most useful for
       BLFS where multiple installations of large packages like Gnome or KDE can
@@ -139 +139 @@
       used, 5 to 10 gigabytes is generally adequate.</para>
       </listitem>
-      
+
       <listitem><para>/tmp &ndash; A separate /tmp directory is rare, but
       useful if configuring a thin client.  This partition, if used, will
       usually not need to exceed a couple of gigabytes.</para></listitem>
-      
+
       <listitem><para>/usr/src &ndash; This partition is very
       useful for providing a location to store BLFS source files and
@@ -149 +149 @@
       for building BLFS packages.  A reasonably large partition of 30-50
       gigabytes allows plenty of room.</para></listitem>
-   
+
     </itemizedlist>
-   
+
     <para>Any separate partition that you want automatically mounted upon boot
     needs to be specified in the <filename>/etc/fstab</filename>.  Details
     about how to specify partitions will be discussed in <xref
     linkend="ch-bootable-fstab"/>.  </para>
-   
+
     </sect3>
   </sect2>