[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] /proc/sys/kernel/bootloader_type
- From: Coywolf Qi Hunt <coywolf@xxxxxxxxx>
- Date: Fri, 31 Dec 2004 22:24:06 +0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ar/VwqcdnQIucfXnnSgg/wTWOHlSZxmLlAm/dWPSATR08N9imWHB6GAvg73UtMIQSjyOod7tAmt1e/itVa8QetJD5ngBKRJ1qvWyQeXoc+Dzbm5Qoem9QeokHuywn1U4Js229UC94m3uWgjShUP8mKxOBLsIOqG5jVdfcr4EcVA=
- References: <41D34E3A.3090708@zytor.com> <20041231013443.313a3320.akpm@osdl.org> <1104487954.5402.20.camel@laptopd505.fenrus.org>
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.
--
Coywolf Qi Hunt
Homepage http://sosdg.org/~coywolf/
-
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/
Follow-Ups: