Gentoo Archives: gentoo-user

From: Alan McKinnon <alan.mckinnon@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Kernel upgrading and linux symlink
Date: Sat, 31 Oct 2009 22:22:01
Message-Id: 200911010020.57136.alan.mckinnon@gmail.com
In Reply to: Re: [gentoo-user] Kernel upgrading and linux symlink by Dale
1 On Saturday 31 October 2009 23:26:33 Dale wrote:
2 > Denis wrote:
3 > > On Sat, Oct 31, 2009 at 12:52 PM, Harry Putnam <reader@×××××××.com> wrote:
4 > >> And in fact does it really matter if its pointing at the newly
5 > >> installed or actual running kernel, when kernel compiling operations
6 > >> take place?
7 > >
8 > > When I upgrade a kernel, I first change the symlink using eselect to
9 > > point to the source I'm about to install. Then, after I configure and
10 > > compile the kernel, I use the "module-rebuild rebuild" to rebuild any
11 > > kernel modules against the new source. Move the bzImage to /boot,
12 > > reboot, and that's it. I don't know how genkernel changes any of this
13 > > - I use manual menuconfig.
14 >
15 > I'm about the same. I update the symlink, build the kernel, update
16 > nvidia-drivers against the new kernel before I forget, copy bzImage to
17 > /boot and edit grub. I reboot when I get the chance.
18
19 I'm a forgetful old git. In my world it usually goes like this:
20
21 emerge, build, install new kernel
22 carry on with work
23 boot into new kernel at some later point
24 observe xdm doing nothing on-screen
25 curse and swear mightily
26 Ctrl-Alt-F1
27 login as root
28 check symlink
29 module-rebuild rebuild
30 modprobe -r nvidia && modprobe nvidia
31 /etc/init.d/xdm restart && logout
32
33 takes about 6 minutes total, 6 minutes that I'll never get back :-)
34
35 --
36 alan dot mckinnon at gmail dot com

Replies

Subject Author
Re: [gentoo-user] Kernel upgrading and linux symlink Dale <rdalek1967@×××××.com>
Re: [gentoo-user] Kernel upgrading and linux symlink Neil Bothwick <neil@××××××××××.uk>
Re: [gentoo-user] Kernel upgrading and linux symlink Mark Knecht <markknecht@×××××.com>