Robert Millan writes: > The problem with that is it can't really solve the problem, only provide a > half-baked solution. If you include pc and gpt, you're misusing space in > a component where it's really critical, and you still don't support all > partitions GRUB might be installed on. For that, you'd have to load _all_ > partition maps, which means even more space.
I understand, and I've been wondering about this. As I do not have much if any knowledge for the sizing constraints of a bootloader, so I cannot appreciate the efforts of reducing space. As a (blonde) user, I would think that you'd want to use *as much* rather than as little space you can. Why not (from a sizing pov, stability could be another issue), after core.img contains all necessary modules, fill up any `remaining' space (if that is how it works) with extra non-essential modules? Little harm in the ability to read more devices, I would say? Greetings, Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
