[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] /proc/sys/kernel/bootloader_type
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Date: Fri, 31 Dec 2004 15:36:47 +0100
- References: <41D34E3A.3090708@zytor.com> <20041231013443.313a3320.akpm@osdl.org> <1104487954.5402.20.camel@laptopd505.fenrus.org> <2cd57c90041231062438c2cab9@mail.gmail.com>
On Fri, 2004-12-31 at 22:24 +0800, Coywolf Qi Hunt wrote:
> On Fri, 31 Dec 2004 11:12:34 +0100, Arjan van de Ven
> <arjan@xxxxxxxxxxxxx> wrote:
> > On Fri, 2004-12-31 at 01:34 -0800, Andrew Morton wrote:
> > > "H. Peter Anvin" <hpa@xxxxxxxxx> wrote:
> > > >
> > > > This patch exports to userspace the boot loader ID which has been
> > > > exported by (b)zImage boot loaders since boot protocol version 2.
> > >
> > > Why does userspace need to know this?
> >
> > so that update tools that update kernels from vendors know which
> > bootloader file they need to update; eg right now those tools do all
> > kinds of hairy heuristics to find out if it's grub or lilo or .. that
> > installed the kernel. Those heuristics are fragile in the presence of
> > more than one bootloader (which isn't that uncommon in OS upgrade
> > situations).
> >
>
> This boot loader ID doesn't help much for system upgrade. The running
> kernel may boot from removable drive.
but then it says syslinux or so...
means that the lilo-or-grub question still needs the heuristics, it's
just that in the normal case, the bootloader type can help make the
heuristics reliable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
References: