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 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. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
