James schreef: > Neil Bothwick <neil <at> digimed.co.uk> writes: > > > >>make menuconfig >>make && make modules_install && make install > > >>is easier and accomplishes the same, and also updates the vmlinuz and >>vmlinuz.old symlinks in /boot, removing the need to alter your grub >>config. > > > > OK, I but often I like to keep the older kernel versions and grup entries > around for a while to test the differences in the various kernels. Won't > this approach overwrite entries in grub or does it just make another > entry? Some of my grub.conf files get pretty ugly...
Neither. Make install does not write to grub.conf-- you have to do that yourself. If you were using LiLO, that would be a different story. However, what Neil is on about (again :-) ), is that a "properly" set up grub.conf would ideally point to vmlinuz for the current kernel, and vmlinuz.old for the previous kernel. If you don't use specific titles that include a kernel version number, but instead generic titles such as "Gentoo_current" (pointing to vmlinuz) and "Gentoo_previous" (pointing to vmlinuz.old), then you will not have to do any editing of grub.conf after installing a new kernel with make install, because the currently running kernel will be symlinked to vmlinuz.old, and the new kernel will be installed and symlinked to vmlinuz. Any older kernels yet will not be symlinked, but can be accessed directly (vmlinuz-2.6.9-gentoo-r8, for example), as their System.map and .config will also be named with the complete version number. This does mean you have to manually remember which kernel is newly installed and which one is "previous", but that's the price you pay. Holly -- gentoo-user@gentoo.org mailing list
