On Jun 30, 2012 7:13 PM, "Dale" <rdalek1...@gmail.com> wrote: > > Neil Bothwick wrote: > > On Sat, 30 Jun 2012 15:24:17 -0500, Dale wrote: > > > >> I still don't like the deal of having to run something after changing > >> the kernel tho. It seems to lilo-ish to me. > > Then how do you manage with GRUB legacy? If you don't have symlinks to > > the kernels and you don't update the config, how do you boot the new > > kernel? You have to update the config, GRUB2 just has an option to do > > this automatically. > > > > > > It's simple. I open grub.conf and add a entry into it. I do that > manually so I that I know what is changed. I also keep a couple older > entries just in case a kernel gets messed up, has a bug or won't boot > for some reason etc. I don't use symlinks for kernels at all. I been > doing it that way for years and it works very well for me. If something > goes wrong, I know what I did and how to fix it. If I use some script, > I may not know exactly what the script did. > The scripts are there for you to read, and even modify.
> The key thing is, after I change the grub.conf file, I don't have to run > anything else. It just works. Grub2 does tho. That reminds me of how > lilo does it. > You don't have to run anything after you create grub.conf with Grub2. In fact, you can still manually edit the config file without using the config generation scripts. But the generation scripts are, once again, both readable and editable. I've also never once had them create an improper config. I just use it because it's faster, since it works. The only problem I had with Grub2 was the grub2 folder in /boot, as I had previously used it on Ubuntu and was confused (so this was gentoo-specific to me, and I had arrogantly ignored the package output). Really, I don't think it's as different as you think. And I, too, manually cp over my kernels after I build them, but only because it never occurred to me to even USE "make install". The next kernel I build I will be trying it! Alecks Gates, sent from Android on an HTC G2
