aboutsummaryrefslogtreecommitdiffstats
path: root/man7/boot.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/boot.7')
-rw-r--r--man7/boot.718
1 files changed, 9 insertions, 9 deletions
diff --git a/man7/boot.7 b/man7/boot.7
index 7e22a8c0cd..ddc628a54a 100644
--- a/man7/boot.7
+++ b/man7/boot.7
@@ -11,7 +11,7 @@
.\"
.TH BOOT 7 2007-06-03 "Linux" "Linux Programmer's Manual"
.SH NAME
-boot\-scripts \- General description of boot sequence
+boot-scripts \- General description of boot sequence
.SH DESCRIPTION
.LP
The boot sequence varies in details among systems
@@ -20,20 +20,20 @@ but can be roughly divided to the following steps:
(iii) kernel startup, (iv) init and inittab,
(v) boot scripts.
We will describe each of these in more detail below.
-.SS "Hardware\-boot"
-After power\-on or hard reset, control is given
+.SS "Hardware-boot"
+After power-on or hard reset, control is given
to a program stored on read only memory (normally
PROM).
In PC we usually call this program the \fBBIOS\fR.
-This program normally makes a basic self\-test of the
-machine and accesses non\-volatile memory to read
+This program normally makes a basic self-test of the
+machine and accesses non-volatile memory to read
further parameters.
This memory in the PC is
-battery\-backed CMOS memory, so most people
+battery-backed CMOS memory, so most people
refer to it as the \fBCMOS\fR, although outside
of the PC world, it is usually called \fBnvram\fR
-(non\-volatile ram).
+(non-volatile ram).
The parameters stored in the nvram vary between
systems, but as a minimum, the hardware boot program
@@ -56,7 +56,7 @@ of the boot device \- this is the \fBMBR\fR
In most systems, this primary loader is very
limited due to various constraints.
-Even on non\-PC systems
+Even on non-PC systems
there are some limitations to the size and complexity
of this loader, but the size limitation of the PC MBR
(512 bytes including the partition table) makes it
@@ -110,7 +110,7 @@ This file defines what should be run in different \fIrun-levels\fR.
This gives the system administrator an easy management scheme, where
each run-level is associated with a set of services (e.g:
-\fBS\fR is \fIsingle\-user\fR, on \fB2\fR most network
+\fBS\fR is \fIsingle-user\fR, on \fB2\fR most network
services start, etc.).
The administrator may change the current
run-level via