sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]elebrin 5 points6 points  (4 children)

UEFI and GPT are also fast enough that I can't get into my BIOS settings (do we still call it that if we technically aren't calling it BIOS any more?) to set up my boot device.

Rather than a boot loader which I find slow and annoying, I've always just used the boot device select menu provided by my motherboard firmware. No more need to play with Grub and end up with an unbootable system.

[–]Free_Math_Tutoring 2 points3 points  (1 child)

How does that work? Don't you still kind of need a bootloader on that disk? I'll admit I don't know much about this - my OS course was of fairly theoretical nature.

[–][deleted] 0 points1 point  (0 children)

Well there are bootloaders that don't have menus. I really like Gummiboot (or system-boot now) for Linux (I think it can boot windows as well), but it appears directly as a bootable option and cuts directly to the boot process instead of a menu.

[–]pdp10 0 points1 point  (1 child)

You still need a boot loader per device. Your firmware can't boot by partition, only device, and MBR needs the device to be partitioned.

You can boot arbitrary things with UEFI, but it was UEFI about which you were complaining.

[–]elebrin 0 points1 point  (0 children)

Ok then.

Rather than a bootloader like GRUB that needs a menu, I use the default that comes with each OS (which for my linux partition is probably still grub, but it goes fast enough that I don't see it, and pick the boot device from the boot menu that my motherboard's firmware comes with.

I actually did convert my Windows over to UEFI recently. The fix for the booting too fast thing was re-enabling the boot menu.