mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] i386 boot loader IDs
Date: 04 Jan 2005 00:43:22 -0700	[thread overview]
Message-ID: <m1vfadr65h.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <41D31696.8050701@zytor.com>

"H. Peter Anvin" <hpa@zytor.com> writes:

> This patch adds some i386 boot loader IDs that were used but never officially
> recorded as assigned.  This makes them nice and official.
> 
>  	Please contact <hpa@zytor.com> if you need a bootloader ID
>  	value assigned.

I suspect /sbin/kexec could use one.  But I don't have the faintest
what you could do with the information after the kernel came up.

I don't think enhancing the bootloader numeric parameter is the
right way to go.  Currently the value is a single byte with the low
nibble reserved for version number information.  With the
values already assigned we have 7 left.  

If we assign a new value each for the bootloaders I know of that don't
yet have values assigned: pxelinux, isolinux, filo, /sbin/kexec,
redboot the pool of numbers is nearly exhausted.  With the addition of
bootloaders I can't recall or have not been written yet we will
quickly exhaust the pool of numbers.

Even if using this mechanism is needed for supporting existing
bootloaders I suggest it be deprecated in favor of a kernel command
line option.  A command line option would be easier to maintain
being string based.  It would be portable to architectures besides
x86.  And it requires no additional code to implement, as you
can already read /proc/cmdline.

Eric

  reply	other threads:[~2005-01-04  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 20:41 H. Peter Anvin
2005-01-04  7:43 ` Eric W. Biederman [this message]
2005-01-04  7:55   ` H. Peter Anvin
2005-01-04 10:37     ` Eric W. Biederman

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=m1vfadr65h.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome