On Thu, 21 May 2015 09:19:26 -0400, Rich Freeman wrote: > >> You mean: copy grub.conf to grub.cfg and change its syntax to suit > >> GRUB2? I'm well used to hand editing grub.conf, so it'll be no big > >> change to operate on grub.cfg instead. I can cope with that. > > > > You'd need to run grub2-mkconfig once, to generate a grub.cfg to which > > you can add your entries. > > > > It is just a text file. I think the only challenge is that there > aren't a lot of decent examples floating around because all the docs > tend to say to run grub2-mkconfig. I found this extremely frustrating > when I first migrated to grub2.
Same here, but running grub2-mkconfig generates a better starting point than an empty file. That's your example. > In my case grub2-mkconfig wouldn't > find anything, since it looks at filenames and my kernels/initramfs > files didn't follow any standard naming convention (they were not > installed using make install). These days I do use grub2-mkconfig. > > That said, the canned config files output by grub2-mkconfig are a bit > smarter about auto-setting things like the grub2 root. I wouldn't > bother putting anything in 40_custom though. Just run it once and > edit the file. That's certainly an option if your needs are not going to change. If you need to edit the file from time to time, I'd prefer to just edit the short file tweaked to my needs than the whole thing. It's really a matter of personal choice but one advantage of continuing to use grub2-mkconfig is that if GRUB upstream changes things, your config will keep track. -- Neil Bothwick Save the whales. Collect the whole set.
pgpUznd5yI9jO.pgp
Description: OpenPGP digital signature
