Commit 2a6e19e1 authored by Manoj Srivastava's avatar Manoj Srivastava

cscvs to tla changeset 181

Author: srivasta
Date: 1998/07/17 04:24:00
Spelling fixes from Nathan E Norman <finn@midco.net>

git-archimport-id: srivasta@debian.org--2003-primary/kernel-package--devel--0.1--patch-180
parent cee8b2e6
......@@ -10,14 +10,14 @@
non-i386 architectures.
I understand that the patches are such that the kernel header
files may change (reuiring an architectire specific kernel-headers
files may change (requiring an architecture specific kernel-headers
package), and also kernel-doc, and of course kernel-image
packages. However, one would like to avoid uploading the huge base
kernel sources for every architecture, just for efficiency if nothing
else.
I guess this proposal is that there is one common, large
source package (maintained, as now, by the i386 maitainer), and every
source package (maintained, as now, by the i386 maintainer), and every
other architecture maintainer just release kernel-patch packages.
make-kpkg from kernel-package has been modified to be aware of
......@@ -27,7 +27,7 @@
support also present).
A nice side effect of this proposal is that we can handle
arbitary patches as well, which could allow the authors of kernel
arbitrary patches as well, which could allow the authors of kernel
patches to say, for example, I have a nice new driver for device XXX,
to use in your kernel, get kernel-patch-yyy.deb, and rebuild your
kernel to use it.
......
$Id: Problems,v 1.6 1998/03/05 22:37:58 srivasta Exp $
$Id: Problems,v 1.7 1998/07/17 04:26:14 srivasta Exp $
This is an (incomplete) list of problems that people have encountered
in the past while using kernel-package. Please remember to configure
......@@ -16,7 +16,7 @@
so.
b) warning, 'debian/tmp-image/DEBIAN/control' contains user-defined field
'Installed-Size'warning,
'Installed-Size' warning,
dpkg-deb: unable to create '..': is a directory
The problem is actually that the version of dpkg being used is
......@@ -85,7 +85,7 @@
really confirm this works for anything except en_US. This is true as of
dpkg/dpkg-dev 1.4.0.19. The error actually reported seems to be
either that debian/substvars file can not be found, or that the
changelog file is empty (eben when the file is not empty).
changelog file is empty (even when the file is not empty).
The work around seems to be to set the LC_ALL to en_US while compiling
the kernel. This should be fixed soon.
......@@ -102,7 +102,7 @@
rm `which encaps`
j) build fails with a bizzarre error talking about /bin/ls and tab
j) build fails with a bizarre error talking about /bin/ls and tab
sizes = Text:
make[3]: Leaving directory `/usr/src/kernel-source-2.0.32/arch/i386/math-emu'
make[2]: Leaving directory `/usr/src/kernel-source-2.0.32/arch/i386/math-emu'
......@@ -120,4 +120,4 @@ make: *** [all] Error 2
make-kpkg --zimage <other options> kernel_image
This is truly a weird error message for machines that need
zImage rahter than the default bzImage
zImage rather than the default bzImage
This diff is collapsed.
......@@ -14,7 +14,7 @@
Firstly, the modules from different flavours have to be
installed in separate directories, the modutils have to be made aware
of this alternative dorectory, and also, the kernel (and klogd)
of this alternative directory, and also, the kernel (and klogd)
should be able to load the right set of symbols from a System.map
file (which are different enough in different flavours that klogd
refuses to load the wrong one).
......
$Id: README,v 1.17 1998/05/11 06:54:38 srivasta Exp $
$Id: README,v 1.18 1998/07/17 04:25:49 srivasta Exp $
This is the Debian GNU/Linux prepackaged version of the Linux kernel.
Linux was written by Linus Torvalds <Linus.Torvalds@cs.Helsinki.FI> and
......@@ -49,7 +49,7 @@ base: gzip, shellutils, and grep.
Some of these packages are marked essential, and hence are going to be
present on your machine already. Others you have to check and install.
Of course, pretty gui front ends to kernel configuration require more
Of course, pretty GUI front ends to kernel configuration require more
packages, but they are not strictly essential (though quite nice really).
Oh, and of course, make-kpkg is part of kernel-package, usually found
......@@ -119,13 +119,13 @@ to dpkg if you actually do want to downgrade later).
The reason for telling kernel-package that the package has a version
"custom-x.y.whatever.you-want.to+add.more-just.do.not+use.an=underscore"
is that to dpkg that is always a higher version number than any version
number starting with a numeral ( eg. "a" > "2" like "b" > "a". ) This way,
number starting with a numeral ( e.g. "a" > "2" like "b" > "a". ) This way,
dselect will not try to upgrade your "roll-it-yourself" kernel-image when
the a new build of the distribution default kernel appears in the archive.
Unfortunately, this fails if the upstream maintainer uses epochs to
correct a version misnumbering;-(. The good news is that you can add
correct a version misnumbering ;-(. The good news is that you can add
your own epoch to your customized image, ugly though that may
be. (--revision 1:custom.Y; the kernel image file shall remain
kernel-image-X.X.XX-custom.Y.deb, but dpkg shall know that it should
......@@ -140,7 +140,7 @@ So, try using an epoch for your custom packages:
make-kpkg --rootcmd fakeroot --revision=3:custom-1.0 kernel_image
And the next time when you build a kernel, because you just bought a new
soundcard or you discovered that you suddenly want masquerading in your
sound card or you discovered that you suddenly want masquerading in your
kernel enabled, you'll type:
make-kpkg --rootcmd fakeroot --revision=3:custom-2 kernel_image
......@@ -151,7 +151,7 @@ install the package (as root):
This will install the kernel, the modules, the map file and do some other
administrativia and finally it will ask you if you want to make a
bootfloppy and if you want to run lilo now.
boot floppy and if you want to run lilo now.
Now, there is a caveat: If you already have kernel 2.0.29 installed,
and you have a freshly created custom 2.0.29 kernel, just installing
......@@ -203,21 +203,21 @@ image_in_boot: Set to True if you want the kernel image symlink (vmlinuz)
kimage: The kernel image type (i.e. zImage or bzImage). Can be
set from the environment variable IMAGE_TYPE. Defaults
to bzImage.
no_symlink Mutualy exclusive to reverse_symlink. Can be used with
no_symlink Mutually exclusive to reverse_symlink. Can be used with
image_in_boot. The image is placed in vmlinuz (instead
of /boot/vmlinuz-X.X.XX). The old vmlinuz is moved to
vmlinuz.old unconditionally. (Normally, that is only
done if the version of the new image differes from the
done if the version of the new image differs from the
old one). This restricts you to two images, unless you
take additional action and save copies of older
images. This is for people who have boot on a system
that does not use symlinks (and say, they use loadlin)
This is a Hack.
reverse_symlink Mutualy exclusive to no_symlink. Can be used with
reverse_symlink Mutually exclusive to no_symlink. Can be used with
image_in_boot. Just like no_symlink, except that the
/boot/vmlinuz-X.XX is sym linked to the real new
/boot/vmlinuz-X.XX is symlinked to the real new
image, vmlinuz. This too restricts you to just two
images unless futher action is taken. The older
images unless further action is taken. The older
symlinks are left dangling. This is for people with
boot on umsdos, and who can't see the link in dos, but
do want to know the iage version when in Linux.
......@@ -241,11 +241,11 @@ do_clean Set to anything but YES, this shall forego the make
clean done in the kernel source tree after building
the kernel image package. The environment variable
CLEAN_SOURCE over-rides this.
make_libc_headers This is meant to be used by the libc6 maintianer,
make_libc_headers This is meant to be used by the libc6 maintainer,
when he compiles libc6, to also package up the
corresponding headers. DO NOT SET THIS as a
mismatch between the headers you package and libc6
may well create a subtle instablity in all code
may well create a subtle instability in all code
compiled on your machine. You have been warned. The
environment variable MAKE_LIBC_HEADERS over-rides
this.
......@@ -315,8 +315,8 @@ fast) can use image = /boot/vmlinuz-X.X.XX.
So that loadlin people don't feel left out, all this talk about LILO
does not mean to ignore loadlin, you can use the generated
kernel-image just as easily (simply ignore the fol-de-rol with sym
links in /). for instance, you could:
kernel-image just as easily (simply ignore the fol-de-rol with symlinks
in /). for instance, you could:
[1]# dpkg -BRGiE kernel-image-X.X.XX, #(need to be root)
and then
......
......@@ -38,11 +38,11 @@ kernel-source-0.33 (1.01) unstable; urgency=low
etc. kernels for Debian/m68k, and may well be required for the alpha,
from what I hear. Unlike the FLAVOURS variable, which affects
everything it can lay its grubby hands on (kernel image, headers,
source, doc package versiosn, and where the modules are looked for
unde /lib/modules), this only affects the naming of the kernel-image
source, doc package versions, and where the modules are looked for
under /lib/modules), this only affects the naming of the kernel-image
as the source and doc packages are architecture independent and the
kernel-headers do not vary from one sub-architecture to the
next. These changes are coutesy of James Troup <J.J.Troup@scm.brad.ac.uk>
next. These changes are courtesy of James Troup <J.J.Troup@scm.brad.ac.uk>
-- Manoj Srivastava <srivasta@debian.org> Mon, 16 Feb 1998 16:47:08 -0600
......@@ -61,7 +61,7 @@ kernel-source-0.31 (1.01) unstable; urgency=low
* Added ARCH to make called, this allows for cross compiling kernels
(added on a request by James Troup <J.J.Troup@scm.brad.ac.uk>)
* Make kernel-headers arch: any, so we can indeed have different headers
for diferent architectures.
for different architectures.
* m68k can now handle vmlinuz, so reverse that behaviour in the rules
file. AFAIK m68k still uses zImage.
* Improvements to /usr/doc/kernel-patch/MultiArch.gz, based on
......@@ -110,7 +110,7 @@ kernel-source-0.27 (1.01) unstable; urgency=low
fixes: Bug#16968
* ignore obsolete fdformat in favour of superformat.
* Changed the kernel rules file not break on the sound modules of
2.1.70+ kernels (I think it is a bug in the kernel Makfile, but this
2.1.70+ kernels (I think it is a bug in the kernel Makefile, but this
fix make make-kpkg handle the problem and be more robust).
* Modified image.postinst to also cater to people on whose architecture
the image is not called vmlinuz but something else (like vmlinux, for
......@@ -154,7 +154,7 @@ kernel-source-0.24 (1.01) unstable; urgency=low
kernel-source-0.23 (1.-0) unstable; urgency=low
* Added README.headers to the kernel-source package as well, since the
information _is_ relevant to compiling kernels. Since kernel soiurce
information _is_ relevant to compiling kernels. Since kernel source
packages have higher visibility than kernel header packages, this may
help avoid some FAQs from being asked.
* Changed image postinst not to use the obsolete -d option to
......@@ -173,9 +173,9 @@ kernel-source-0.22 (1.01) unstable; urgency=low
in the map files (including top, ps, and klogd) also will look at
/boot/System.map-<version>, we just need to ensure that that file is
present, and no longer require the symbolic link.
Actually, having the sumbolic link in / is technically detrimental
Actually, having the symbolic link in / is technically detrimental
(apart from cluttering up /); many programs, though looking in /boot,
stll allow /Sytem.map to override. If you use LILO to choose between
still allow /System.map to override. If you use LILO to choose between
multiple kernels, then the /System.map symbolic link only applies to
one such kernel, for all other choices the symbols loaded will be
wrong. Not having the symbolic links at all prevents this.
......@@ -189,7 +189,7 @@ kernel-source-0.21 (1.01) unstable; urgency=low
* Fixed handling of modules.dep in the image.postinst. We do not attempt
to recreate a modules.dep, since the man page admits the file so
created may be incorrect. We warn the installer that there maybe
problems loading modules into the kernel intil reboot iff the version
problems loading modules into the kernel until reboot iff the version
being installed is the same as the version currently running.
-- Manoj Srivastava <srivasta@debian.org> Tue, 16 Sep 1997 15:07:02 -0500
......@@ -280,12 +280,12 @@ kernel-source-0.13 (1.01) unstable; urgency=low
* Really add in all the changes sent in by Herbert Xu. The changes are:
* Changed to source package name back to kernel-source-=V again.
* Changed the install's to be without -o root -g root since it is no
longer useful as the chown's are done before the packages are built. It
* Changed the installs to be without -o root -g root since it is no
longer useful as the chowns are done before the packages are built. It
also means that if it is used in targets like stamp-configure which may
be run by anyone it won't not generate an error.
* Made rules file generate the control file.
* Fixed some typos in chowns commands while generating the header
* Fixed some typos in chown commands while generating the header
packages.
-- Manoj Srivastava <srivasta@debian.org> Mon, 21 Apr 1997 15:12:19 -0500
......@@ -366,7 +366,7 @@ kernel-source-0.5 (1.01) unstable; urgency=low
kernel-source-0.4 (1.01) unstable; urgency=low
* kernel-source-X.XX now recommends bin86, which fixes Bug#4443
* Added short, succint (and potentially dangerous) instructions on
* Added short, succinct (and potentially dangerous) instructions on
compiling kernels at the top of the README file. This fixes Bug#4445.
-- Manoj Srivastava <srivasta@debian.org> Wed, 6 Nov 1996 23:59:47 -0600
......@@ -390,7 +390,7 @@ kernel-source-0.2 (1.01) unstable; urgency=low
* Also enabled kernel-{source,image,headers} targets in kernel.rules
* Changed make-kpkg to also accept the new targets.
* Fixed typo in man page.
* The man page says it is an adminstrators man page rather than a
* The man page says it is an administrators man page rather than a
programmers man page.
* Recommended libc-dev for kernel-source and kernel-package
* source suggests ncurses3.0-dev, tk40-dev and the description explains
......@@ -409,7 +409,7 @@ kernel-source-0.2 (1.01) unstable; urgency=low
directory /usr/src/modules/ (whether these files are produced is at
the discretion of the maintainer of that modules package.
* Make configure depend on stamp-configure which in turn depends on
.config Hopefully, this will remake the image atrget if one changes
.config Hopefully, this will remake the image target if one changes
the config file Hopefully, this will not cause the image target to
build needlessly.
......@@ -424,7 +424,7 @@ kernel-source-0.1 (1.01) unstable; urgency=low
* Fixed the targets expected by make-kpkg (kernel_image rather than
kernel-image, etc).
* In image.postinst, made arguments to system be a single argument if
the arguments contain shell metacharacters, (this way perl passes
the arguments contain shell meta-characters, (this way perl passes
them to sh -c).
* Made make-kpkg accept non floats as revision numbers, to facilitate
local names.
......
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