lkml.org 
[lkml]   [2005]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] i386 boot loader IDs
From
Date
"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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.038 / U:4.784 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site