public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Peixoto de Morais Neto" <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel upgrade problem
Date: Wed, 5 Nov 2008 15:38:32 -0200	[thread overview]
Message-ID: <38af3d670811050938v1e069f67y3f4ad1d87e07055c@mail.gmail.com> (raw)
In-Reply-To: <20081104175610.246b7e89@osage.osagesoftware.com>

On Tue, Nov 4, 2008 at 8:56 PM, David Relson <relson@osagesoftware.com> wrote:
> Hello Dirk,
>
> Thanks for taking the time to reply.  The combination of gentoo-sources
> and genkernel has been working quite well for the 2 yrs I've been
> running Gentoo.  It's convenient to have grub.conf auto-magically
> updated and that's not been an issue.
You don't need to edit grub.conf at all.
"make install" automatically updates the symlinks in /boot/
For me, the kernel update process is:
emerge -a1v sys-kernel/vanilla-sources
cd /usr/src/linux
// I usually issue make defconfig to start with a fresh config. But if
you skip make defconfig, the following command will start with your
old config from /boot/config
make menuconfig
make
make install modules_install
//The above command automatically copies the kernel image, System.map
and .config to /boot and updates the /boot/vmlinuz, /boot/vmlinuz.old,
/boot/config, /boot/config.old, /boot/System.map, /boot/System.map.old
symlinks. It also copies the modules to /lib/modules
//No need for genkernel, no need to edit grub.conf
*reboot
*delete obsolete modules in /lib/modules, and obsolete files in /boot
*By the way, before i delete obsolete config file in /boot, i back it
up in a oldconfigs.tar.lzma compressed archive.



      reply	other threads:[~2008-11-05 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 19:51 [gentoo-user] Kernel upgrade problem David Relson
2008-11-04 21:27 ` Dirk Heinrichs
2008-11-04 22:56   ` David Relson
2008-11-05 17:38     ` Jorge Peixoto de Morais Neto [this message]

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=38af3d670811050938v1e069f67y3f4ad1d87e07055c@mail.gmail.com \
    --to=please.no.spam.here@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