On ���, 2001-11-20 at 12:08, Chmouel Boudjnah wrote:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
> > Chmouel, are you listening? :-)
>
> I was in vacation and didn't get the messages,
For this reason I repost it.
i don't understand the
> point in the forward here..
>
It is a bug either in installkernel or RPM packaging. installkernel -R
is called in kernel posuninstall script; at this moment
/sbin/kernel-`uname -r` is already deleted. /usr/share/loader/lilo calls
do_check() that checks existence of /boot/kernel-... and exits if not
found.
IMHO even if no kernel image is found it still makes sense to remove
lilo entry. So I tend to believe it is a bug in installkernel.
-andrej
> >
> > >
> > > Hi,
> > > Am Freitag, 2. November 2001, 22:53:39 Uhr MET, schrieb Borsenkow
> > Andrej:
> > > > Attn Chmouel ...
> > > > {pts/1}% sudo rpm -e kernel-2.4.10-3mdk kernel-2.4.12-3mdk
> > > > kernel-2.4.12-5mdk
> > > > look like i cannot find the specified kernel
> > /boot/vmlinuz-2.4.12-5mdk
> > > > look like i cannot find the specified kernel
> > /boot/vmlinuz-2.4.12-3mdk
> > > > no wonder, because installkernel -R is called in postuninstall
> > script,
> > > > which means that the following function always fails
> > (vmlinuz-$version
> > > > is already removed):
> > >
> > > > I think, that when we are requested to remove lilo entry we can
> > safely
> > > > ignore the fact that kernel it points to does not (already) exist?
> > > I've already posted this without getting a reply. The easy solution
> > would
> > > be
> > > to call installkernel -R in %preun.
> > >
> > > CU
>
