-.\" -*- nroff -*-
.\" This man-page is Copyright (C) 1997 John S. Kallal
.\"
+.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and author(s) of this work.
+.\" %%%LICENSE_END
.\"
.\" If the you wish to distribute versions of this work under other
.\" conditions than the above, please contact the author(s) at the following
.fi
.PP
Also, support for both "RAM disk" and "Initial RAM disk"
-(e.g.
+(e.g.,
.BR CONFIG_BLK_DEV_RAM=y
and
.BR CONFIG_BLK_DEV_INITRD=y )
contents for a two-phase system boot-up.
.PP
In the first boot-up phase, the kernel starts up
-and mounts an initial root file-system from the contents of
+and mounts an initial root filesystem from the contents of
.I /dev/initrd
(e.g., RAM disk initialized by the boot loader).
In the second phase, additional drivers or other modules
are loaded from the initial root device's contents.
-After loading the additional modules, a new root file system
-(i.e., the normal root file system) is mounted from a
+After loading the additional modules, a new root filesystem
+(i.e., the normal root filesystem) is mounted from a
different device.
.\"
.\"
.\"
-.SS "Boot-up Operation"
+.SS Boot-up operation
When booting up with
.BR initrd ,
the system boots as follows:
.IP 3.
The kernel then read-write mounts the device
.I /dev/ram0
-as the initial root file system.
+as the initial root filesystem.
.IP 4.
-If the indicated normal root file system is also the initial
-root file-system (e.g.
+If the indicated normal root filesystem is also the initial
+root filesystem (e.g.,
.IR /dev/ram0 )
then the kernel skips to the last step for the usual boot sequence.
.IP 5.
If the executable file
.IR /linuxrc
-is present in the initial root file-system,
+is present in the initial root filesystem,
.I /linuxrc
is executed with UID 0.
(The file
.I /linuxrc
is not executed or when
.I /linuxrc
-terminates, the normal root file system is mounted.
+terminates, the normal root filesystem is mounted.
(If
.I /linuxrc
-exits with any file-systems mounted on the initial root
-file-system, then the behavior of the kernel is
+exits with any filesystems mounted on the initial root
+filesystem, then the behavior of the kernel is
.BR UNSPECIFIED .
See the NOTES section for the current kernel behavior.)
.IP 7.
-If the normal root file system has a directory
+If the normal root filesystem has a directory
.IR /initrd ,
the device
.I /dev/ram0
.IR /
to
.IR /initrd .
-Otherwise if the directory
+Otherwise, if the directory
.IR /initrd
does not exist, the device
.I /dev/ram0
.IR /dev/ram0 .
If directory
.I /initrd
-does not exist on the normal root file system
+does not exist on the normal root filesystem
and any processes remain running from
.IR /dev/ram0
when
.IP 8.
The usual boot sequence (e.g., invocation of
.IR /sbin/init )
-is performed on the normal root file system.
+is performed on the normal root filesystem.
.\"
.\"
.\"
configuration file
.IR /etc/lilo.config .
The filename specified with this
-option will typically be a gzipped file-system image.
+option will typically be a gzipped filesystem image.
.TP
.I noinitrd
This boot option disables the two-phase boot-up operation.
loaded into memory by the boot loader contents are preserved.
This option permits the contents of
.I /dev/initrd
-to be any data and need not be limited to a file system image.
+to be any data and need not be limited to a filesystem image.
However, device
.I /dev/initrd
is read-only and can be read only one time after system startup.
.TP
.BI root= "device-name"
-Specifies the device to be used as the normal root file system.
+Specifies the device to be used as the normal root filesystem.
For
.B LOADLIN
this is a command-line option.
configuration file
.IR /etc/lilo.config .
The device specified by the this option must be a mountable
-device having a suitable root file-system.
+device having a suitable root filesystem.
.\"
.\"
.\"
-.SS "Changing the Normal Root File System"
+.SS Changing the normal root filesystem
By default,
the kernel's settings
(e.g., set in the kernel file with
.BR rdev (8)
or compiled into the kernel file),
or the boot loader option setting
-is used for the normal root file systems.
-For an NFS-mounted normal root file system, one has to use the
+is used for the normal root filesystems.
+For an NFS-mounted normal root filesystem, one has to use the
.B nfs_root_name
and
.B nfs_root_addrs
boot options to give the NFS settings.
For more information on NFS-mounted root see the kernel documentation file
.BR Documentation/filesystems/nfsroot.txt .
-For more information on setting the root file system see also the
+For more information on setting the root filesystem see also the
.BR LILO
and
.BR LOADLIN
.IR /proc/sys/kernel/nfs-root-addrs .
For a physical root device, the root device is changed by having
.I /linuxrc
-write the new root file system device number into
+write the new root filesystem device number into
.IR /proc/sys/kernel/real-root-dev .
-For an NFS root file system, the root device is changed by having
+For an NFS root filesystem, the root device is changed by having
.I /linuxrc
write the NFS setting into files
.IR /proc/sys/kernel/nfs-root-name
.BR Note :
The use of
.I /proc/sys/kernel/real-root-dev
-to change the root file system is obsolete.
-See the kernel source file
+to change the root filesystem is obsolete.
+See the Linux kernel source file
.I Documentation/initrd.txt
as well as
.BR pivot_root (2)
and
.BR pivot_root (8)
-for information on the modern method of changing the root file system.
-.\" FIXME the manual page should describe the pivot_root mechanism.
+for information on the modern method of changing the root filesystem.
+.\" FIXME . Should this manual page describe the pivot_root mechanism?
.\"
.\"
.\"
(e.g., support for
.IR /dev/ram ,
.IR /dev/initrd ,
-and the ext2 file-system) and loads
+and the ext2 filesystem) and loads
.IR /dev/initrd
-with a gzipped version of the initial file-system.
+with a gzipped version of the initial filesystem.
.IP 2.
The executable
.I /linuxrc
-determines what is needed to (1) mount the normal root file-system
-(i.e., device type, device drivers, file system) and (2) the
+determines what is needed to (1) mount the normal root filesystem
+(i.e., device type, device drivers, filesystem) and (2) the
distribution media (e.g., CD-ROM, network, tape, ...).
This can be done by asking the user, by auto-probing,
or by using a hybrid approach.
.IP 3.
The executable
.I /linuxrc
-loads the necessary modules from the initial root file-system.
+loads the necessary modules from the initial root filesystem.
.IP 4.
The executable
.I /linuxrc
-creates and populates the root file system.
-(At this stage the normal root file system does not have to be a
+creates and populates the root filesystem.
+(At this stage the normal root filesystem does not have to be a
completed system yet.)
.IP 5.
The executable
.IR /proc/sys/kernel/real-root-dev ,
unmount
.IR /proc ,
-the normal root file system and any other file
-systems it has mounted, and then terminates.
+the normal root filesystem and any other filesystems
+it has mounted, and then terminates.
.IP 6.
-The kernel then mounts the normal root file system.
+The kernel then mounts the normal root filesystem.
.IP 7.
-Now that the file system is accessible and intact,
+Now that the filesystem is accessible and intact,
the boot loader can be installed.
.IP 8.
The boot loader is configured to load into
.I /dev/initrd
-a file system with the set of modules that was used to bring up the system.
+a filesystem with the set of modules that was used to bring up the system.
(e.g., Device
.I /dev/ram0
can be modified, then unmounted, and finally, the image is written from
would be different.
.PP
A third scenario is more convenient recovery disks.
-Because information like the location of the root file-system
+Because information like the location of the root filesystem
partition is not needed at boot time, the system loaded from
.I /dev/initrd
can use a dialog and/or auto-detection followed by a
.\"
.SH NOTES
.IP 1. 3
-With the current kernel, any file systems that remain mounted when
+With the current kernel, any filesystems that remain mounted when
.I /dev/ram0
is moved from
.I /
.B not
be fully unmounted if
.I /dev/ram0
-is used by any process or has any file-system mounted on it.
+is used by any process or has any filesystem mounted on it.
If
.IR /dev/ram0
is
.\" The code for
.\" .BR initrd
.\" was added to the baseline Linux kernel in development version 1.3.73.
-.SH "SEE ALSO"
+.SH SEE ALSO
.BR chown (1),
.BR mknod (1),
.BR ram (4),
.BR freeramdisk (8),
.BR rdev (8)
-The documentation file
-.I initrd.txt
-in the kernel source package, the LILO documentation,
-the LOADLIN documentation, the SYSLINUX documentation.
+.I Documentation/initrd.txt
+in the Linux kernel source tree, the LILO documentation,
+the LOADLIN documentation, the SYSLINUX documentation
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
OSDN Git Service
