From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel upgrading and linux symlink
Date: Sun, 1 Nov 2009 00:20:57 +0200 [thread overview]
Message-ID: <200911010020.57136.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4AECAB89.6020909@gmail.com>
On Saturday 31 October 2009 23:26:33 Dale wrote:
> Denis wrote:
> > On Sat, Oct 31, 2009 at 12:52 PM, Harry Putnam <reader@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
next prev parent reply other threads:[~2009-10-31 22:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 16:52 [gentoo-user] Kernel upgrading and linux symlink Harry Putnam
2009-10-31 18:00 ` [gentoo-user] " Nikos Chantziaras
2009-10-31 18:09 ` Harry Putnam
2009-10-31 18:41 ` Nikos Chantziaras
2009-10-31 19:18 ` Alan McKinnon
2009-10-31 20:03 ` Nikos Chantziaras
2009-10-31 21:07 ` Alan McKinnon
2009-10-31 21:27 ` Nikos Chantziaras
2009-10-31 21:43 ` Mark Knecht
2009-10-31 22:17 ` Alan McKinnon
2009-10-31 20:06 ` Harry Putnam
2009-10-31 21:03 ` Alan McKinnon
2009-11-01 7:00 ` Dirk Heinrichs
2009-10-31 20:50 ` Neil Bothwick
2009-10-31 18:24 ` [gentoo-user] " Denis
2009-10-31 21:26 ` Dale
2009-10-31 22:20 ` Alan McKinnon [this message]
2009-10-31 22:52 ` Dale
2009-10-31 22:58 ` Alan McKinnon
2009-10-31 23:25 ` Neil Bothwick
2009-10-31 23:29 ` Mark Knecht
2009-10-31 23:40 ` [gentoo-user] " walt
2009-10-31 23:43 ` Mark Knecht
2009-10-31 23:41 ` [gentoo-user] " Alan McKinnon
2009-10-31 23:50 ` Mark Knecht
2009-10-31 23:43 ` Mike Edenfield
2009-11-01 6:55 ` Dirk Heinrichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200911010020.57136.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox