Re: custom kernel
Thank you Nathan and Morgan for your advice!
regarding the Morgan answer I have another question: I found the rotate scheme
amazing, but what about the modules? does "dpkg -i" creates a new directory in
/lib/modules (perhaps with the new kernel revision label) each time it
rotates the links /vmlinuz and /vmlinuz.old?
Thanks again!
On Thu, Apr 12, 2001 at 03:20:40PM -0600, Morgan Terry wrote:
> Installing the new kernel-image will not do anything to your existing
> kernel. It will, however, make lilo boot the new one. If you want to
> have access to your old kernel (which is always a good idea), all you
> need to do is set up a section for it in your lilo.conf. You can
> probably just copy your current kernel's section, and change the label
> and image lines. For example, here is what I have for one of my boxes:
>
> image=/vmlinuz
> label=linux
> root=/dev/hda1
> read-only
> image=/vmlinuz.old
> label=linux.old
> root=/dev/hda1
> read-only
>
> Assuming you have /vmlinuz linked to your current kernel (which should
> be the case - it should have been set up when you installed), typing
> "linux" at the lilo prompt will boot it. If you want to boot the old
> kernel (/vmlinuz.old should point to it automatically), you can type
> "linux.old" instead.
>
> Every time you install a new kernel-image package, it will automatically
> rotate these links (/vmlinuz will point to the newly installed kernel,
> and /vmlinuz.old will point to the previous kernel), so this will give
> you a nice little safety net.
>
Reply to: