[NTLUG:Discuss] Kernel module woes.

[Brian]

On Tue, Jul 23, 2002 at 05:27:49PM -0500, Lance Simmons wrote:
> I find Debian's package management tools in general helpful and well
> thought-out, and make-kpkg particularly so. "make-kpkg kernel_image" and
> "dpkg -i <kernel-image>" (dpkg runs a script that automates updating
> lilo or grub) makes it simpler to try out new kernels. It's still
> important to know how to do all the steps independently, I think, but I
> don't miss doing every step by hand.

What do you do when the kernel fails to boot?  Does dpkg modify lilo so that there
is a label pointing to the original kernel?  And does dpkg overwrite modules for the
current kernel, or are they archived away just in case?  What happens if the kernel
is too big?  Does dpkg automatically attempt to build a compressed version?   

If dpkg does all this, then I respectfully bow to the clever minds that make all
this work.

There's a lot that can go wrong with a kernel install, much more than I would trust
to dpkg (unless convinced otherwise).  

  --Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://ntlug.org/pipermail/discuss/attachments/20020723/0646403a/attachment.bin