os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Consistancy checks: s/file system/filesystem/g

Browse source
This commit is contained in:
Tom Rhodes 2002-05-16 01:42:28 +00:00
parent 09da6dffce
commit 9ba764ae23
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13100
16 changed files with 124 additions and 124 deletions
en_US.ISO8859-1
articles
multi-os
article.sgml
new-users
article.sgml
solid-state
article.sgml
vinum
article.sgml
books
arch-handbook/driverbasics
chapter.sgml
developers-handbook
driverbasics
chapter.sgml
kerneldebug
chapter.sgml
secure
chapter.sgml
tools
chapter.sgml
faq
book.sgml
handbook
advanced-networking
chapter.sgml
basics
chapter.sgml
boot
chapter.sgml
config
chapter.sgml
disks
chapter.sgml
install
chapter.sgml

6
en_US.ISO8859-1/articles/multi-os/article.sgml
View file

@ -126,7 +126,7 @@
<para>FAT32 is the replacement to the FAT filesystem included in
Microsoft's OEM SR2 Beta release, which started replacing FAT
on computers pre-loaded with Windows 95 towards the
end of 1996. It converts the normal FAT file system and
end of 1996. It converts the normal FAT filesystem and
allows you to use smaller cluster sizes for larger hard
drives. FAT32 also modifies the traditional FAT boot sector
and allocation table, making it incompatible with some boot
@ -288,12 +288,12 @@ Press Esc to continue
partitions, but not FFS (FreeBSD) or EXT2 (Linux) partitions.
Likewise, Windows 95 can only read and write to FAT and FAT32
(see <xref linkend="ch2">) partitions. FreeBSD can read most
file systems, but currently cannot read HPFS partitions. Linux
filesystems, but currently cannot read HPFS partitions. Linux
can read HPFS partitions, but can not write to them. Recent
versions of the Linux kernel (2.x) can read and write to Windows
95 VFAT partitions (VFAT is what gives Windows 95 long file
names - it is pretty much the same as FAT). Linux can read and
write to most file systems. Got that? I hope so.</para>
write to most filesystems. Got that? I hope so.</para>
</sect1>
<sect1 id="ch5">

8
en_US.ISO8859-1/articles/new-users/article.sgml
View file

@ -757,7 +757,7 @@
<term><command>man hier</command></term>
<listitem>
<para>man page on the Unix file system</para>
<para>man page on the Unix filesystem</para>
</listitem>
</varlistentry>
</variablelist>
@ -775,7 +775,7 @@
(which should be in quotes). If you tell
<command>find</command> to search in <filename>/</filename>
instead of <filename>/usr</filename> it will look for the
file(s) on all mounted file systems, including the CDROM and the
file(s) on all mounted filesystems, including the CDROM and the
DOS partition.</para>
<para>An excellent book that explains Unix commands and utilities
@ -1029,9 +1029,9 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
drive. The most recent versions of FreeBSD let you mount the
CDROM with just <command>/sbin/mount /cdrom</command>.</para>
<para>Using the live file system&mdash;the second of FreeBSD's
<para>Using the live filesystem&mdash;the second of FreeBSD's
CDROM disks&mdash;is useful if you have got limited space. What
is on the live file system varies from release to release. You
is on the live filesystem varies from release to release. You
might try playing games from the CDROM. This involves using
<command>lndir</command>, which gets installed with the X Window
System, to tell the program(s) where to find the necessary

12
en_US.ISO8859-1/articles/solid-state/article.sgml
View file

@ -74,7 +74,7 @@
that are of interest in such an environment, the
<filename>rc.diskless</filename> mechanisms that automate the
initialization of such systems and the need for read-only filesystems,
and building file systems from scratch. The article will conclude
and building filesystems from scratch. The article will conclude
with some general strategies for small and read-only FreeBSD
environments.</para>
</abstract>
@ -193,7 +193,7 @@ pseudo-device md # memory disk</programlisting>
and replaced it with a symbolic link to <filename>/var/tmp</filename>.
Because <filename>tmp</filename> is one of the directories created in
<filename>/var</filename> by the <filename>/etc/rc.diskless2</filename>
script, and because <filename>/var</filename> is a memory file system
script, and because <filename>/var</filename> is a memory filesystem
(which is mounted read-write), <filename>/tmp</filename> will now be a
directory that is read-write as well.</para>
@ -298,7 +298,7 @@ pseudo-device md # memory disk</programlisting>
</step>
<step>
<title>Creating file systems on your flash memory device</title>
<title>Creating filesystems on your flash memory device</title>
<para>Exit the custom installation menu, and from the main
installation menu choose the <literal>fixit</literal> option. After
@ -416,7 +416,7 @@ pseudo-device md # memory disk</programlisting>
<screen><prompt>ftp></prompt> <userinput>get tarfile.tar "| zcat | tar xvf -"</userinput></screen>
<para>After the contents of your tarred filesystem are on your flash
memory file system, you can unmount the flash memory and
memory filesystem, you can unmount the flash memory and
reboot:</para>
<screen>&prompt.root; <userinput>cd /</userinput>
@ -584,7 +584,7 @@ pseudo-device md # memory disk</programlisting>
<para>where <replaceable>20010412</replaceable> is a date that is
appropriate for your particular release of FreeBSD</para>
<para>Now, any time that you mount your file systems as read-write and
<para>Now, any time that you mount your filesystems as read-write and
install a package, the <command>make install</command> will work
because it finds a suitable
<filename>/var/db/port.mkversion</filename>, and package information
@ -599,7 +599,7 @@ pseudo-device md # memory disk</programlisting>
<para>Apache keeps pid files and logs in
<filename><replaceable>apache_install</replaceable>/logs</filename>.
Since this directory no doubt exists on a read-only file system, this
Since this directory no doubt exists on a read-only filesystem, this
will not work. It is necessary to add a new directory to the
<filename>/etc/rc.diskless2</filename> list of directories to create
in <filename>/var</filename>, to link

94
en_US.ISO8859-1/articles/vinum/article.sgml
View file

@ -20,8 +20,8 @@
<year>2001</year>
<holder>Robert A. Van Valzah</holder>
</copyright>
<pubdate>$Date: 2002-02-28 02:55:01 $ GMT</pubdate>
<releaseinfo>$Id: article.sgml,v 1.6 2002-02-28 02:55:01 keramida Exp $</releaseinfo>
<pubdate>$Date: 2002-05-16 01:42:03 $ GMT</pubdate>
<releaseinfo>$Id: article.sgml,v 1.7 2002-05-16 01:42:03 trhodes Exp $</releaseinfo>
</articleinfo>
<abstract>
@ -63,7 +63,7 @@
<para>&vinum.ap;
is a volume manager for FreeBSD that provides a standard block
I/O layer interface to the file system code just as any hardware
I/O layer interface to the filesystem code just as any hardware
device driver would.
It works by managing partitions
of type <literal>vinum</literal> and
@ -74,7 +74,7 @@
Volumes can
be configured for resilience, performance, or both. Experienced
system administrators will immediately recognize the benefits
of being able to configure each file system to match the way
of being able to configure each filesystem to match the way
it is most often used.</para>
<para>In some ways, <application>Vinum</application> is similar to
@ -358,7 +358,7 @@
<application>Vinum</application> volume.</para>
<note><para><application>Vinum</application> currently does not
support the root file system (this feature
support the root filesystem (this feature
is in development).</para></note>
<para>Hence it is a bit
@ -509,7 +509,7 @@
</tip>
<para>The pros and cons discussed above suggest
that the root file system and swap partition are good
that the root filesystem and swap partition are good
candidates for hardware RAID if available.
This is especially true for servers where it is difficult for
administrators to get console access (recall that this is sometimes
@ -564,8 +564,8 @@
Instead, <application>Vinum</application>
objects are configured so that they occupy the
same disk space where <command>/stand/sysinstall</command> built
file systems.
The file systems are thus embedded within
filesystems.
The filesystems are thus embedded within
<application>Vinum</application> objects without copying.</para>
<para>There are several distinct phases to the
@ -593,9 +593,9 @@
<para>In phase 2, we will install a minimum FreeBSD system on a
single spindle using partitions of type
<literal>4.2BSD</literal> (regular UFS file systems).</para>
<literal>4.2BSD</literal> (regular UFS filesystems).</para>
<para>Phase 3 will embed the non-root file systems from phase 2 in
<para>Phase 3 will embed the non-root filesystems from phase 2 in
<application>Vinum</application> objects.
Note that <application>Vinum</application> will be up and
running at this point,
@ -603,8 +603,8 @@
one spindle on which to store data.</para>
<para>Finally in phase 4, we configure <application>Vinum</application>
on a second spindle and make a backup copy of the root file system.
This will give us resilience on all file systems.</para>
on a second spindle and make a backup copy of the root filesystem.
This will give us resilience on all filesystems.</para>
<section id="P1">
<title>Bootstrapping Phase 1: Planning and Preparation</title>
@ -624,7 +624,7 @@
<itemizedlist>
<listitem><para>
What file system and partitions will be needed?
What filesystem and partitions will be needed?
</para></listitem>
<listitem><para>
How will they be used?
@ -667,7 +667,7 @@
and swap partitions.
The root,
<filename>/usr</filename>, and
<filename>/home</filename> file systems all need resilience since the
<filename>/home</filename> filesystems all need resilience since the
server will not be much good without them.
The swap partition needs performance first and
generally does
@ -756,13 +756,13 @@
from these outer cylinders as
<command>/stand/sysinstall</command> generally does.</para>
<para>The root file system is traditionally the outermost, even though
<para>The root filesystem is traditionally the outermost, even though
it generally is not as critical to system performance as others.
(However root can have a larger impact on performance if it contains
<filename>/tmp</filename> and <filename>/var</filename> as it
does in this example.)
The FreeBSD boot loaders assume that the
root file system lives in the <literal>a</literal> partition.
root filesystem lives in the <literal>a</literal> partition.
There is no requirement that the <literal>a</literal>
partition start on the outermost cylinders, but this
convention makes it easier to manage disk labels.</para>
@ -778,14 +778,14 @@
<filename>/home</filename> and
<filename>/usr</filename>.
Access patterns here tend not to be as intense as for other
file systems (especially if there is an abundant supply of RAM
filesystems (especially if there is an abundant supply of RAM
and read cache hit rates are high).</para>
<para>If the pair of spindles you have are large enough to allow
for more than
<filename>/home</filename> and
<filename>/usr</filename>,
it is fine to plan for additional file systems here.</para>
it is fine to plan for additional filesystems here.</para>
</section
@ -794,7 +794,7 @@
<para>We will want to assign
partitions to these spindles so that either can fail
without loss of data on file systems configured for
without loss of data on filesystems configured for
resilience.</para>
<para>Reliability on
@ -803,7 +803,7 @@
is best achieved using <application>Vinum</application>
mirroring.
Resilience will have to come differently, however, for the root
file system since <application>Vinum</application>
filesystem since <application>Vinum</application>
is not a part of the FreeBSD boot sequence.
Here we will have to settle for two identical
partitions with a periodic copy from the primary to the
@ -830,7 +830,7 @@
(After &vinum.ap; is bootstrapped, there is nothing special
about either of these spindles--they are interchangeable.)
You can later use the remaining space on the rootback spindle for
other file systems.</para>
other filesystems.</para>
<para>If you have more than two spindles, the
<literal>bootvinum</literal> Perl script and the procedure
@ -868,7 +868,7 @@
<title>Assigning Partitions on the Root Spindle</title>
<para>We will allocate 200,000 blocks (about 93 MB)
for a root file system on each spindle
for a root filesystem on each spindle
(<devicename>/dev/ad0s1a</devicename> and
<devicename>/dev/ad2s1a</devicename>).
We will initially allocate 200,265 blocks for a swap partition
@ -1100,7 +1100,7 @@ Not to scale</literallayout>
<note>
<para>We do not really want to have a
<filename>/NOFUTURE</filename> UFS file system (we
<filename>/NOFUTURE</filename> UFS filesystem (we
want a vinum partition instead), but that is the
best choice we have for the space given the limitations of
<command>/stand/sysinstall</command>.
@ -1112,7 +1112,7 @@ Not to scale</literallayout>
<step>
<para>Partition any other spindles with swap if desired and a
single <filename>/NOFUTURExx</filename> file system.</para>
single <filename>/NOFUTURExx</filename> filesystem.</para>
</step>
<step>
@ -1147,7 +1147,7 @@ Not to scale</literallayout>
root spindle.
We will embed the existing
<filename>/usr</filename> and
<filename>/home</filename> file systems in a
<filename>/home</filename> filesystems in a
<application>Vinum</application> partition.
Note that the <application>Vinum</application>
volumes created will not yet be
@ -1166,7 +1166,7 @@ Not to scale</literallayout>
</step>
<step>
<para>We will need a directory in the root file system in
<para>We will need a directory in the root filesystem in
which to keep a few files that will be used in the
<application>Vinum</application>
bootstrapping process.</para>
@ -1272,7 +1272,7 @@ ok <userinput>boot -s</userinput</screen>
for the first time.
It is going to want to create several device nodes under
<filename>/dev/vinum</filename> so we will need to mount the
root file system for read/write access.</para>
root filesystem for read/write access.</para>
<screen>&prompt.root; <userinput>fsck -p /</userinput>
&prompt.root; <userinput>mount /</userinput></screen>
@ -1281,7 +1281,7 @@ ok <userinput>boot -s</userinput</screen>
<step>
<para>Now it is time to create the <application>Vinum</application>
objects that
will embed the existing non-root file systems on
will embed the existing non-root filesystems on
the root spindle in a
<application>Vinum</application> partition.
This will load the <application>Vinum</application>
@ -1314,7 +1314,7 @@ S usr.p0.s0 State: up PO: 0 B Size: 1330 MB</screen>
</step>
<step>
<para>Our non-root file systems should now be embedded in a
<para>Our non-root filesystems should now be embedded in a
<application>Vinum</application> partition and
hence available through <application>Vinum</application>
volumes.
@ -1334,7 +1334,7 @@ S usr.p0.s0 State: up PO: 0 B Size: 1330 MB</screen>
</step>
<step>
<para>While we have the root file system mounted read/write, this is
<para>While we have the root filesystem mounted read/write, this is
a good time to install <filename>/etc/fstab</filename>.</para>
<screen>&prompt.root; <userinput>mv /etc/fstab /etc/fstab.b4vinum</userinput>
@ -1371,7 +1371,7 @@ S usr.p0.s0 State: up PO: 0 B Size: 1330 MB</screen>
to copy the data from the root spindle to the
rootback spindle.
Finally, we use <command>dump</command> and <command>restore</command>
to copy the root file system.</para>
to copy the root filesystem.</para>
<section id="P4E">
<title>Phase 4 Example</title>
@ -1485,7 +1485,7 @@ S usr.p1.s0 State: up PO: 0 B Size: 1330 MB</screen>
</step>
<step>
<para>Copy the root file system so that you will have a backup.</para>
<para>Copy the root filesystem so that you will have a backup.</para>
<screen>&prompt.root; <userinput>cd /rootback</userinput>
&prompt.root; <userinput>dump 0f - / | restore rf -</userinput>
@ -1501,7 +1501,7 @@ abort? [yn] <userinput>n</userinput>
expected next file 492, got 491</screen>
<para>They seem to cause no harm.
I suspect they are a consequence of dumping the file system
I suspect they are a consequence of dumping the filesystem
containing <filename>/tmp</filename> and/or the pipe
connecting <command>dump</command> and
<command>restore</command>.</para>
@ -1511,7 +1511,7 @@ expected next file 492, got 491</screen>
<step>
<para>Make a directory on which we can mount a damaged root
file system during the recovery process.</para>
filesystem during the recovery process.</para>
<screen>&prompt.root; <userinput>mkdir /rootbad</userinput></screen>
@ -1670,7 +1670,7 @@ expected next file 492, got 491</screen>
case, being careful not to interfere with ventilation.</para></tip>
<section id="ad0RootBad">
<title>Root file system on ad0 unusable, rest of drive ok</title>
<title>Root filesystem on ad0 unusable, rest of drive ok</title>
<note>
<para>We assume here that the boot blocks and disk label on
@ -1704,7 +1704,7 @@ expected next file 492, got 491</screen>
<para>After the kernel is loaded, hit any key but enter to interrupt
the boot sequence.
Boot into single-user mode and allow explicit entry of
a root file system.</para>
a root filesystem.</para>
<screen>Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel] in 8 seconds...
@ -1716,9 +1716,9 @@ ok <userinput>boot -as</userinput</screen>
<step>
<para>Select <filename>/rootback</filename>
as your root file system.</para>
as your root filesystem.</para>
<screen>Manual root file system specification:
<screen>Manual root filesystem specification:
&lt;fstype>:&lt;device> Mount &lt;device> using filesystem &lt;fstype>
e.g. ufs:/dev/da0s1a
? List valid disk boot devices
@ -1730,7 +1730,7 @@ ok <userinput>boot -as</userinput</screen>
<step>
<para>Now that you are in single-user mode, change
<filename>/etc/fstab</filename> to avoid the
bad root file system.</para>
bad root filesystem.</para>
<tip>
<para>If you used the <literal>bootvinum</literal> Perl script from <xref linkend=Perl>
@ -1982,7 +1982,7 @@ ok <userinput>boot -s</userinput</screen>
<step>
<para>Now we need to restore
<filename>/rootback</filename> to a current copy of the
root file system.
root filesystem.
These commands will accomplish this.</para>
<screen>&prompt.root; <userinput>newfs /dev/ad2s1a</userinput>
@ -2032,7 +2032,7 @@ ok <userinput>boot -s</userinput</screen>
</step>
<step>
<para>Unmount all non-root file systems.</para>
<para>Unmount all non-root filesystems.</para>
</step>
<step>
@ -2087,13 +2087,13 @@ ok <userinput>boot -s</userinput</screen>
use strict;
use FileHandle;
my $config_tag1 = '$Id: article.sgml,v 1.6 2002-02-28 02:55:01 keramida Exp $';
my $config_tag1 = '$Id: article.sgml,v 1.7 2002-05-16 01:42:03 trhodes Exp $';
# Copyright (C) 2001 Robert A. Van Valzah
#
# Bootstrap Vinum
#
# Read /etc/fstab and current partitioning for all spindles mentioned there.
# Generate files needed to mirror all file systems on root spindle.
# Generate files needed to mirror all filesystems on root spindle.
# A new partition table for each spindle
# Input for the vinum create command to create Vinum objects on each spindle
# A copy of fstab mounting Vinum volumes instead of BSD partitions
@ -2106,7 +2106,7 @@ my $config_tag1 = '$Id: article.sgml,v 1.6 2002-02-28 02:55:01 keramida Exp $';
# Expectations:
# The root spindle must contain at least root, swap, and /usr partitions
# The rootback spindle must have matching /rootback and swap partitions
# Other spindles should only have a /NOFUTURE* file system and maybe swap
# Other spindles should only have a /NOFUTURE* filesystem and maybe swap
# File systems named /NOFUTURE* will be replaced with Vinum drives
# Change configuration variables below to suit your taste
@ -2120,7 +2120,7 @@ my @spndl; # One entry per SPiNDLe
my $rsp; # Root SPindle (as in /dev/$rsp)
my $rbsp; # RootBack SPindle (as in /dev/$rbsp)
my $cfgsiz = 265; # Size of Vinum on-disk configuration info in sectors
my $nxtpas = 2; # Next fsck pass number for non-root file systems
my $nxtpas = 2; # Next fsck pass number for non-root filesystems
# Parse fstab, generating the version we'll need for Vinum and noting
# spindles in use.
@ -2148,7 +2148,7 @@ while (&lt;FSIN>) {
print FSOUT "$dev\t\t$mnt\t$fstyp\t$opt\t\t$dump\t$pass\n";
next;
}
# Move non-root file systems on smallest spindle into Vinum
# Move non-root filesystems on smallest spindle into Vinum
if (defined($rsp) && $dev =~ /^\/dev\/$rsp/ && $dev =~ /[d-h]$/) {
$pass = $nxtpas++;
print FSOUT "/dev/vinum$mnt\t\t$mnt\t\t$fstyp\t$opt\t\t$dump\t$pass\n";
@ -2282,7 +2282,7 @@ foreach my $i (0..$#spndl) {
# Make a Vinum partition the size of all non-root, non-swap,
# non-c partitions + the size of Vinum's on-disk configuration.
# Set its offset so that the start of the first subdisk it contains
# coincides with the first file system we're embedding in Vinum.
# coincides with the first filesystem we're embedding in Vinum.
printf DLOUT "%4s%9d%9d%10s\n", "$vip:", $totsiz+$cfgsiz, $minoff-$cfgsiz,
'vinum';
} else {

2
en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml
View file

@ -28,7 +28,7 @@
<para>Most devices in a Unix-like operating system are accessed
through device-nodes, sometimes also called special files.
These files are usually located under the directory
<filename>/dev</filename> in the file system hierarchy. Until
<filename>/dev</filename> in the filesystem hierarchy. Until
devfs is fully integrated into FreeBSD, each device node must be
created statically and independent of the existence of the
associated device driver. Most device nodes on the system are

2
en_US.ISO8859-1/books/developers-handbook/driverbasics/chapter.sgml
View file

@ -28,7 +28,7 @@
<para>Most devices in a Unix-like operating system are accessed
through device-nodes, sometimes also called special files.
These files are usually located under the directory
<filename>/dev</filename> in the file system hierarchy. Until
<filename>/dev</filename> in the filesystem hierarchy. Until
devfs is fully integrated into FreeBSD, each device node must be
created statically and independent of the existence of the
associated device driver. Most device nodes on the system are

4
en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
View file

@ -72,7 +72,7 @@
then perform the following steps:</para>
<screen>&prompt.root; <userinput>fsck -p</userinput>
&prompt.root; <userinput>mount -a -t ufs</userinput> # so your file system for /var/crash is writable
&prompt.root; <userinput>mount -a -t ufs</userinput> # so your filesystem for /var/crash is writable
&prompt.root; <userinput>savecore -N /kernel.panicked /var/crash</userinput>
&prompt.root; <userinput>exit</userinput> # ...to multi-user</screen>
@ -480,7 +480,7 @@
<para>Which might be a good way to cleanly shut down the running system,
<function>sync()</function> all disks, and finally reboot. As long as
the disk and file system interfaces of the kernel are not damaged, this
the disk and filesystem interfaces of the kernel are not damaged, this
might be a good way for an almost clean shutdown.</para>
<screen><userinput>call cpu_reset()</userinput></screen>

2
en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml
View file

@ -456,7 +456,7 @@ int main() {
<para>An application should never assume that anything about the
users environment is sane. This includes (but is certainly not
limited to): user input, signals, environment variables,
resources, IPC, mmaps, the file system working directory, file
resources, IPC, mmaps, the filesystem working directory, file
descriptors, the # of open files, etc.</para>
<indexterm><primary>positive filtering</primary></indexterm>

2
en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml
View file

@ -361,7 +361,7 @@
</step>
<step>
<para>Finally, write the executable on the file system.</para>
<para>Finally, write the executable on the filesystem.</para>
</step>
</procedure>

10
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -1320,7 +1320,7 @@ File: +DESC (ignored)</screen>
<listitem>
<para>Boot the FreeBSD boot floppy (or CDROM) and choose the
<quote>Fixit</quote> menu item. Select either the Fixit
floppy or CDROM #2 (the <quote>live</quote> file system
floppy or CDROM #2 (the <quote>live</quote> filesystem
option) as appropriate and enter the fixit shell. Then
execute the following command:</para>
@ -5289,7 +5289,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
mode, it is not required.</para>
<para>You should never use anything but &man.dump.8; and
&man.restore.8; to move the root file system. The
&man.restore.8; to move the root filesystem. The
&man.tar.1; command may work - then again, it may not.
You should also use &man.dump.8; and &man.restore.8;
if you are moving a single partition to another empty
@ -5865,7 +5865,7 @@ C:\="DOS"</programlisting>
<para>Unless it is a floppy, or a removable you plan on sharing
with other people, it is probably a better idea to stick a BSD
file system on it. You will get long filename support, at least a
filesystem on it. You will get long filename support, at least a
2X improvement in performance, and a lot more stability. First,
you need to redo the DOS-level partitions/filesystems. You can
either use &man.fdisk.8; or
@ -5883,7 +5883,7 @@ C:\="DOS"</programlisting>
swap space on a fixed disk, but it is probably irrelevant on a
removable drive like a ZIP.</para>
<para>Finally, create a new file system, this one is on our ZIP
<para>Finally, create a new filesystem, this one is on our ZIP
drive using the whole disk:</para>
<screen>&prompt.root; <userinput>newfs /dev/rda2c</userinput></screen>
@ -6404,7 +6404,7 @@ C:\="DOS"</programlisting>
</listitem>
<listitem>
<para>Put the quota file on the file system that the quotas
<para>Put the quota file on the filesystem that the quotas
are to be enforced on. ie:</para>
<informaltable frame="none">

20
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -28,7 +28,7 @@
</listitem>
<listitem>
<para>How to setup a network file system.</para>
<para>How to setup a network filesystem.</para>
</listitem>
<listitem>
@ -668,7 +668,7 @@ host2.example.com link#1 UC 0 0
<title>NFS</title>
<indexterm><primary>NFS</primary></indexterm>
<para>Among the many different file systems that FreeBSD supports is
<para>Among the many different filesystems that FreeBSD supports is
the Network File System, also known as <acronym>NFS</acronym>.
<acronym>NFS</acronym> allows a system to share directories and files
with others over a network. By using <acronym>NFS</acronym>, users and
@ -809,9 +809,9 @@ mountd_flags="-r"</programlisting>
three example machines that have the same domain name as the server
(hence the lack of a domain name for each) or have entries in your
<filename>/etc/hosts</filename> file. The <option>-ro</option>
flag makes the exported file system read-only. With this flag, the
flag makes the exported filesystem read-only. With this flag, the
remote system will not be able to write any changes to the
exported file system.</para>
exported filesystem.</para>
<programlisting>/cdrom -ro host1 host2 host3</programlisting>
@ -902,7 +902,7 @@ mountd_flags="-r"</programlisting>
system. In these examples the
server's name will be <literal>server</literal> and the client's
name will be <literal>client</literal>. If you only want to
temporarily mount a remote file system or would rather test the
temporarily mount a remote filesystem or would rather test the
configuration, just execute a command like this as <username>root</username> on the
client:</para>
<indexterm>
@ -1087,7 +1087,7 @@ Exports list on foobar:
<emphasis>server</emphasis>, include the option
<option>-w=1024</option> on the mount from the client. If the
FreeBSD system is the <emphasis>client</emphasis>, then mount the
NFS file system with the option <option>-r=1024</option>. These
NFS filesystem with the option <option>-r=1024</option>. These
options may be specified using the fourth field of the
<filename>fstab</filename> entry on the client for automatic
mounts, or by using the <option>-o</option> parameter of the mount
@ -1107,7 +1107,7 @@ Exports list on foobar:
<filename>/sharedfs</filename> will be the exported NFS
filesystem (see &man.exports.5;), and
<filename>/project</filename> will be the mount point on the
client for the exported file system. In all cases, note that
client for the exported filesystem. In all cases, note that
additional options, such as <option>hard</option> or
<option>soft</option> and <option>bg</option> may be desirable in
your application.</para>
@ -1181,7 +1181,7 @@ Exports list on foobar:
<indexterm><primary>diskless operation</primary></indexterm>
<para>A FreeBSD machine can boot over the network and operate without a
local disk, using file systems mounted from an NFS server. No system
local disk, using filesystems mounted from an NFS server. No system
modification is necessary, beyond standard configuration files.
Such a system is easy to set up because all the necessary elements
are readily available:</para>
@ -1238,7 +1238,7 @@ Exports list on foobar:
<para>The diskless workstations use a shared
read-only <filename>root</filename> filesystem, and a shared
read-only <filename>/usr</filename>.</para>
<para>The <filename>root</filename> file system is a copy of a
<para>The <filename>root</filename> filesystem is a copy of a
standard FreeBSD root (typically the server's), with some
configuration files overridden by ones specific to diskless
operation or, possibly, to the workstation they belong to.</para>
@ -1644,7 +1644,7 @@ Exports list on foobar:
<title>Using a non-FreeBSD Server</title>
<para>When the server for the root filesystem is not running FreeBSD,
you will have to create the root file system on a
you will have to create the root filesystem on a
FreeBSD machine, then copy it to its destination, using
<command>tar</command> or <command>cpio</command>.</para>
<para>In this situation, there are sometimes

14
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -205,17 +205,17 @@
<quote>/</quote>. This directory is the first one mounted at
boot time and it contains the base system necessary to prepare
the operating system for multi-user operation. The root
directory also contains mount points for every other file system
directory also contains mount points for every other filesystem
that you may want to mount.</para>
<para>A mount point is a directory where additional file systems can
be grafted onto the root file system. Standard mount points include
<para>A mount point is a directory where additional filesystems can
be grafted onto the root filesystem. Standard mount points include
<filename>/usr</filename>, <filename>/var</filename>,
<filename>/mnt</filename>, and <filename>/cdrom</filename>. These
directories are usually referenced to entries in the file
<filename>/etc/fstab</filename>. <filename>/etc/fstab</filename> is
a table of various file systems and mount points for reference by the
system. Most of the file systems in <filename>/etc/fstab</filename>
a table of various filesystems and mount points for reference by the
system. Most of the filesystems in <filename>/etc/fstab</filename>
are mounted automatically at boot time from the script &man.rc.8;
unless they contain the <option>noauto</option> option. Consult the
&man.fstab.5; manual page for more information on the format of the
@ -306,7 +306,7 @@
<row>
<entry><filename class="directory">/proc/</filename></entry>
<entry>Process file system; see &man.procfs.5;,
<entry>Process filesystem; see &man.procfs.5;,
&man.mount.procfs.8;.</entry>
</row>
@ -1327,7 +1327,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<sect3>
<title>devfs (Device File System)</title>
<para> The device file system, or devfs, provides access to
<para> The device filesystem, or devfs, provides access to
kernel's device namespace in the global filesystem namespace.
Instead of having to create and modify device nodes,
devfs maintains this particular filesystem for you.</para>

2
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -512,7 +512,7 @@ boot:</screen>
<listitem>
<para>during kernel initialization, ask for the device
to mount as the root file system.</para>
to mount as the root filesystem.</para>
</listitem>
</varlistentry>

4
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -960,9 +960,9 @@ kern.maxfiles: 2088 -> 5000</screen>
the filesystem. If there is a failure during an operation
that updated large amounts of meta-data (like a power
failure, or someone pressing the reset button),
the file system
the filesystem
will be left in an unpredictable state. There is no opportunity
to examine the state of the file system when the system
to examine the state of the filesystem when the system
comes up again; the data blocks of a file could already have
been written to the disk while the updates of the inode
table or the associated directory were not. It is actually

62
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -233,9 +233,9 @@
<para><application>sysinstall</application>'s Label editor
favors the <literal>e</literal>
partition for non-root, non-swap partitions. Within the
Label editor, create a single file system by typing
Label editor, create a single filesystem by typing
<userinput>C</userinput>. When prompted if this will be a FS
(file system) or swap, choose <literal>FS</literal> and type in a
(filesystem) or swap, choose <literal>FS</literal> and type in a
mount point (e.g, <filename>/mnt</filename>). When adding a
disk in post-install mode, <application>sysinstall</application>
will not create entries
@ -243,7 +243,7 @@
you specify is not important.</para>
<para>You are now ready to write the new label to the disk and
create a file system on it. Do this by typing
create a filesystem on it. Do this by typing
<userinput>W</userinput>. Ignore any errors from
<application>sysinstall</application> that
it could not mount the new partition. Exit the Label Editor
@ -461,10 +461,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
</indexterm>
<para>For finer control over your quota startup, there is an
additional configuration variable available. Normally on bootup,
the quota integrity of each file system is checked by the
the quota integrity of each filesystem is checked by the
<command>quotacheck</command> program. The
<command>quotacheck</command> facility insures that the data in
the quota database properly reflects the data on the file system.
the quota database properly reflects the data on the filesystem.
This is a very time consuming process that will significantly
affect the time your system takes to boot. If you would like to
skip this step, a variable in <filename>/etc/rc.conf</filename>
@ -479,13 +479,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<programlisting>check_quotas=<quote>YES</quote></programlisting>
<para>Finally you will need to edit <filename>/etc/fstab</filename>
to enable disk quotas on a per-file system basis. This is where
to enable disk quotas on a per-filesystem basis. This is where
you can either enable user or group quotas or both for all of your
file systems.</para>
filesystems.</para>
<para>To enable per-user quotas on a file system, add the
<para>To enable per-user quotas on a filesystem, add the
<literal>userquota</literal> option to the options field in the
<filename>/etc/fstab</filename> entry for the file system you want
<filename>/etc/fstab</filename> entry for the filesystem you want
to enable quotas on. For example:</para>
<programlisting>/dev/da1s2g /home ufs rw,userquota 1 2</programlisting>
@ -498,7 +498,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<programlisting>/dev/da1s2g /home ufs rw,userquota,groupquota 1 2</programlisting>
<para>By default, the quota files are stored in the root directory of
the file system with the names <filename>quota.user</filename> and
the filesystem with the names <filename>quota.user</filename> and
<filename>quota.group</filename> for user and group quotas
respectively. See &man.fstab.5; for more
information. Even though the &man.fstab.5; manual page says that
@ -535,7 +535,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<screen>&prompt.root; <userinput>quota -v</userinput></screen>
<para>You should see a one line summary of disk usage and current
quota limits for each file system that quotas are enabled
quota limits for each filesystem that quotas are enabled
on.</para>
<para>You are now ready to start assigning quota limits with the
@ -552,7 +552,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>A hard limit may not be exceeded. Once a user reaches his
hard limit he may not make any further allocations on the file
system in question. For example, if the user has a hard limit of
500 blocks on a file system and is currently using 490 blocks, the
500 blocks on a filesystem and is currently using 490 blocks, the
user can only allocate an additional 10 blocks. Attempting to
allocate an additional 11 blocks will fail.</para>
@ -581,7 +581,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
/usr/var: blocks in use: 0, limits (soft = 50, hard = 75)
inodes in use: 0, limits (soft = 50, hard = 60)</programlisting>
<para>You will normally see two lines for each file system that has
<para>You will normally see two lines for each filesystem that has
quotas enabled. One line for the block limits, and one line for
inode limits. Simply change the value you want updated to modify
the quota limit. For example, to raise this user's block limit
@ -626,12 +626,12 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
is a member of. Only the super-user may view all user and group
quotas. The
<command>repquota</command> command can be used to get a summary
of all quotas and disk usage for file systems with quotas
of all quotas and disk usage for filesystems with quotas
enabled.</para>
<para>The following is some sample output from the
<command>quota -v</command> command for a user that has quota
limits on two file systems.</para>
limits on two filesystems.</para>
<programlisting>Disk quotas for user test (uid 1002):
Filesystem blocks quota limit grace files quota limit grace
@ -639,18 +639,18 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
/usr/var 0 50 75 0 50 60</programlisting>
<indexterm><primary>grace period</primary></indexterm>
<para>On the <filename>/usr</filename> file system in the above
<para>On the <filename>/usr</filename> filesystem in the above
example, this user is currently 15 blocks over the soft limit of
50 blocks and has 5 days of the grace period left. Note the
asterisk <literal>*</literal> which indicates that the user is
currently over his quota limit.</para>
<para>Normally file systems that the user is not using any disk
<para>Normally filesystems that the user is not using any disk
space on will not show up in the output from the
<command>quota</command> command, even if he has a quota limit
assigned for that file system. The <option>-v</option> option
will display those file systems, such as the
<filename>/usr/var</filename> file system in the above
assigned for that filesystem. The <option>-v</option> option
will display those filesystems, such as the
<filename>/usr/var</filename> filesystem in the above
example.</para>
</sect2>
@ -714,8 +714,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<primary>filesystems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>The ISO 9660 file system was designed to deal with these
differences. It unfortunately codifies file system limits that were
<para>The ISO 9660 filesystem was designed to deal with these
differences. It unfortunately codifies filesystem limits that were
common then. Fortunately, it provides an extension mechanism that
allows properly written CDs to exceed those limits while still
working with systems that do not support those extensions.</para>
@ -749,8 +749,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2 id="mkisofs">
<title>mkisofs</title>
<para><command>mkisofs</command> produces an ISO 9660 file system
that is an image of a directory tree in the Unix file system name
<para><command>mkisofs</command> produces an ISO 9660 filesystem
that is an image of a directory tree in the Unix filesystem name
space. The simplest usage is:</para>
<screen>&prompt.root; <userinput>mkisofs <option>-o</option> <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
@ -760,11 +760,11 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<secondary>ISO-9660</secondary>
</indexterm>
<para>This command will create an <replaceable>imagefile</replaceable>
containing an ISO 9660 file system that is a copy of the tree at
containing an ISO 9660 filesystem that is a copy of the tree at
<replaceable>/path/to/tree</replaceable>. In the process, it will
map the file names to names that fit the limitations of the
standard ISO 9660 file system, and will exclude files that have
names uncharacteristic of ISO file systems.</para>
standard ISO 9660 filesystem, and will exclude files that have
names uncharacteristic of ISO filesystems.</para>
<indexterm>
<primary>filesystems</primary>
@ -778,13 +778,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
restrictions. In particular, <option>-R</option> enables the
Rock Ridge extensions common to Unix systems, <option>-J</option>
enables Joliet extensions used by Microsoft systems, and
<option>-hfs</option> can be used to create HFS file systems used
<option>-hfs</option> can be used to create HFS filesystems used
by MacOS.</para>
<para>For CDs that are going to be used only on FreeBSD systems,
<option>-U</option> can be used to disable all filename
restrictions. When used with <option>-R</option>, it produces a
file system image that is identical to the FreeBSD tree you started
filesystem image that is identical to the FreeBSD tree you started
from, though it may violate the ISO 9660 standard in a number of
ways.</para>
@ -800,13 +800,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<filename>/tmp/myboot</filename> holds a bootable FreeBSD system
with the boot image in
<filename>/tmp/myboot/boot/cdboot</filename>, you could produce the
image of an ISO 9660 file system in
image of an ISO 9660 filesystem in
<filename>/tmp/bootable.iso</filename> like so:</para>
<screen>&prompt.root; <userinput>mkisofs <option>-U</option> <option>-R</option> <option>-b</option> <filename>boot/cdboot</filename> <option>-o</option> <filename>/tmp/bootable.iso</filename> <filename>/tmp/myboot</filename></userinput></screen>
<para>Having done that, if you have <devicename>vn</devicename>
configured in your kernel, you can mount the file system with:</para>
configured in your kernel, you can mount the filesystem with:</para>
<screen>&prompt.root; <userinput>vnconfig <option>-e</option> <filename>vn0c</filename> <filename>/tmp/bootable.iso</filename></userinput>
&prompt.root; <userinput>mount <option>-t</option> cd9660 <filename>/dev/vn0c</filename> <filename>/mnt</filename></userinput></screen>

4
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -2192,7 +2192,7 @@ Mounting root from ufs:/dev/md0c
<entry>100MB</entry>
<entry>This is the root file system. Every other filesystem
<entry>This is the root filesystem. Every other filesystem
will be mounted somewhere under this one. 100MB is a
reasonable size for this filesystem. You will not be storing
too much data on it, as a regular FreeBSD install will put
@ -3170,7 +3170,7 @@ Upload subdirectory:
<screen> Message
Operating as an NFS server means that you must first configure an
/etc/exports file to indicate which hosts are allowed certain kinds of
access to your local file systems.
access to your local filesystems.
Press [Enter] now to invoke an editor on /etc/exports
[ OK ]</screen>