RE: Shutdown during kernel upgrade using aptitude
Well usually upgrading a kernel should *not* be a trivial thing.
In an ideal world, you'd upgrade your kernel only because a given
feature offers a slight performance / security improvement, or such
thing. Prod systems just won't upgrade a kernel for the fun of it.
Given that, if you choose to upgrade your kernel, you should devote all
your attention to it and know exactly what is going on on your system.
On Wed, 2005-01-26 at 18:01 -0500, J F wrote:
> Don't know if it is a bug or not.
> One thing that could easily be improved
> about debian is the warning that "you should not shut down
> the system now" when you upgrade a kernel.
> I got pull away from my computer and forgot
> aptitude was running.
> I would rather not have a warning. It sits there at the
> WORST possible time waiting for the user to do hit carriage return.
> I would rather it get finished setting up everything.
> --- On Wed 01/26, Robert Brockway < firstname.lastname@example.org > wrote:
> From: Robert Brockway [mailto: email@example.com]
> To: firstname.lastname@example.org
> Cc: email@example.com
> Date: Wed, 26 Jan 2005 22:42:33 +0000 (GMT)
> Subject: RE: Shutdown during kernel upgrade using aptitude
> On Wed, 26 Jan 2005, J F wrote:<br><br>> SOLVED:<br>> ls -l /vmlinuz<br>> lrwxrwxrwx 1 root root 23 Jan 7 15:33 /vmlinuz -> boot/vmlinuz-2.6.9-2-k7<br>><br>> Turns out that somehow /vmlinuz was not a link but a file containing a <br>> specific version of vmlinuz. By deleting the file, and putting in a <br>> link aptitude can now update the kernel. Also, "can't find file <br>> /lib/modules/2.6.9-1-k7/modules.dep<br>at boot time" error message is <br>> now gone away.<br><br>That could be a bug.<br><br>lilo should be able to see /vmlinuz as a file (I did this until about <br>1997).<br><br>If you have an old system and have /boot as a seperate filesystem you may <br>be running into an ancient problem where the kernel had to be wholly <br>inside the first 1024 cylinders. A common way to ensure this was to put <br>a small /boot filesystem at the start of the disk and put the kernel in <br>there.<br><br>Rob<br><br>-- <br>Robert Brockway B.Sc.<br>Senior Technical Consultant, OpenTrend S
> olutions Ltd.<br>Phone: 416-669-3073 Email: firstname.lastname@example.org http://www.opentrend.net<br>OpenTrend Solutions: Reliable, secure solutions to real world problems.<br>
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!