public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31
Date: Wed, 10 Mar 2010 14:09:22 +0000	[thread overview]
Message-ID: <20100310140922.77fc4045@zaphod.digimed.co.uk> (raw)
In-Reply-To: <4B97A508.8070204@libertytrek.org>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

On Wed, 10 Mar 2010 08:56:24 -0500, Tanstaafl wrote:

> > The .30, .31 is the minor kernel version. You shouldn't use oldconfig
> > when going from 2.4 to 2.6 but from 2.6.m to 2.6.n is safe.  
> 
> Again, not according to the official upgrade guide - it specifically
> uses 2.6.9-r1 to 2.6.9-r2 as an example of a 'minor' update, and going
> from 2.6.8 to 2.6.9 as having potentially 'too large of changes for make
> oldconfig to be considered safe'.
> 
> If the guide is outdated, maybe it should be updated:

Whatever the guide says, the third part of the kernel version is
considered the minor revision, anything after that is a patch level.

I see what you mean about the guide and consider it wrong, especially for
an advanced section. You are more likely to run into problems when not
reusing your old config that when using make oldconfig. Even the comment
about context isn't really true, as oldconfig shows some context and the
same help that menuconfig does.

My only complaint about oldconfig is that there is no way to step back or
undo a change, short of Ctrl-C and start again.


-- 
Neil Bothwick

Top Oxymorons Number 43: Genuine imitation

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-10 14:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  1:36 [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31 Walter Dnes
2010-03-10  9:02 ` Kaddeh
2010-03-10 13:22 ` Tanstaafl
2010-03-10 13:38   ` Dale
2010-03-10 13:46     ` Tanstaafl
2010-03-10 14:07       ` Alan McKinnon
2010-03-10 14:19         ` Tanstaafl
2010-03-11 10:16           ` Alan McKinnon
2010-03-10 13:47   ` Neil Bothwick
2010-03-10 13:56     ` Tanstaafl
2010-03-10 14:09       ` Neil Bothwick [this message]
2010-03-10 14:27         ` Tanstaafl
2010-03-10 14:35           ` Neil Bothwick
2010-03-10 15:46             ` Tanstaafl
2010-03-10 15:53             ` Paul Hartman
2010-03-10 14:09       ` Mick
2010-03-10 14:37         ` Neil Bothwick
2010-03-10 14:03   ` Alan McKinnon
2010-03-10 13:55 ` Mick
2010-03-11 13:03   ` Walter Dnes
2010-03-11 13:20     ` Neil Bothwick
2010-03-11 13:23     ` Jonathan
2010-03-11 23:38   ` [gentoo-user] Re: [solved] " Walter Dnes

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=20100310140922.77fc4045@zaphod.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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