On Thu, May 21, 2015 at 8:10 AM, Neil Bothwick <[email protected]> wrote: > On Thu, 21 May 2015 12:44:42 +0100, Peter Humphrey wrote: > >> > If you're just going to hand-edit your config file, I don't see much >> > point in sticking this stuff in /etc/grub.d. Just hand-edit your >> > config file and forget about grub2-mkconfig. >> >> 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. 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. -- Rich
