On Wednesday 16 November 2005 22:24, Harry Putnam wrote: > Harry Putnam <[EMAIL PROTECTED]> writes: > > Updating the kernel today, I referenced that piece of the > > documentation and borrowed this command from it: > > > > genkernel --bootloader=grub all > > > > However, not only did it not update grub.conf but grub.conf > > disappeared entirely following the successful build. > > Let me tell this story again briefly... This was quite a knuckleheaded > move on my part. Its been so long since I updated my kernel, I forgot > that I switched to lilo some mnths ago.... So, er I misinfomed the > genkernel tool. > > I'm not sure that should have made any difference in what it did to > grub.conf or not..
It doesn't make any difference trust me. I tried genkernel a few months ago with the --bootloader=grub option and it it removed everything in my grub.conf as well ; the file was 0 bytes afterwards. Lucky for me, I keep backups. I've never really liked Genkernel though and don't use it. Most of the time when I update my kernel it is pretty quick and easy: I turn on the symlink USEflag which makes a new symlink of my new kernel. So, after I emerge any new kernel source I just cd /usr/src/linux then zcat /proc/config.gz >.config which copies the config from my current kernel then run make oldconfig (any new changes will prompt you); then make menuconfig if I want to change anything, otherwise make all install install_modules Then just reboot. I already have grub configured to use either the vmlinuz symlink in /boot which points to my latest kernel image or the fallback vmlinuz.old which is my previous kernel image. The make install copies these files into /boot automaticly. -- Chris Linux 2.6.14-gentoo-r2 i686 AMD Athlon(tm) XP 01:39:55 up 21:54, 8 users, load average: 3.21, 2.61, 2.39 -- [email protected] mailing list
