Commit 987138f7 authored by Manoj Srivastava's avatar Manoj Srivastava

Typographical error fixes

Closes: #530494, 528955
Signed-off-by: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
parent 3e436174
......@@ -135,7 +135,7 @@ make: *** [all] Error 2
withdrawn. Problems seem to go away when one downgrades to 5.004.
This is also caused by a broken grep, (for example, grep
2.3-1). Upgrading to a fixed grep solves this (2.3-4 is knownn
2.3-1). Upgrading to a fixed grep solves this (2.3-4 is known
to work, at the time of writing this).
m) Some versions of gcc do not interact well with the kernel
......@@ -197,7 +197,7 @@ VFS: Cannot open root device "308" or 03:08
r) When run in a git sourced tree, scripts/setlocalversion
checks to see if the tree is the trunk, if not, it adds
version information to the kernel version. It also checks
to see if there are uncommited changes, if so, it adds the
to see if there are uncommitted changes, if so, it adds the
string "-dirty" to the version. Since we change a couple of
files in ./scripts/, this falls afoul of the make-kpkg
checks, since the version number is now different from what
......@@ -211,8 +211,8 @@ VFS: Cannot open root device "308" or 03:08
t)
There is a problem when GREP_OPTIONS are exported, since it
may impact the results comoing out of grep in scripts that
are tun in shubshells -- and, of course, make-kpkg is one of
may impact the results coming out of grep in scripts that
are tun in subshells -- and, of course, make-kpkg is one of
them.
$ echo $GREP_OPTIONS --colour=always
......
......@@ -72,13 +72,13 @@ Phase TWO: Create a portable kernel image .deb file
Personally, I prefer non initrd images for my personal machines,
since then adding third party modules to the machine has fewer
gotchas. Note that you will have to arrange for the actual
initrd creation to take place by installting a script like
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/yaird
initrd creation to take place by installing a script like
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird
or, alternately,
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the correspondung directories /etc/kernel/post{inst,rm}.d,
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the corresponding directories /etc/kernel/post{inst,rm}.d,
since the kernel-postinst does not arrange for the initramfs
creatorto be called. You can thuse select your own;
creator to be called. You can thus select your own;
initramfs-tools or yaird.
Phase THREE: Install the kernel image on one or more machines
......@@ -155,7 +155,7 @@ Configuration File
The kernel now needs to be configured, that is you have to set the
kernel options and select the drivers which are going to be included,
either as built-in, or as external modules. These setting are saved in
either as builtin, or as external modules. These setting are saved in
a file ./config. The kernel build infrastructure offers a number of
targets, which invoke different configuration front ends.
......@@ -171,8 +171,8 @@ If you do not wish to copy the old copy over, you can create a new one
from scratch using console-based menu configuration command "make
menuconfig" (please look at the kernel documentation for help on
configuring your kernel). Instead of menuconfig one can use config
(text-based line-by-line configuration frontend) or xconfig (graphical
configuration frontend).
(text-based line-by-line configuration front-end) or xconfig (graphical
configuration front-end).
After the configuration process is finished, the new or updated kernel
configuration will be stored in .config file in the top-level
......@@ -282,12 +282,12 @@ shall not have any effect)
Note that you will have to arrange for the actual initrd creation to
take place by installting a script like
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/yaird
take place by installing a script like
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird
or, alternately,
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the correspondung directories /etc/kernel/post{inst,rm}.d, since
the kernel-postinst does not arrange for the initramfs creatorto be
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the corresponding directories /etc/kernel/post{inst,rm}.d, since
the kernel-postinst does not arrange for the initramfs creator to be
called. You can thuse select your own; initramfs-tools or yaird
......@@ -315,7 +315,7 @@ action.
Let me repeat:
Since nothing is created automatically. you need to provide a hook
script for things to happen when you install the kernel imaeg
script for things to happen when you install the kernel image
package. The user provides such scripts. For example, to invoke
mkinitramfs, I did:
--8<---------------cut here---------------start------------->8---
......@@ -333,9 +333,9 @@ action.
/etc/kernel/postrm.d/
--8<---------------cut here---------------end--------------->8---
These scripts above to nothing unless the correspondig
packages are isntalled (initramfs-tools or yaird), so you could
potentially cp both over -- as long as you never install both yaired
These scripts above to nothing unless the corresponding
packages are installed (initramfs-tools or yaird), so you could
potentially cp both over -- as long as you never install both yaird
and initramfs-tools at the same time.
To run grub, I have in /etc/kernel-img.conf:
......@@ -350,7 +350,7 @@ script you want to cp into /etc/kernel -- and you can create your own
scripts.
For example, if you use linux-headers-* packages to compile third
party modules so that you do not havce to keep the sources directory
party modules so that you do not have to keep the sources directory
around, you might be interested in:
--8<---------------cut here---------------start------------->8---
/etc/kernel/header_postinst.d/link
......@@ -744,7 +744,7 @@ kernel image (same version), then the install scripts detect that, and
ask you to move at least the /lib/modules/X.X.XX dir away. If you
continue anyway, the files in /boot shall be overwritten.
Also, if you try to recompile with a changed --revison option or a
Also, if you try to recompile with a changed --revision option or a
different debian revision, you shall have to remove ./debian, and then
recompile.
......
......@@ -23,7 +23,7 @@ use strict;
my $conffile = '/etc/kernel-pkg.conf';
my $prompt = <<"EOP";
You have installed the debian package kernel-package. This package
You have installed the Debian package kernel-package. This package
essentially consists of a Makefile called debian.rules and supporting
scripts and documentation, and also a site over-ride file
$conffile.
......
......@@ -92,13 +92,13 @@ Phase TWO: Create a portable kernel image .deb file
Personally, I prefer non initrd images for my personal machines,
since then adding third party modules to the machine has fewer
gotchas. Note that you will have to arrange for the actual
initrd creation to take place by installting a script like
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/yaird,
initrd creation to take place by installing a script like
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird,
or, alternately,
/usr/share/kerne-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the correspondung directories /etc/kernel/post{inst,rm}.d,
into the corresponding directories /etc/kernel/post{inst,rm}.d,
since the kernel-postinst does not arrange for the initramfs
creatorto be called. You can thuse select your own;
creator to be called. You can thus select your own;
initramfs-tools or yaird.
Phase THREE: Install the kernel image on one or more machines
......@@ -297,13 +297,13 @@ compile again with a different revision, or else the revision flag
shall not have any effect)
Note that you will have to arrange for the actual initrd creation to
take place by installting a script like
take place by installing a script like
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird,
or, alternately,
/usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs
into the correspondung directories /etc/kernel/post{inst,rm}.d, since
the kernel-postinst does not arrange for the initramfs creatorto be
called. You can thuse select your own; initramfs-tools or yaird
into the corresponding directories /etc/kernel/post{inst,rm}.d, since
the kernel-postinst does not arrange for the initramfs creator to be
called. You can thus select your own; initramfs-tools or yaird
NOTE about using initial ram disk images (initrd). Recent kitchen
......@@ -329,7 +329,7 @@ action.
Let me repeat:
Since nothing is created automatically. you need to provide a hook
script for things to happen when you install the kernel imaeg
script for things to happen when you install the kernel image
package. The user provides such scripts. For example, to invoke
mkinitramfs, I did:
--8<---------------cut here---------------start------------->8---
......@@ -348,9 +348,9 @@ action.
--8<---------------cut here---------------end--------------->8---
These scripts above to nothing unless the correspondig
packages are isntalled (initramfs-tools or yaird), so you could
potentially cp both over -- as long as you never install both yaired
These scripts above do nothing unless the corresponding
packages are installed (initramfs-tools or yaird), so you could
potentially cp both over -- as long as you never install both yaird
and initramfs-tools at the same time.
To run grub, I have in /etc/kernel-img.conf:
......@@ -365,7 +365,7 @@ script you want to cp into /etc/kernel -- and you can create your own
scripts.
For example, if you use linux-headers-* packages to compile third
party modules so that you do not havce to keep the sources directory
party modules so that you do not have to keep the sources directory
around, you might be interested in:
--8<---------------cut here---------------start------------->8---
/etc/kernel/header_postinst.d/link
......
......@@ -851,7 +851,7 @@ EOERR3
print STDERR "the extended version, since the version becomes\n";
print STDERR "part of the kernel-image name; and package names\n";
print STDERR "may only contain lowercase alphanumerics.\n";
print STDERR "I have $append_to_version, which shall be dissallowed \n";
print STDERR "I have $append_to_version, which shall be disallowed \n";
print STDERR "by the packaging tools. Aborting.\n";
exit 1;
}
......
......@@ -288,7 +288,7 @@ variable
.B INITRD
to any non empty value. Please note that unless there are hook
scripts in
.I /etc/kenel
.I /etc/kernel
or added into the hook script parameter of
.I /etc/kernel-img.conf.
no initrd will be created (the bundled in example scripts are
......@@ -564,7 +564,7 @@ of the kernel image, and the second argument being the
.I location
of the kernel image itself. Since debconf is in
use before the script is called, this script should issue no
diagnostic messgaes to stdout -- while the postinst does call
diagnostic messages to stdout -- while the postinst does call
.B db_stop
, debconf does not restore stdout, so messages to stdout disappear.
.IP
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment