Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | A call for boot loader IDs | Date | 5 Dec 2003 08:38:13 -0800 |
| |
Hi all,
So far only a small number of boot loaders have actually officially registered their IDs, this is the list that I have:
type_of_loader: 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: 0 LILO 1 Loadlin 2 bootsect-loader 3 SYSLINUX 4 EtherBoot 5 ELILO
Please contact <hpa@zytor.com> if you need a bootloader ID value assigned.
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.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.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 - 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/
| |