On 2019-01-17, Rich Freeman <ri...@gentoo.org> wrote: > On Thu, Jan 17, 2019 at 6:15 PM Grant Edwards <grant.b.edwa...@gmail.com> > wrote: >> >> Do all the Gentoo package maintainers promise they'll never run >> grub-mkconfig as part of a any package (even grub:2) install, remove, >> or update? > > I doubt you'd get it in writing but I'd be shocked if they ever did. > Gentoo doesn't install a kernel for you, so why would it go messing > with grub?
Good point. :) > You definitely can manually configure grub.conf for grub2, and it > would basically work the same as grub legacy if you did so. The > syntax is slightly different so you'll have to check on that, but it > would basically consist of taking your old config file and just making > a few syntax tweaks. Yep, I've spent plenty of time editing grub2's grub.conf files. > I do suggest at least giving grub-mkconfig a try though. I've used it on plenty of other distros and didn't like it -- maybe it's better on Gentoo... > Basically grub2 is a completely inert package. The stuff in > /usr/bin and so on doesn't do anything unless you explicitly run it. > The bootloader reads its config file and does what it says, just > like the old one. The bootloader won't even be there unless you > explicitly install it, just as with the old grub. OK, that sounds reasonable. I should have had more faith in the Gentoo devs. > The one issue you're going to have is finding documentation on the > config file. It's pretty well documented in the grub2 manual: https://www.gnu.org/software/grub/manual/grub/grub.html#Shell_002dlike-scripting https://www.gnu.org/software/grub/manual/grub/grub.html#Multi_002dboot-manual-config https://www.gnu.org/software/grub/manual/grub/grub.html#Environment https://www.gnu.org/software/grub/manual/grub/grub.html#Commands The thing to keep in mind, is that grub.conf is more of a shell-script than a config file. Amongh other things, you can define shell functions that are attached to menu entries. Then, if execution falls off the bottom of the script, that menu is executed and the selected shell function executes. IIRC, you don't actually _have_ to define a menu at all if you don't want to, but that rather limits your options at boot time... > There is a TON of docs on running mkconfig, and very little on > rolling your own, but it definitely can be done. Not a problem -- I know enough about the config file syntax to do everything I need to do. -- Grant Edwards grant.b.edwards Yow! UH-OH!! I put on at "GREAT HEAD-ON TRAIN gmail.com COLLISIONS of the 50's" by mistake!!!
