RE: Upgrading to 2.4 kernel in Woody
I've found this handy in the past. Perhaps you're doing it already -
apologies in that case.
I always make a link named "vmlinuz" to the current kernel if the distro
install didn't by default. Then, before my final reboot to a new kernel I
add a link to the old kernel like this:
ln -s <my_old_kernel> vmlinuz.old
In the grub menu.lst I add something like:
title Debian 3.0, Kernel that used to work
root (hd1,0)
kernel /vmlinuz.old root=/dev/<your_hdisk>
... what ever else you need ...
Since modules are kept in separate kernel-version specific directories I
would assume that this should work even across kernel versions (i.e. 2.2 to
2.4); but to be honest and say that I've only done this within with a
recompile of kernel 2.4.18. If I'm off-base here I hope someone will jump
in and correct any misconceptions.
Personally, I hate trying to remember different version names so I always
link with "vmlinuz" and "vmlinuz.x" where ".x" could be old, new or whatever
is salient. If I fat-finger menu.lst it helps to have something simple. I
need all the protection that I can muster.
Cheers,
-rick
-----Original Message-----
From: jennyw [mailto:jennyw@dangerousideas.com]
Sent: Sunday, July 14, 2002 6:40 PM
To: debian-user@lists.debian.org
Subject: Re: Upgrading to 2.4 kernel in Woody
Forgot something (in case someone reads this in the future). After
apt-get'ing the kernel image, I just typed update-grub and it
automagically updated menu.lst with the correct information. I understand
from reading the docs that this doesn't always work, but it probably will
with a simple installation (this is currently a single OS machine).
Jen
On Sun, Jul 14, 2002 at 09:26:22PM -0400, Chris Jenks wrote:
> At 08:56 PM 7/14/02, you wrote:
> >Thanks! Yeah, I'd like to start building kernels from source, but
thought
> >I'd try the upgrade with an image first. I mean, start easy, right?
> >
> >I have a question about the line:
> >
> >initrd /boot/initrd-2.4.18.gz
> >
> >How does /boot/initrd-2.4.18.gz get generated? Is it as simple as typing
> >mkinitrd /lib/modules/<version>?
> >
> >I haven't got that far yet because apt tells me to make sure I have my
> >bootloader configured before I continue with getting the new kernel, so
> >I've aborted before it finishes. I assume it puts stuff in /lib/modules,
> >but I don't know for sure.
> >
> >Thanks again!
> >
> >Jen
>
> It was there after the install was completed. I played around with the
> grub menu a bit before I got it working, and the config I posted is what
> worked. apt-geting the kernel does 90 to 95% of the work for you. The
> problem is, you get what the maintainer uses. The kernel works, but
> there is stuff that you don't need or want, and sometimes the stuff you
> do want is compiled turned off (like apm).
>
> (I also put the list back in to the email thread for archive reasons).
>
>
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: