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

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1275 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Larry Lawrence 2003-10-03 02:12:31 +00:00
parent 0482b012c6
commit 666f6de69c
22 changed files with 52 additions and 51 deletions

View File

@ -171,7 +171,7 @@
<entry>K60</entry>
<entry>mountfs</entry>
<entry><filename>../init.d/mountfs</filename></entry>
<entry>Unmount all filesystems: Part of <acronym>LFS</acronym> base.</entry>
<entry>Unmount all file systems: Part of <acronym>LFS</acronym> base.</entry>
</row>
<row>

View File

@ -164,7 +164,7 @@
<entry>K60</entry>
<entry>mountfs</entry>
<entry><filename>../init.d/mountfs</filename></entry>
<entry>Unmount all filesystems: Part of <acronym>LFS</acronym> base.</entry>
<entry>Unmount all file systems: Part of <acronym>LFS</acronym> base.</entry>
</row>
<row>

View File

@ -10,12 +10,12 @@
<sect3><title>pcregrep</title>
<para><command>pcregrep</command> is a grep that understands
<application>perl</application> compatible regular
<application>Perl</application> compatible regular
expressions.</para></sect3>
<sect3><title>pcretest</title>
<para><command>pcretest</command> can test your
<application>perl</application> compatible regular expression.</para></sect3>
<application>Perl</application> compatible regular expression.</para></sect3>
<sect3><title>pcre-config</title>
<para><filename>pcre-config</filename> is used during the compile process of programs

View File

@ -2,7 +2,7 @@
<title>Introduction to <application>pcre</application></title>
<para>The <application>pcre</application> package contains
<application>perl</application> compatible regular expression
<application>Perl</application> compatible regular expression
libraries. These are useful for implementing regular expression pattern
matching using the same syntax and semantics as <application>Perl
5</application>.</para>

View File

@ -1,7 +1,7 @@
<sect2>
<title>Introduction to <application>perl</application> modules</title>
<title>Introduction to <application>Perl</application> modules</title>
<para>The <application>perl</application> module packages add useful objects
<para>The <application>Perl</application> module packages add useful objects
to the <application>Perl</application> language. Modules utilized by packages
throughout <acronym>BLFS</acronym> are listed here along with their
dependencies.</para>

View File

@ -47,7 +47,7 @@ a place to put packages that will be the same on all of them.</para></listitem>
<listitem><para>Or you might regularly rebuild your <acronym>LFS</acronym>, but
want a place to put files that you don't want to rebuild each time. This way
you can wipe the <acronym>LFS</acronym> filesystem and start from a clean
you can wipe the <acronym>LFS</acronym> file system and start from a clean
partition every time without losing everything.</para></listitem>
</itemizedlist>

View File

@ -21,7 +21,7 @@
<sect3><title>mkisofs</title>
<para><command>mkisofs</command> and <command>mkhybrid</command>
generate an <acronym>ISO</acronym>9660/JOLIET/<acronym>HFS</acronym> hybrid filesystem.</para></sect3>
generate an <acronym>ISO</acronym>9660/JOLIET/<acronym>HFS</acronym> hybrid file system.</para></sect3>
<sect3><title>readcd</title>
<para><command>readcd</command> reads or writes Compact Discs.</para></sect3>

View File

@ -7,7 +7,7 @@ for creating and mounting <acronym>CD</acronym>-<acronym>RW</acronym> disks with
reading and writing. <acronym>UDF</acronym> files systems are used on
both <acronym>CD</acronym>-<acronym>RW</acronym> media and
on <acronym>DVD</acronym>. For more details of the
<acronym>UDF</acronym> filesystem standard see:
<acronym>UDF</acronym> file system standard see:
<ulink url="http://www.osta.org"/> and <ulink
url="http://www.ecma-international.org"/>.</para>

View File

@ -1,9 +1,9 @@
<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
system has a problem, often lost partition information or corrupted file
@ -15,8 +15,8 @@ drive <emphasis>will</emphasis> be available is a risky presumption.</para>
<para>Heeding the warning, the rescue disk created here has no
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
corrupted, possibly as an effect of the other two problems.</para>
@ -29,7 +29,7 @@ that might be expected to be needed when reconstructing.</para>
<sect2>
<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
url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox
@ -47,7 +47,7 @@ just too numerous to mention here.</para>
</sect2>
<sect2>
<title>Build the Rescue Bootdisk</title>
<title>Build the Rescue Boot Disk</title>
<sect3>
<title>Prerequisites</title>
@ -238,7 +238,8 @@ your host, you'll want to use something similar to this longer command,
to minimize wasting space with unneeded inodes.</para>
<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
that you need. Extensive analysis has not been done on the list below,
@ -267,7 +268,7 @@ inodes and two blocks of space on the initial ramdisk. This only really
matters because of trying to squeeze everything onto a 1.44MB
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
url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox
@ -639,7 +640,7 @@ Note that no <command>seek</command> parameter is used.</para>
<screen><userinput><command>dd if=/tmp/rootfs.gz of=/dev/floppy/0 bs=1k</command></userinput></screen>
<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
may be gained at

View File

@ -22,7 +22,7 @@ to go is to use the script below.
# Modified 20030925 by Yann E. Morin &lt;yann.morin.1998 @ # anciens.enib.fr&gt;
# 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.
#
# TODO:
@ -31,7 +31,7 @@ to go is to use the script below.
# - choose a default compress method to be based on the available
# 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?
@ -81,7 +81,7 @@ function help ()
dirs A list of space-separated _absolute_ pathname to the man
directories.
When empty, and only then, parse ${MAN_CONF}/man.conf for all
occurences of MANPATH.
occurrences of MANPATH.
Note about compression
There has been a discussion on blfs-support about compression ratios of
@ -90,7 +90,7 @@ Note about compression
was much efficient on 'small' files, and bzip2 on 'big' files, small and
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
On my system (x86, ext3), man pages were 35564kiB before compression. gzip -9
@ -290,7 +290,7 @@ if [ -z "${COMP_METHOD}" -a "${BACKUP}" = "no" ]; then
exit 1
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
cd "${DIR}/.."
@ -357,7 +357,7 @@ for DIR in $MAN_DIR; do
fi
# 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
*.bz2)

View File

@ -89,7 +89,7 @@ just send the results to the user's home directory. If the file is going
to be in <filename class="directory">/etc/skel</filename>, change the book's command(s) to
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>
<para><emphasis>When Adding a User</emphasis></para>

View File

@ -2,8 +2,8 @@
<?dbhtml filename="ext3.html" dir="postlfs"?>
<title>Ext3</title>
<para>Ext3 is a journaling filesystem that is an extension to the ext2
filesystem. It is backward compatible with ext2 and the conversion from ext2
<para>Ext3 is a journaling file system that is an extension to the ext2
file system. It is backward compatible with ext2 and the conversion from ext2
to ext3 is trivial.</para>
<para>You don't need to install anything to use ext3, all the required

View File

@ -2,11 +2,11 @@
<?dbhtml filename="filesystems.html" dir="postlfs"?>
<title>Filesystems</title>
<para>Journaling filesystems reduce the time needed to recover a
filesystem that was not unmounted properly. While this can be extremely
<para>Journaling file systems reduce the time needed to recover a
file system that was not unmounted properly. While this can be extremely
important in reducing downtime for servers, it has also become popular for
desktop environments. This chapter contains a variety of journaling
filesystems.</para>
file systems.</para>
&postlfs-filesystems-ext3;
&reiser;

View File

@ -12,9 +12,9 @@
<sect3><title>debugreiserfs</title>
<para><command>debugreiserfs</command> can sometimes help to solve problems
with <application>ReiserFS</application> filesystems. If it is called without
with <application>ReiserFS</application> file systems. If it is called without
options it prints the super
block of any reiserfs filesystem found on the device.</para></sect3>
block of any reiserfs file system found on the device.</para></sect3>
<sect3><title>mkreiserfs</title>
<para><command>mkreiserfs</command> creates a
@ -39,7 +39,7 @@ man page thoroughly.</para></sect3>
<sect3><title>unpack</title>
<para>The <command>unpack</command> utility can be used to dump
<application>ReiserFS</application>
filesystem information to files for debugging, much like
file system information to files for debugging, much like
<command>debugreiserfs</command>.
</para></sect3>

View File

@ -2,7 +2,7 @@
<title>Introduction to <application>ReiserFS</application></title>
<para>The <application>ReiserFS</application> package contains various
utilities for use with the Reiser filesystem.</para>
utilities for use with the Reiser file system.</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>

View File

@ -14,16 +14,16 @@
<sect2><title>Description</title>
<sect3><title>xfsgrowfs</title>
<para><command>xfsgrowfs</command> expands an <acronym>XFS</acronym> filesystem.
<para><command>xfsgrowfs</command> expands an <acronym>XFS</acronym> file system.
</para></sect3>
<sect3><title>xfs_admin</title>
<para><command>xfs_admin</command> changes the parameters of an <acronym>XFS
</acronym> filesystem.</para></sect3>
</acronym> file system.</para></sect3>
<sect3><title>xfs_freeze</title>
<para><command>xfs_freeze</command> suspends access to an <acronym>XFS</acronym> filesystem.</para></sect3>
<para><command>xfs_freeze</command> suspends access to an <acronym>XFS</acronym> file system.</para></sect3>
<sect3><title>xfs_mkfile</title>
@ -32,7 +32,7 @@ padded with zeroes by default.</para></sect3>
<sect3><title>xfs_check</title>
<para><command>xfs_check</command> checks <acronym>XFS</acronym> filesystem
<para><command>xfs_check</command> checks <acronym>XFS</acronym> file system
consistency.</para>
</sect3>
@ -42,29 +42,29 @@ consistency.</para>
<sect3><title>xfs_rtcp</title>
<para><command>xfs_rtcp</command> copies a file to the real-time
partition on an <acronym>XFS</acronym> filesystem.</para></sect3>
partition on an <acronym>XFS</acronym> file system.</para></sect3>
<sect3><title>xfs_repair</title>
<para><command>xfs_repair</command> repairs corrupt or damaged <acronym>XFS
</acronym>filesystems.</para></sect3>
</acronym>file systems.</para></sect3>
<sect3><title>xfs_db</title>
<para><command>xfs_db</command> is used to debug an <acronym>XFS</acronym>
filesystem.</para></sect3>
file system.</para></sect3>
<sect3><title>xfs_logprint</title>
<para><command>xfs_logprint</command> prints the log of an <acronym>XFS
</acronym> filesystem.</para></sect3>
</acronym> file system.</para></sect3>
<sect3><title>xfs_ncheck</title>
<para><command>xfs_ncheck</command> generates pathnames from inode numbers for
an <acronym>XFS</acronym> filesystem.</para></sect3>
an <acronym>XFS</acronym> file system.</para></sect3>
<sect3><title>mkfs.xfs</title>
<para><command>mkfs.xfs</command> constructs an <acronym>XFS</acronym>
filesystem.</para></sect3>
file system.</para></sect3>
<sect3><title>fsck.xfs</title>
<para><command>fsck.xfs</command> simply exits with a zero status, since

View File

@ -2,7 +2,7 @@
<title>Introduction to <application><acronym>XFS</acronym></application></title>
<para>The <application>XFS</application> package contains administration
and debugging tools for the <acronym>XFS</acronym> filesystem.</para>
and debugging tools for the <acronym>XFS</acronym> file system.</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>

View File

@ -2,7 +2,7 @@
<title><acronym>XFS</acronym> kernel patch</title>
<para>The <acronym>XFS</acronym> kernel patch must be applied to use
<acronym>XFS</acronym> filesystems.</para>
<acronym>XFS</acronym> file systems.</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>

View File

@ -17,7 +17,7 @@ preferences and experience. Note, that for the quoted scripts it is assumed
that the modules need to be loaded at first.</para>
<screen>Network options menu
Network paket filtering: Y
Network packet filtering: Y
Unix domain sockets: Y or M
TCP/IP networking: Y
IP: advanced router: Y

View File

@ -18,7 +18,7 @@
to read:
<screen><userinput>MD5_CRYPT_ENAB yes</userinput></screen>
Passwords created after this change will be encrypted using
<acronym>MD</acronym>5 (Message-Digest Algroithm) instead of using
<acronym>MD</acronym>5 (Message-Digest Algorithm) instead of using
<acronym>DES</acronym> encryption.
</para>
</sect2>

View File

@ -28,7 +28,7 @@ Custom policy file for SuSE 7.2 system</screen>
Get ideas from the examples above and read <filename>
/usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt
</filename> is a good policy file for beginners as it will note any changes to
the filesystem and can even be used as an annoying way of keeping track of
the file system and can even be used as an annoying way of keeping track of
changes for uninstallation of software.</para>
<para>After your policy file has been transferred to <filename

View File

@ -11,7 +11,7 @@ the rest of the book.</para></sect2>
<sect2><title>Part II - Post <acronym>LFS</acronym> Configuration and Extra
Software</title>
<para>Here we introduce basic configuration and security issues. We also
discuss a range of editors, filesystems and shells which aren't covered in
discuss a range of editors, file systems and shells which aren't covered in
the main <acronym>LFS</acronym> book.</para></sect2>
<sect2><title>Part III - General Libraries and Utilities</title>