From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, SYSLINUX@zytor.com
Subject: Re: [PATCH] /proc/sys/kernel/bootloader_type
Date: Fri, 31 Dec 2004 22:24:06 +0800 [thread overview]
Message-ID: <2cd57c90041231062438c2cab9@mail.gmail.com> (raw)
In-Reply-To: <1104487954.5402.20.camel@laptopd505.fenrus.org>
On Fri, 31 Dec 2004 11:12:34 +0100, Arjan van de Ven
<arjan@infradead.org> wrote:
> On Fri, 2004-12-31 at 01:34 -0800, Andrew Morton wrote:
> > "H. Peter Anvin" <hpa@zytor.com> 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/
next prev parent reply other threads:[~2004-12-31 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:39 [PATCH] /proc/sys/kernel/bootloader_type H. Peter Anvin
2004-12-31 9:34 ` Andrew Morton
2004-12-31 10:12 ` Arjan van de Ven
2004-12-31 14:24 ` Coywolf Qi Hunt [this message]
2004-12-31 14:36 ` Arjan van de Ven
2004-12-31 20:10 ` H. Peter Anvin
2005-01-01 20:22 ` Kay Sievers
2005-01-02 8:56 ` Lethalman
-- strict thread matches above, loose matches on Subject: below --
2005-01-01 9:39 Lethalman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd57c90041231062438c2cab9@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=SYSLINUX@zytor.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.