Hi,
>>"Brian" == Brian C White <[EMAIL PROTECTED]> writes:
>> >> There is indeed a Debian-ized version of the kernel. The package
>> is >> called kernel-image.
>> You could also grab the raw source and use kernel-package package
>> to generate your new image package. This is the recommended method
>> for generating custom kernel images.
Brian> Could you point me to exactly where this is recommended?
Umm, err, I don't think it is in any publically available
document yet. It has been discussed on the developers list, though,
and I'll see what can be done about putting this into the
general documentation.
Brian> In any case, though, I have no desire to follow this path. I
Brian> like building my kernel directly from the main sources. I
Brian> don't want to have to wait for a package to get built or apply
Brian> patches to the debian sources.
This is what kernel-packages are designed for. You get the
main sources on your own (or patch 'em up, if you wish). You get the
kernel-package package, which is kernel version independent, so you
don't have to wait for it, or download a new one per kernel
revision. You get it once. (barring upgrades for bug fixes, changing
specs, etc, but I hope that there ain't gonna be none, at least for a
resonable period). It is a small, << 25K package.
No kernel files are patched. No C code is provided. The
kernel image is produced by a normal make boot/zimage. All the
package does is provide you a debian.rules debian.README (explaining
how to use debian.rules), and debian/* files, which arrange for you to
register and manage the kernel images using dpkg, and to satisfy
dependencies that other debian packages may have for the image.
You still can customize your images at will (I do, believe
me. I have not installed a standard image since 1.2.8, I think, and I
like being bleeding edge [1.99.9 at the moment]).
Brian> But is there a "self-compiled-kernel-image"? At least the new
Brian> "diald" (in Incoming) depends on "kernel-image".
>> The self compiled kernel, if you do it using kernel-package
>> package, will also "Provide" kernel-image.
Brian> See above.
ditto.
Brian> If I recall, some other package used to depend on the image but
Brian> was changed to check the kernel version in the preinst script.
>> This is true about kernel version.
Brian> So... Should there be a restriction against listing the
Brian> kernel-image as a dependancy in another package?
>> No, since if you follow the recommended method of generating
>> kernel images, this will work.
Brian> But neither I nor some others install the Debian kernels. We
Brian> like building our own.
All you have to do is get a 22K package that adds a thin
veneer of information that dpkg needs. The image is not changed, and
you use your own custom config file, and decide whatever you want as
modules. It just makes handling kernel images easier, since you now
can use dpkg. The raison de 'etre of this package is that I was sick
of the mechanical, routine things I had to do every other day
compiling yet another kernel.
manoj
--
Everything is for sale; only the price is negotiable. %%
Manoj Srivastava Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918 A143B Lederle Graduate Research Center,
Fax: (413) 545-1249 University of Massachusetts, Amherst, MA 01003
<[EMAIL PROTECTED]> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>
