summaryrefslogtreecommitdiffstats
path: root/share/man/man8
diff options
context:
space:
mode:
authorru <ru@FreeBSD.org>2002-12-12 17:26:04 +0000
committerru <ru@FreeBSD.org>2002-12-12 17:26:04 +0000
commit041d1287e88250bf06ad159c6c696bd653a77957 (patch)
tree8a8960200349aa661a39654202f6e0adc5e7360e /share/man/man8
parent719bf117173e17f5286b995c031a11d553149e50 (diff)
downloadFreeBSD-src-041d1287e88250bf06ad159c6c696bd653a77957.zip
FreeBSD-src-041d1287e88250bf06ad159c6c696bd653a77957.tar.gz
Uniformly refer to a file system as "file system".
Approved by: re
Diffstat (limited to 'share/man/man8')
-rw-r--r--share/man/man8/crash.818
-rw-r--r--share/man/man8/diskless.810
-rw-r--r--share/man/man8/intro.84
-rw-r--r--share/man/man8/picobsd.820
-rw-r--r--share/man/man8/rc.82
5 files changed, 27 insertions, 27 deletions
diff --git a/share/man/man8/crash.8 b/share/man/man8/crash.8
index fc902f6..03d125a 100644
--- a/share/man/man8/crash.8
+++ b/share/man/man8/crash.8
@@ -58,7 +58,7 @@ and then invokes an automatic reboot procedure as
described in
.Xr reboot 8 .
Unless some unexpected inconsistency is encountered in the state
-of the filesystems due to hardware or software failure, the system
+of the file systems due to hardware or software failure, the system
will then resume multi-user operations.
.Pp
The system has a large number of internal consistency checks; if one
@@ -78,12 +78,12 @@ error produced the message in some unexpected way.
.Pp
.Bl -diag -compact
.It "cannot mount root"
-This panic message results from a failure to mount the root filesystem
+This panic message results from a failure to mount the root file system
during the bootstrap process.
-Either the root filesystem has been corrupted,
-or the system is attempting to use the wrong device as root filesystem.
+Either the root file system has been corrupted,
+or the system is attempting to use the wrong device as root file system.
Usually, an alternate copy of the system binary or an alternate root
-filesystem can be used to bring up the system to investigate.
+file system can be used to bring up the system to investigate.
Most often
this is done by the use of the boot floppy you used to install the system,
and then using the
@@ -95,7 +95,7 @@ This is not a panic message, as reboots are likely to be futile.
Late in the bootstrap procedure, the system was unable to locate
and execute the initialization process,
.Xr init 8 .
-The root filesystem is incorrect or has been corrupted, or the mode
+The root file system is incorrect or has been corrupted, or the mode
or type of
.Pa /sbin/init
forbids execution or is totally missing.
@@ -108,11 +108,11 @@ forbids execution or is totally missing.
.It "blkfree: freeing free frag"
.It "ifree: freeing free inode"
These panic messages are among those that may be produced
-when filesystem inconsistencies are detected.
-The problem generally results from a failure to repair damaged filesystems
+when file system inconsistencies are detected.
+The problem generally results from a failure to repair damaged file systems
after a crash, hardware failures, or other condition that should not
normally occur.
-A filesystem check will normally correct the problem.
+A file system check will normally correct the problem.
.Pp
.It "timeout table full"
This really should not be a panic, but until the data structure
diff --git a/share/man/man8/diskless.8 b/share/man/man8/diskless.8
index 63edc70..e6a49f1 100644
--- a/share/man/man8/diskless.8
+++ b/share/man/man8/diskless.8
@@ -38,7 +38,7 @@ The ability to boot a machine over the network is useful for
or
.Em dataless
machines, or as a temporary measure while repairing or
-re-installing filesystems on a local disk.
+re-installing file systems on a local disk.
This file provides a general description of the interactions between
a client and its server when a client is booting over the network.
.Sh OPERATION
@@ -80,7 +80,7 @@ loaded using TFTP or NFS.
.Pp
In phase 3, the kernel uses again DHCP or BOOTP to acquire
configuration information, and proceeds to mount the
-root filesystem and start operation.
+root file system and start operation.
Some specific actions performed during the startup
of a diskless system are listed in
.Pa /etc/rc.diskless1
@@ -155,7 +155,7 @@ The files and subdirectories within
.Pa /conf/default/etc
are used to bootstrap the diskless environment's
.Pa /etc
-memory filesystem.
+memory file system.
Be sure and copy the entirety of
.Pa /etc ,
and not just overrides.
@@ -208,7 +208,7 @@ local startup files will not be used.
.Pp
While an
.Xr md 4 Ns -backed
-filesystem is mounted on
+file system is mounted on
.Pa /var
by the startup scripts,
some sites may want to disable the saving of entropy by setting
@@ -248,7 +248,7 @@ This manpage is probably incomplete.
sometimes requires to write onto
the root partition, so the startup scripts create and mount
.Xr md 4 Ns -backed
-filesystems on some locations (e.g.\&
+file systems on some locations (e.g.\&
.Pa /etc
and
.Pa /var ) ,
diff --git a/share/man/man8/intro.8 b/share/man/man8/intro.8
index 415de10..04a99af 100644
--- a/share/man/man8/intro.8
+++ b/share/man/man8/intro.8
@@ -41,9 +41,9 @@
.Sh DESCRIPTION
This section contains information related to system operation
and maintenance.
-It describes commands used to create new filesystems,
+It describes commands used to create new file systems,
.Xr newfs 8 ,
-verify the integrity of the filesystems,
+verify the integrity of the file systems,
.Xr fsck 8 ,
control disk usage,
.Xr edquota 8 ,
diff --git a/share/man/man8/picobsd.8 b/share/man/man8/picobsd.8
index 8e7fd53..1aa0d67 100644
--- a/share/man/man8/picobsd.8
+++ b/share/man/man8/picobsd.8
@@ -30,15 +30,15 @@ in the server, it can be extremely useful to developers to
test their code without having to reinstall the system.
.Pp
The boot media (typically a floppy disk) contains a boot loader and a
-compressed kernel which includes a memory filesystem.
+compressed kernel which includes a memory file system.
Depending on the media, it might also contain a number of
additional files, which can be updated at run time, and are
-used to override/update those in the memory filesystem.
+used to override/update those in the memory file system.
.Pp
The system loads the kernel in the normal way, uncompresses
-the memory filesystem and mounts it as root.
+the memory file system and mounts it as root.
It then updates the memory
-filesystem with files from the boot media (if present),
+file system with files from the boot media (if present),
and executes a specialized version of
.Pa /etc/rc .
The boot media (floppy, etc.) is
@@ -96,8 +96,8 @@ commands to be executed and waiting for user
input before executing each of them.
Useful for debugging.
.It Fl -all_in_mfs
-Put the entire contents of the filesystem in the
-memory filesystem image which is contained in the
+Put the entire contents of the file system in the
+memory file system image which is contained in the
kernel.
This is the default behaviour, and is
extremely useful as the kernel itself can be loaded,
@@ -233,7 +233,7 @@ option:
options MD_ROOT_SIZE=4200 # same as def_sz
.Ed
.Pp
-This informs the script of the size of the memory filesystem and
+This informs the script of the size of the memory file system and
provides a few other details on how to build the image.
.It Pa crunch.conf
.Xr crunchgen 1
@@ -317,7 +317,7 @@ because only the files that are actually loaded from the image
contribute to the memory usage.
.It Va import_files
Contains a list of files to be imported in the floppy tree.
-Absolute names refer to the standard filesystem, relative
+Absolute names refer to the standard file system, relative
names refer to the root of the source tree being used
(i.e.\&
.Va SRC_PATH/.. ) .
@@ -494,7 +494,7 @@ ethernet.
.Pp
After booting,
.Nm
-loads the root filesystem from the memory filesystem, starts
+loads the root file system from the memory file system, starts
.Pa /sbin/init ,
and passes control to a first startup script,
.Pa /etc/rc .
@@ -504,7 +504,7 @@ and
.Pa /root
directories with the default files, then tries to identify the boot
device (floppy, hard disk partition) and possibly override the contents
-of the root filesystem with files read from the boot device.
+of the root file system with files read from the boot device.
This allows you to store local configuration on the same media.
After this phase the boot device is no longer used, unless the
user specifically does it.
diff --git a/share/man/man8/rc.8 b/share/man/man8/rc.8
index f299111..b82da37 100644
--- a/share/man/man8/rc.8
+++ b/share/man/man8/rc.8
@@ -379,7 +379,7 @@ the script does not do anything.
The
.Nm rc.early
script is run very early in the startup process, immediately before the
-filesystem check.
+file system check.
The
.Nm rc.early
script is deprecated.
OpenPOWER on IntegriCloud