Package: lilo
Version: 1:22.6.1-7
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man5/lilo.conf.5.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages lilo depends on:
ii debconf 1.4.58 Debian configuration management sy
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libdevmapper1.01 2:1.01.05-1 The Linux Kernel Device Mapper use
lilo recommends no packages.
-- debconf information excluded
--- - 2005-10-01 03:44:31.686064000 -0400
+++ /tmp/liloconf.5.gz.19620 2005-10-01 03:44:31.000000000 -0400
@@ -173,7 +173,7 @@
countdown timer. <x>,<y>
specifies the character (or pixel) coordinate of the location of the timer
the same as 'bmp-table='
-above; and the color triple specifes the character color attributes
+above; and the color triple specifies the character color attributes
the same as 'bmp-colors=' above, with the exception that the background color
.I must
be specified. If used to override the timer specification in a bitmap file,
@@ -289,7 +289,7 @@
disk addressing option (LILO 21.2) ignores disk geometry.
.sp
In cases where there is no
-kernel paritition information available, such as on loopback devices,
+kernel partition information available, such as on loopback devices,
the 'disk=' specification may include paritition start information;
viz.,
.sp
@@ -308,7 +308,7 @@
entries for the device in the "/dev" directory (with 'mknod'). The
maximum number of partitions must be one of 63 (like an IDE disk), 15
(like SCSI disks -- most common value), or 7 (like one array controller).
-An example specifictaion would be:
+An example specification would be:
.sp
.nf
disk=/dev/userd0
@@ -363,7 +363,7 @@
Selects the user interface which will be seen at boot time. One of the
following three options may be specified: \fBtext\fP, \fBmenu\fP, or
\fBbmp\fP. The traditional LILO interface is `text'; but `menu' is now the
-default, unless the configurtion file contains the `bitmap='
+default, unless the configuration file contains the `bitmap='
specification. The \fItext\fP interface is strictly a command-line
interface as though the console were a dumb terminal. The \fImenu\fP
interface is a text-based screen of the boot choices, with the option to
@@ -382,7 +382,7 @@
passing the initrd to the kernel. The presence of this option merely
indicates that your system does not have the old BIOS limitation.
-This switch (or its abscence) is not passed to the kernel, and does not
+This switch (or its absence) is not passed to the kernel, and does not
in any way affect the
amount of physical memory which it will use. (See the
kernel documentation for the kernel command line parameter
@@ -514,14 +514,14 @@
with LILO version 22.0, the boot record is normally written to the first
sector of the RAID1 partition. On PARALLEL raid sets, no other boot records
are needed. The
-default action is \fIauto\fP, meaning, automatically generate auxilary boot
+default action is \fIauto\fP, meaning, automatically generate auxiliary boot
records as needed on SKEWED raid sets. \fInone\fP means
suppress generation of all auxiliary boot records.
\fImbr-only\fP suppresses generation of a boot record on the raid device,
and forces compatibility with versions of LILO earlier than version 22.0
by writing boot records to all Master Boot Records (MBRs) of all disks which
have partitions in the raid set. \fImbr\fP is like \fImbr-only\fP except the
-boot record on the RAID parition is not suppressed.
+boot record on the RAID partition is not suppressed.
Use of an explicit list of devices, forces writing of auxiliary boot records
only on those devices enumerated, in addition to the boot record on the RAID1
device. Since the version 22 RAID1 codes will never automatically write a boot
@@ -671,7 +671,7 @@
The string must be enclosed within double quotes. Usually, the previous
.B "append="
will specify parameters common to all kernels by appearing in the top,
-or global, section of the configuratin file and
+or global, section of the configuration file and
.B "addappend="
will be used to add local parameter(s) to an individual image.
Addappend= may be used only once per "image=" section.
@@ -798,7 +798,7 @@
The alternate chain loader,
.I os2_d
passes partition and drive information unconditionally, and uses a format
-suitalble for OS/2 and DOS (see
+suitable for OS/2 and DOS (see
.I table=<letter>
below).
.TP
@@ -853,7 +853,7 @@
normal, and activated. Activation sets the boot-flag in the partition
table. The
.I automatic
-keyword may confict with default change rules, so the
+keyword may conflict with default change rules, so the
.I set=
lines above may be redundant.
.TP
@@ -941,7 +941,7 @@
The bitmap graphic (install=bmp) is retained when control is passed to the
loaded kernel image, or other= bootloader; i.e., the screen is not
blanked to alphanumeric mode before starting the kernel. This feature is
-conisdered EXPERIMENTAL, for those users working with startup splash
+considered EXPERIMENTAL, for those users working with startup splash
screens.
.TP
.BI "fallback=" <command-line>
