On Tue, 2010-06-08 at 14:00 +0200, Peter Palfrader wrote:
> On Tue, 08 Jun 2010, Ben Hutchings wrote:
>
> > On Tue, 2010-06-08 at 13:39 +0200, Vincent Danjean wrote:
> > > On 07/06/2010 17:37, Stephen Powell wrote:
> > > > But for a kernel install or reconfigure, it is the responsibility of the
> > > > kernel maintainer scripts to invoke the bootloader. See also, for
> > > > example,
> > > > linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the
> > > > bootloader
> > > > on line 38. This really is an "open and shut case", if only I can the
> > > > kernel
> > > > people to actually look at it! Please look at it!
> > >
> > > If I recall correctly, kernel maintainers have introduced
> > > /etc/kernel/post{inst,rm}.d/ in order to avoid to hardcode each possible
> > > bootloader in their script.
> > > Can't lilo provide a script here ?
> >
> > It could, but that should be redundant in squeeze since update-initramfs
> > already runs lilo.
>
> Not every kernel package needs an initrd.But those that don't, invoke lilo (or other bootloader) directly. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
