On Sat, Oct 31, 2009 at 3:20 PM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On Saturday 31 October 2009 23:26:33 Dale wrote: >> Denis wrote: >> > On Sat, Oct 31, 2009 at 12:52 PM, Harry Putnam <rea...@newsguy.com> wrote: >> >> And in fact does it really matter if its pointing at the newly >> >> installed or actual running kernel, when kernel compiling operations >> >> take place? >> > >> > When I upgrade a kernel, I first change the symlink using eselect to >> > point to the source I'm about to install. Then, after I configure and >> > compile the kernel, I use the "module-rebuild rebuild" to rebuild any >> > kernel modules against the new source. Move the bzImage to /boot, >> > reboot, and that's it. I don't know how genkernel changes any of this >> > - I use manual menuconfig. >> >> I'm about the same. I update the symlink, build the kernel, update >> nvidia-drivers against the new kernel before I forget, copy bzImage to >> /boot and edit grub. I reboot when I get the chance. > > I'm a forgetful old git. In my world it usually goes like this: > > emerge, build, install new kernel > carry on with work > boot into new kernel at some later point > observe xdm doing nothing on-screen > curse and swear mightily > Ctrl-Alt-F1 > login as root > check symlink > module-rebuild rebuild > modprobe -r nvidia && modprobe nvidia > /etc/init.d/xdm restart && logout > > takes about 6 minutes total, 6 minutes that I'll never get back :-) > > -- > alan dot mckinnon at gmail dot com
So I think this thread addresses a question I've had about the kernel installation process over the years. I only copy bzImage to /boot with a rename to whatever this kernel is. I don't do anything with the other files - System.map and something else - which I don't even have on most of my systems anymore. They don't seem to be needed. Are they just things used in the old days but now too outdated or replaced by other stuff? (Like config.gz in the kernel, etc.) Thanks, Mark
