Mike Gilbert posted on Thu, 02 May 2013 14:13:30 -0400 as excerpted: > On Thu, May 2, 2013 at 2:05 PM, William Hubbs <willi...@gentoo.org> > wrote: >> On Thu, May 02, 2013 at 04:26:06PM +1200, Kent Fredric wrote: >>> bootloader configuration under grub1 for instance, was quite >>> straight-forward. Now with grub-2, its quite convoluted, for me at >>> least. >> >> I haven't looked at grub2 yet, but I can't imagine it being convoluted >> based on the documentation I have read. >> >> > If you manually write your own configuration for GRUB2, it is no more > convoluted than for GRUB Legacy.
FWIW, this is the key to getting along with grub2. Its automated configuration might arguably make simple things simple, but it makes the (somewhat) complex /horribly/ complex and /terribly/ convoluted, to the point it's nearly impossible. So for those doing anything beyond the basics, just dumping the automated config is from my experience the easiest way to go. FWIW, here I even install-masked the automated config install app (grub2-mkconfig IIRC) along with some of the then useless boilerplate config it installs for it, so there's /no/ /possibility/ of it getting run accidentally, overwriting my custom manual config. FWIW, reminds me a lot of iptables, where there's all these tools that promise to "simplify" things, but I found I was only more mixed up, until I took the time to learn iptables itself, and write in its language myself, thus eliminating all the convoluted middleware that attempted to simplify the simple but ended up horribly convoluting anything beyond the already simple. The automated grub2 stuff is IMO similar middleware that only makes anything beyond the basics harder than it should be, without simplifying the simple (at least to a gentooer) much at all. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
