Image of RHCE Red Hat Certified Engineer Linux Study Guide (Exam RH302) (Certification Press)
Image of Advanced Programming in the UNIX Environment, Second Edition (Addison-Wesley Professional Computing Series)
Image of Android Wireless Application Development
Image of Beginning Google Maps API 3

We don’t need no stinkin bootloaders!

I have been saying for a number of years now that bootloaders such as GRUB2, rEFit, Clover and others have no place in modern EFI-based Linux systems and that the only reason to use such a bootloader is if you are on older system where you wish to be able to boot into one of a number of operating systems. The Linux Foundation is now a member of Unified EFI Forum (about time!) and has now got full access to the resources of that forum. As a result, kernel developer Greg Kroah-Hartman has been working on the procedures for how

Boot Linux Without An Initramfs

So you think you always need an initramfs to boot your Linux system. Not true and I will show you how. For example, here is my GRUB2 (/boot/grub2/grub.cfg) configuration file for Fedora 17: menuentry ‘Fedora Linux, no initramfs’ { set root=’hd0,msdos1′ linux /vmlinuz-3.3.4-5.fc17.i686.PAE rootfstype=ext4 root=/dev/sda2 rd.lvm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 } Note there is no line specifying an initramfs! I was not aware that this was possible until I saw it demonstrated by Harald Hoyer. By the way, in case you were wondering, yes I manually edit my GRUB2 configuration file rather than using the numerous crazy GRUB2

Fedora 12 Dracut

Fedora 12 contains a new infrastructure for populating and building an initramfs image called Dracut. This post examines what has changed in the boot process and the contents of the initramfs image.