Class conflicts (was: grub and grub_pc)

Thomas Neumann blacky+fai at fluffbunny.de
Wed Jan 26 12:56:07 CET 2011


hiya

>> Hello, may a client belong simultaneously to GRUB and GRUB_PC classes?
>> If not, if a client belongs to GRUB_PC class,
>> the /files/boot/grub/menu.lst/GRUB
>> will not be copied to the new system installed.

> Nope...GRUB and GRUB_PC are seperate bootloaders.

> A server or install client should only belong to one class.

How to tell that someone is doing something stupid? From the software's
point of view, a class combination of "WEBSERVER DBSERVER DHCPSERVER" is
as valid as "DEBIAN UBUNTU X86_32 X86_64".

Is it useful to have some kind of list(s), where one could specify classes
that do not play well together? "pick on of these"

Operating system: Debian vs. Ubuntu vs. SuSE
Architecture: 32 vs. 64 bit
Bootloader: lilo vs. grub vs. grub2
[...]

tschüß
thomas



More information about the linux-fai-devel mailing list