Re: kernel upgrade message
well thanks. That makes things clear. Btw, I had to re-install my system around end of march 2006. And yes it was installed with grub. So, I guess that takes care of the rerun issue? There is a "savedefault" option that can be added to the grub config file (/boot/grub/menu.lst) after describing a boot parition. Does this have any relevance to the point at hand? The reason why I bring this out is becasue, couple of weeks back after a regular apt-get upgrade/dist-upgrade I had to reboot the system, and grub was complaining that kernel file could not be found. It would not boot the system at all. With trial and error I removed the 'savedefault' line from the menu.lst file and it booted perfectly fine. Whats the opinion?? --kruton --- Christopher Nelson <[EMAIL PROTECTED]> wrote: > On Thu, May 04, 2006 at 09:36:44PM -0400, > [EMAIL PROTECTED] wrote: > > On Thu, May 04, 2006 at 06:32:42PM -0700, > Christopher Nelson wrote: > > > On Thu, May 04, 2006 at 03:47:28PM -0700, kruton > wrote: > > > > Debian Unstable, running 2.6.16-1-486 on i386 > > > > platform. > > > > > > > > These days I get the following message from > Debian > > > > Configuration when I 'apt-get upgrade'.. Any > idea why > > > > its trying to install the same kernel image... > > > > > > > > > It's updating the kernel image. Often due to > security/usability fixes. > > > It's not trying to do anything nasty, it's > fairly standard, especially > > > on unstable. You will, however, probably want > to reboot soon as the > > > linux-image- packages are built with a lot > of things as > > > modules, and you may not be able to load modules > without rebooting. > > > > But if you use lilo, you had better make sure it > gets rerun before you > > reboot, else the system will try to boot from > where the old kernel was, > > and is no longer. > > > > I don't know what you have to do if you use grub. > > If you installed the system with grub it puts in > post-install hooks to > run update-grub. (at least the etch installers > post-february 2006 do, I > don't know about earlier) > > I'm not sure how to put those hooks in if you didn't > install with grub. > At any rate, I think all it does is rub > 'update-grub', so if nothing > happens automatically that should do it. > > Also, I think grub knows about filesystems and looks > for the kernel that > way, so if the name of the kernel hasn't changed > even that may be > unnecessary. > > -- > Christopher Nelson -- [EMAIL PROTECTED] > --- > Generated by Signify v1.14. For this and more, > visit http://www.debian.org/ > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade message
On Thu, May 04, 2006 at 09:36:44PM -0400, [EMAIL PROTECTED] wrote: > On Thu, May 04, 2006 at 06:32:42PM -0700, Christopher Nelson wrote: > > On Thu, May 04, 2006 at 03:47:28PM -0700, kruton wrote: > > > Debian Unstable, running 2.6.16-1-486 on i386 > > > platform. > > > > > > These days I get the following message from Debian > > > Configuration when I 'apt-get upgrade'.. Any idea why > > > its trying to install the same kernel image... > > > > > > It's updating the kernel image. Often due to security/usability fixes. > > It's not trying to do anything nasty, it's fairly standard, especially > > on unstable. You will, however, probably want to reboot soon as the > > linux-image- packages are built with a lot of things as > > modules, and you may not be able to load modules without rebooting. > > But if you use lilo, you had better make sure it gets rerun before you > reboot, else the system will try to boot from where the old kernel was, > and is no longer. > > I don't know what you have to do if you use grub. If you installed the system with grub it puts in post-install hooks to run update-grub. (at least the etch installers post-february 2006 do, I don't know about earlier) I'm not sure how to put those hooks in if you didn't install with grub. At any rate, I think all it does is rub 'update-grub', so if nothing happens automatically that should do it. Also, I think grub knows about filesystems and looks for the kernel that way, so if the name of the kernel hasn't changed even that may be unnecessary. -- Christopher Nelson -- [EMAIL PROTECTED] --- Generated by Signify v1.14. For this and more, visit http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade message
On Thu, May 04, 2006 at 06:32:42PM -0700, Christopher Nelson wrote: > On Thu, May 04, 2006 at 03:47:28PM -0700, kruton wrote: > > Debian Unstable, running 2.6.16-1-486 on i386 > > platform. > > > > These days I get the following message from Debian > > Configuration when I 'apt-get upgrade'.. Any idea why > > its trying to install the same kernel image... > > > It's updating the kernel image. Often due to security/usability fixes. > It's not trying to do anything nasty, it's fairly standard, especially > on unstable. You will, however, probably want to reboot soon as the > linux-image- packages are built with a lot of things as > modules, and you may not be able to load modules without rebooting. But if you use lilo, you had better make sure it gets rerun before you reboot, else the system will try to boot from where the old kernel was, and is no longer. I don't know what you have to do if you use grub. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade message
On Thu, May 04, 2006 at 03:47:28PM -0700, kruton wrote: > Debian Unstable, running 2.6.16-1-486 on i386 > platform. > > These days I get the following message from Debian > Configuration when I 'apt-get upgrade'.. Any idea why > its trying to install the same kernel image... It's updating the kernel image. Often due to security/usability fixes. It's not trying to do anything nasty, it's fairly standard, especially on unstable. You will, however, probably want to reboot soon as the linux-image- packages are built with a lot of things as modules, and you may not be able to load modules without rebooting. -- Christopher Nelson -- [EMAIL PROTECTED] --- Scrubbing floors and emptying bedpans has as much dignity as the Presidency. -- Richard Nixon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
