public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benno Schulenberg <benno.schulenberg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Wed, 30 May 2007 12:03:44 +0200	[thread overview]
Message-ID: <200705301203.44714.benno.schulenberg@gmail.com> (raw)
In-Reply-To: <9acccfe50705292020peb200e8jc12c0036ff64cc30@mail.gmail.com>

Kevin O'Gorman wrote:
> On 5/29/07, Denis <denis.che@gmail.com> wrote:
> > I usually dread kernel updates because then I have to go
> > through kernel menuconfig all over again, and for me, that
> > takes some time.  I guess one can reuse the old .config file,
> > but I understand it's not always a safe thing to do.
>
> You can use the old .config safely if you "make oldconfig" before
> anything else.  It will prompt you for replies to any new things,
> and quietly ditch anything it doesn't recognize.

And this can ditch needed options when they get renamed or replaced, 
like happened with the netfilter stuff on the upgrade to 2.6.17, 
and with some IDE/ATA stuff on the upgrade to 2.6.20.  Just running 
'make oldconfig' on a 2.6.x to 2.6.y upgrade will not always give 
you a fully working kernel.

> > Is it reasonably ok to wait for every "major" 2.6.x release to
> > update, or is it necessary to update on every minor 2.6.x.y
> > release also?

If your kernel does everything you need and you are content with its 
performance, there's no need to upgrade to a new 2.6.y.  Just put a 
~sys-kernel/gentoo-sources-2.6.y into /etc/portage/package.mask and 
forget about it.  But the -rn upgrades for your current version you 
normally _do want to install because they fix serious bugs.  Often 
those bugs affect only specific hardware, but there's no harm in 
blindly upgrading: these little rev bumps _are safe.

Benno
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-30 10:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 14:01 [gentoo-user] how do you keep up with system administration? Denis
2007-05-29 14:29 ` Mark Shields
2007-05-29 14:32 ` Kevin O'Gorman
2007-05-29 14:40 ` Ryan Sims
2007-05-29 14:48 ` Albert Hopkins
2007-05-29 14:50 ` Daniel Iliev
2007-05-29 16:49   ` Roy Wright
2007-05-29 17:07 ` Ralf Stephan
2007-05-29 17:39 ` Florian Philipp
2007-05-29 19:07   ` Denis
2007-05-29 18:45 ` kashani
2007-05-30  0:16 ` Tim Allinghan
2007-05-30  1:19   ` Denis
2007-05-30  2:20     ` Ryan Sims
2007-05-30  2:53       ` Michael Sullivan
2007-05-30  3:05       ` Denis
2007-05-30  7:21         ` Neil Bothwick
2007-05-30  9:06           ` Eray Aslan
2007-05-30  3:20     ` Kevin O'Gorman
2007-05-30 10:03       ` Benno Schulenberg [this message]
2007-05-30 17:20         ` Denis
2007-05-30 20:57           ` Neil Bothwick
2007-05-30  3:49 ` Boyd Stephen Smith Jr.
2007-05-30  4:37   ` Denis
2007-05-30  7:22     ` Neil Bothwick
2007-05-30  7:25     ` John covici

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=200705301203.44714.benno.schulenberg@gmail.com \
    --to=benno.schulenberg@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