--- Begin Message ---
Package: kernel-package
Version: 12.014
Severity: minor
Tags: patch
Attached is a patch to fix some typos in kernel-package. Hopefully it can be of
use.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kernel-package depends on:
ii binutils 2.19.1-1 The GNU assembler, linker and bina
ii build-essential 11.4 Informational list of build-essent
ii debianutils 3.1.3 Miscellaneous utilities specific t
ii file 5.03-1 Determines file type using "magic"
ii gettext 0.17-6 GNU Internationalization utilities
ii make 3.81-5 The GNU version of the "make" util
ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo
ii po-debconf 1.0.16 tool for managing templates file t
ii util-linux 2.13.1.1-1 Miscellaneous system utilities
kernel-package recommends no packages.
Versions of packages kernel-package suggests:
ii bzip2 1.0.5-1 high-quality block-sorting file co
ii docbook-utils 0.6.14-1.1 Convert Docbook files to other for
ii e2fsprogs 1.41.5-1 ext2/ext3/ext4 file system utiliti
ii initramfs-tools [linux-in 0.93.2 tools for generating an initramfs
pn libdb3-dev <none> (no description available)
ii libncurses5-dev [libncurs 5.7+20090510-1 developer's libraries and docs for
ii linux-source-2.6.29 [linu 2.6.29-4 Linux kernel source for version 2.
pn xmlto <none> (no description available)
-- no debconf information
diff -Naur kernel-package-12.014/kernel/docs/README kernel-package-12.015/kernel/docs/README
--- kernel-package-12.014/kernel/docs/README 2009-05-02 00:37:07.000000000 +0300
+++ kernel-package-12.015/kernel/docs/README 2009-05-16 20:00:28.000000000 +0300
@@ -92,13 +92,13 @@
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 @@
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 @@
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 @@
--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 @@
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
diff -Naur kernel-package-12.014/kernel-packageconfig kernel-package-12.015/kernel-packageconfig
--- kernel-package-12.014/kernel-packageconfig 2009-02-17 10:32:17.000000000 +0200
+++ kernel-package-12.015/kernel-packageconfig 2009-05-16 19:56:15.000000000 +0300
@@ -23,7 +23,7 @@
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.
diff -Naur kernel-package-12.014/make-kpkg kernel-package-12.015/make-kpkg
--- kernel-package-12.014/make-kpkg 2009-04-13 09:18:41.000000000 +0300
+++ kernel-package-12.015/make-kpkg 2009-05-16 19:55:03.000000000 +0300
@@ -851,7 +851,7 @@
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;
}
diff -Naur kernel-package-12.014/make-kpkg.8 kernel-package-12.015/make-kpkg.8
--- kernel-package-12.014/make-kpkg.8 2009-05-16 19:35:32.000000000 +0300
+++ kernel-package-12.015/make-kpkg.8 2009-05-16 19:52:20.000000000 +0300
@@ -564,7 +564,7 @@
.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
diff -Naur kernel-package-12.014/Problems kernel-package-12.015/Problems
--- kernel-package-12.014/Problems 2009-02-17 10:33:46.000000000 +0200
+++ kernel-package-12.015/Problems 2009-05-16 19:52:38.000000000 +0300
@@ -135,7 +135,7 @@
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 @@
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 @@
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
diff -Naur kernel-package-12.014/README kernel-package-12.015/README
--- kernel-package-12.014/README 2009-05-02 00:37:36.000000000 +0300
+++ kernel-package-12.015/README 2009-05-16 19:52:46.000000000 +0300
@@ -72,13 +72,13 @@
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 @@
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 @@
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 @@
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 @@
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 @@
/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 @@
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 @@
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.
--- End Message ---
