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? 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. I do suggest at least giving grub-mkconfig a try though. It does depend on kernels/initramfs/etc using a standardized naming convention. If you use make install to install your kernels you're fine. If you go hand copying things then it won't. The one thing I have noticed is that it doesn't always get ordering right if you go messing around and creating kernels with suffixes on the filenames or +'s on them. You can run grub-mkconfig and if you don't append -o to the command line it just dumps the config file to stdout, so you can see what it would do. But, if you want to always have a vmlinux and vmlinux.old in your /boot and just point grub to the one and then the other and never touch it, that will work perfectly fine. The autogenerated configs have a ton of scripting in them but a minimal one isn't really any more complex than the old grub was. 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. The one issue you're going to have is finding documentation on the config file. There is a TON of docs on running mkconfig, and very little on rolling your own, but it definitely can be done. -- Rich
