aboutsummaryrefslogtreecommitdiffstats
path: root/man7/bootparam.7
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2008-03-19 07:26:08 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2008-03-19 07:26:08 +0000
commit24d01c530c5a3f75217543d02bf6712395e5f90c (patch)
tree0fff2e832ef0714ca1a56c5c70fad257b6471c14 /man7/bootparam.7
parentbed47b47a76a796711a98870ef7d5cf4dc878af7 (diff)
downloadman-pages-24d01c530c5a3f75217543d02bf6712395e5f90c.tar.gz
s/filesystem/file system/
Diffstat (limited to 'man7/bootparam.7')
-rw-r--r--man7/bootparam.714
1 files changed, 7 insertions, 7 deletions
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 3165d951b8..62ee5acd24 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -168,7 +168,7 @@ to use Linux.
.TP
.B "'root=...'"
This argument tells the kernel what device is to be used as the root
-filesystem while booting.
+file system while booting.
The default of this setting is determined
at compile time, and usually is the value of the root device of the
system that the kernel was built on.
@@ -203,16 +203,16 @@ possible root devices in major/minor format is also accepted.
alternative.)
.TP
.BR 'ro' " and " 'rw'
-The 'ro' option tells the kernel to mount the root filesystem
-as 'readonly' so that filesystem consistency check programs (fsck)
+The 'ro' option tells the kernel to mount the root file system
+as 'readonly' so that file system consistency check programs (fsck)
can do their work on a quiescent file system.
No processes can
-write to files on the filesystem in question until it is 'remounted'
+write to files on the file system in question until it is 'remounted'
as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
(See also
.BR mount (8).)
-The 'rw' option tells the kernel to mount the root filesystem read/write.
+The 'rw' option tells the kernel to mount the root file system read/write.
This is the default.
The choice between read-only and read/write can also be set using
@@ -369,7 +369,7 @@ But while booting (or while constructing boot floppies)
it is often useful to load the floppy contents into a
ramdisk.
One might also have a system in which first
-some modules (for filesystem or hardware) must be loaded
+some modules (for file system or hardware) must be loaded
before the main disk can be accessed.
In Linux 1.3.48, ramdisk handling was changed drastically.
@@ -416,7 +416,7 @@ When this feature is enabled, the boot process will load the kernel
and an initial ramdisk; then the kernel converts initrd into
a "normal" ramdisk, which is mounted read-write as root device;
then /linuxrc is executed; afterwards the "real" root file system is mounted,
-and the initrd filesystem is moved over to /initrd; finally
+and the initrd file system is moved over to /initrd; finally
the usual boot sequence (e.g., invocation of /sbin/init) is performed.
For a detailed description of the initrd feature, see