* A call for boot loader IDs
@ 2003-12-05 16:38 H. Peter Anvin
0 siblings, 0 replies; only message in thread
From: H. Peter Anvin @ 2003-12-05 16:38 UTC (permalink / raw)
So far only a small number of boot loaders have actually officially
registered their IDs, this is the list that I have:
If your boot loader has an assigned id (see table below),
enter 0xTV here, where T is an identifier for the boot loader
and V is a version number. Otherwise, enter 0xFF here.
Assigned boot loader ids:
Please contact <email@example.com> if you need a bootloader ID
I would really appreciate if other boot loaders -- especially GRUB,
which is widely used -- would let me know (a) what they are currently
doing, and (b) whether or not they need an official allocation. It's
probably unwise to not do so, at least for the ones which have a
significant user community.
The purpose of this ID is so we can work around individual boot loader
issues if we should have a need to adjust or change the boot
protocol. Not reporting a unique ID makes this impossible.
<firstname.lastname@example.org> at work, <email@example.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-12-05 16:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-05 16:38 A call for boot loader IDs H. Peter Anvin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).