Set Up the Master Boot Record

When setting up the Master Boot Record, you need to enter appropriate partition information. In this example, Grub is in the first partition on the first hard drive, which is (hd0,0) in Grub. Change this to whatever partition Grub is in.

After getting the Grub prompt, type:

root (hd0,0)
setup (hd0)

via Set Up the Master Boot Record.

This has been sitting as draft since August 5 and works in setting the MBR on a hard drive and since things like this can be easily forgotten, it has become a reference.  Even Testdisk couldn’t  write the MBR correctly when I tried to transfer a Fedora14 VM onto a real hard drive.  After setting the MBR and getting it to boot the network and graphic interfaces required manual intervention.  I’m not convinced transferring a virtual image to a physical image is much of a time saver.

Note: Not all installations have grub installed by default.  The command to get the grub prompt is /sbin/grub run as root.

Our Planned Approach to Secure Boot

At the implementation layer, we intend to use the shim loader originally developed by Fedora – it’s a smart solution which avoids several nasty legal issues, and simplifies the certification/signing step considerably. This shim loader’s job is to load grub2 and verify it; this version of grub2 in turn will load kernels signed by a SUSE key only. We are currently considering to provide this functionality with SLE11 SP3 on fresh installations with UEFI Secure Boot present.

via Our Planned Approach to Secure Boot | SUSE Blogs.

GRUB 2.00 Boot-Loader Officially Released

The GRUB2 boot-loader features an EHCI driver, an official theme, ports to Itanium and SGI MIPS architectures, better default video mode selection using monitor EDID information, new drivers (EHCI / AHCI / ESCC serial / EFI / Network stack / VBE on Coreboot), new file-system support, improved file-system capabilities, new boot protocols, performance improvements, better internationalization, and improved installation support.

via [Phoronix] GRUB 2.00 Boot-Loader Officially Released.

Ubuntu’s Plans To Implement UEFI SecureBoot: No GRUB2

With the GPLv3-licensed GRUB2 not being an option, Canonical then explored using the GRUB Legacy release with EFI patches on top, but they didn’t want to touch that aging code-base. Canonical has decided to use Intel’s efilinux loader that is more liberally licensed and they’re able to make some modifications to provide a simple menu interface.

via [Phoronix] Ubuntu’s Plans To Implement UEFI SecureBoot: No GRUB2.

Configure the GRUB boot loader

Adding a single user mode option to the GRUB menu

password –md5 $1$U$JK7xFegdxWH6VuppCUSIb.

default 0

title Red Hat Linux (2.4.9-21)

root (hd0,0)

kernel /vmlinuz-2.4.9-21 ro root=/dev/hda6

initrd /initrd-2.4.9-21.img

title Red Hat Linux (2.4.9-21) single user mode


root (hd0,0)

kernel /vmlinuz-2.4.9-21 ro root=/dev/hda6 s

initrd /initrd-2.4.9-21.img

via Configure the GRUB boot loader.