public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Billy Wayne McCann <thebillywayne@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
Date: Tue, 17 Jul 2007 14:24:56 -0500	[thread overview]
Message-ID: <469D1788.3030603@gmail.com> (raw)
In-Reply-To: <1184680951.15828.57.camel@blackwidow.nbk>

Albert Hopkins wrote:
> On Tue, 2007-07-17 at 15:19 +0200, Alan McKinnon wrote:
>> On Tuesday 17 July 2007, Mick wrote:
>>> On Tuesday 17 July 2007 13:20, Billy McCann wrote:
>>>> Hi Mick.   From what I understand, using oldconfig for major
>>>> version changes (.20 -> .21) is a bad idea.  Here's what I did.  It
>>>> may be slow and stupid but it worked like a charm.
>>> Sure, but I have been using oldconfig for previous major changes and
>>> never had a problem like this before.
>> Now you know why the kernel devs keep telling you not to do it, heh :-)
>>
> 
> I don't know which kernel dev keeps saying that, but I'd recommend
> he/she specify what is meant by "major version" since, historically:
> 
> 2.6.22
> ^ ^ ^
> | | +--- Revision
> | +----- Minor version
> +------- Major version
> 
> And therefore .20 -> .21 would not be considered a "major" version
> change by most accounts.
> 
> --
> Albert W. Hopkins

Thanks for correcting my nomenclature, Albert.  I too was wanting to use
oldconfig for upgrading my kernel from .20 to .21, but decided not to
after reading the recommendation of the Gentoo Kernel Upgrade Guide, the
relevant portion of which I have pasted below. Perhaps this applied only
to the specific example used.

My purpose for pasting this into this discussion is three-fold: to show
why I said what I did, to hopefully dispel the notion that I merely made
this all up, and to discuss the relevance of the pasted text itself.

I apologize for being off-topic and hope that Mick finds himself a
working kernel config soon.  :)


Billy Wayne

=====================

(Note the the second and third sentences of the second paragraph.)

http://www.gentoo.org/doc/en/kernel-upgrade.xml

10. Advanced: Using your old kernel .config to configure a new one

It is sometimes possible to save time by re-using the configuration file
from your old kernel when configuring the new one. Note that this is
generally unsafe -- too many changes between every kernel release for
this to be a reliable upgrade path.

The only situation where this is appropriate is when upgrading from one
Gentoo kernel revision to another. For example, the changes made between
gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very small,
so it is usually OK to use the following method. However, it is not
appropriate to use it in the example used throughout this document:
upgrading from 2.6.8 to 2.6.9. Too many changes between the official
releases, and the method described below does not display enough context
to the user, often resulting in the user running into problems because
they disabled options that they really didn't want to.

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-07-17 19:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 11:40 [gentoo-user] Cannot boot 2.6.21-gentoo-r4 Mick
2007-07-17 12:20 ` Billy McCann
2007-07-17 12:45   ` Mick
2007-07-17 13:19     ` Alan McKinnon
2007-07-17 14:02       ` Albert Hopkins
2007-07-17 15:35         ` Dale
2007-07-17 19:24         ` Billy Wayne McCann [this message]
2007-07-17 20:11           ` [gentoo-user] Using oldconfig and kernel revisions ( was : Cannot boot 2.6.21-gentoo-r4) Billy Wayne McCann
2007-07-17 21:19             ` Stroller
2007-07-18  4:59           ` [gentoo-user] OT " Albert Hopkins
2007-07-19 20:33             ` Billy McCann
2007-07-20  6:49               ` Luigi Pinna
2007-07-20  9:02                 ` Ian Hastie
2007-07-20 12:42                 ` Albert Hopkins
2007-07-17 13:22   ` Re[2]: [gentoo-user] Cannot boot 2.6.21-gentoo-r4 Sergey A. Kobzar
2007-07-17 13:30   ` Neil Bothwick
2007-07-17 14:00     ` Mick
2007-07-17 14:46       ` Neil Bothwick
2007-07-17 15:18         ` Mick
2007-07-17 21:02           ` Peter Alfredsen
2007-07-17 22:20             ` Mick

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=469D1788.3030603@gmail.com \
    --to=thebillywayne@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