[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new kernel too big for lilo



On 12/31/05 12:37:12AM +0900, Craig Hagerman wrote:
> Thanks for all the feedback. I tried installing a new kernel the 'debian way':
> 
> % make menuconfig
> % make-kpkg
> 
> followed by:
> 
> % dpkg -i kernel_name.deb
> 
> which did everything automatically. Then I restarted ... to find I had
> no GUI and no internet. I realized that the automatic install had
> renamed my old kernel by appending .old to the name. I was able to add
> THAT to lilo.conf by hand and successfully reboot.
> 

I would have thought that both would be available in lilo after the update.
But I don't use LILO and I don't let make-kpkg touch my bootloader so I
could be wrong.

> I am sure most of you will disagree with me but this is one area where
> I do NOT like doing things the debian way. Compiling and installing a
> kernel isn't something I do everyday but it is something that can mess
> up a system. I don't know what is automagically being done behind the
> scenes and I am very uncomfortable with that. I would much rather
> follow a manual compile-installation instruction so that I can add the
> new kernel to lilo by hand to try it out, knowing the working kernel
> is still safe.

You can still use make-kpkg and have it not touch the symlinks or the
bootloader, they're adjustable via kernel-img.conf.

Jim.



Reply to: