Hi,
You can always delete the kernel before or after you install the new
kernel... preferrably AFTER.
You could do the update and dump the backup kernel. It's not one that would usually be
used anyways.
You can also upgrade and make the new kernel the backup kernel (the
working one).
Removing the kernel when you have NO other kernel is worst than having a
bad backup. Making it the backup kernel would only be an inconvenience.
To remove the old kernel (once the new one is in)
If you are running lilo..
1. edit lilo.conf first
If you don't know how to edit lilo.conf maybe someone at the meeting can
help. Comment out the selection for the bad kernel and then make sure
default doesn't point to it. Theres a default keyword that points to that
image. How bad is your situation? Are you able to get into the machine?
2. run lilo to reflect the changes
3. remove the old kernel or bad kernel. When you install the new kernel
the old system map becomes system.old and the old kernel becomes
vmlinuz.old
4. remove /lib/modules/2.this.kernel.sucks (um, just how old *is* your
kernel...maybe 1.this.kernel.sucks?)
-marcia
On Mon, 18 Aug 2003, Miles Beck wrote:
> Hello,
>
> I have an old kernel that does not work on my system that I would like to have
> removed. If I came to the tuesday meeting tomorrow would someone be able to fix
> this for me?
>
> I have been putting off updating some packages until this is fixed. One of the
> packages is a new kernel that fixes some security issues. I do not want to do
> this upgrade until the old kernel is gone. Having the non-working kernel become
> the backup kernel would not be a good idea.
>
> ;)
>
>
> -------------------------------------------------
> FastQ Communications
> Providing Innovative Internet Solutions Since 1993
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
(text/plain)