Changeset 666f6de for postlfs/config

Timestamp:

10/03/2003 02:12:31 AM (21 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

9491ec6b

Parents:

0482b012

Message:

filesystem->file system, bootdisk->boot disk, other spelling

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1275 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:

postlfs/config

Files:

• bootdisk.xml (modified) (7 diffs)
• compressdoc.xml (modified) (6 diffs)
• skel.xml (modified) (1 diff)

postlfs/config/bootdisk.xml

@@ -1 +1 @@
 <sect1 id="postlfs-config-bootdisk">
 <?dbhtml filename="bootdisk.html" dir="postlfs"?>
-<title>Creating a Custom Bootdisk</title>
+<title>Creating a Custom Boot Disk</title>
 
 <sect2>
-<title>Decent Rescue Bootdisk Needs</title>
+<title>Decent Rescue Boot Disk Needs</title>
 <para>This section is really about creating a <emphasis>rescue</emphasis>
 diskette.  As the name <emphasis>rescue</emphasis> implies, the host
@@ -16 +16 @@
 dependency on the host system's resources, other than basic bootability
 and hardware soundness.  At a minimum, the most common sorts of failures
-requiring a rescue bootdisk should be addressed by the contents of the
-bootdisk.  This would include the common loss of partitioning (master
+requiring a rescue boot disk should be addressed by the contents of the
+boot disk.  This would include the common loss of partitioning (master
 boot record is lost or corrupted), file system corruption, and the need
 to allow creation and editing of files that may have been lost or
@@ -30 +30 @@
 <title>This Minimal Decent Rescue Disk</title>
 
-<para>The intent here is to create a "rescue bootdisk" that will support
+<para>The intent here is to create a "rescue boot disk" that will support
 the common operations listed above.  These functions are provided by
 including selected executables from <application><ulink
@@ -48 +48 @@
 
 <sect2>
-<title>Build the Rescue Bootdisk</title>
+<title>Build the Rescue Boot Disk</title>
 <sect3>
 <title>Prerequisites</title>
@@ -239 +239 @@
 
 <para><emphasis>You must modify this to suit your kernel configuration and
-other needs.</emphasis>  For example, you may need scsi devices and may not need
+other needs.</emphasis>  For example, you may need
+<acronym>SCSI</acronym> devices and may not need
 frame buffer devices or the pseudo-terminal directory.  Also, the number
 of hard drives and partitions that you include should be the minimal
@@ -268 +269 @@
 diskette.  Every little bit helps.  The strategy taken here is to create
 these two files as part of the rescue boot and initialization process.
-The commands that make the two files will be imbedded inside the
+The commands that make the two files will be embedded inside the
 <filename>rcS</filename> script that <filename>linuxrc</filename>
 (really <application><ulink
@@ -640 +641 @@
 
 <para>That's all there is to it. The possibilities from here are limited only
-by your imagination and tenacity in pursueing enhancements. And your
+by your imagination and tenacity in pursuing enhancements. And your
 willingness to research available documentation. A good starting point
 is the "Documentation" directory in your kernel source tree. More help

postlfs/config/compressdoc.xml

@@ -23 +23 @@
 # to accept compression/decompression, to correctly handle hard-links,
 # to allow for changing hard-links into soft- ones, to specify the
-# compression level, to parse the man.conf for all occurences of MANPATH,
+# compression level, to parse the man.conf for all occurrences of MANPATH,
 # to allow for a backup, to allow to keep the newest version of a page.
 #
@@ -32 +32 @@
 #          tool : gzip or bzip2;
 #        - when a MANPATH env var exists, use this instead of /etc/man.conf
-#          (usefull for users to (de)compress their man pages;
+#          (useful for users to (de)compress their man pages;
 #        - offer an option to restore a previous backup;
 #        - add other compression engines (compress, zip, etc?). Needed?
@@ -82 +82 @@
                 directories.
                 When empty, and only then, parse ${MAN_CONF}/man.conf for all
-                occurences of MANPATH.
+                occurrences of MANPATH.
 
 Note about compression
@@ -91 +91 @@
   big being very dependent on the content of the files.
 
-  See the original thread begining at :
+  See the original thread beginning at :
 http://archive.linuxfromscratch.org/mail-archives/blfs-support/2003/04/0424.html
 
@@ -291 +291 @@
 fi
 
-# In backup mode, do the backup sollely
+# In backup mode, do the backup solely
 if [ "$BACKUP" = "yes" ]; then
   for DIR in $MAN_DIR; do
@@ -358 +358 @@
 
         # Now take care of the file that has no hard-link
-        # We do decompress first to recompress with the selected
+        # We do decompress first to re-compress with the selected
         # compression ratio later on...
         case $FILE in

postlfs/config/skel.xml

@@ -90 +90 @@
 send output there instead and then just copy the file from
 <filename class="directory">/etc/skel</filename> to the appropriate directories, like
-<filename class="directory">/etc</filename>, <filename class="directory">~</filename> or the home directoriy
+<filename class="directory">/etc</filename>, <filename class="directory">~</filename> or the home directory
 of any other user already in the system.</para>