public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
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 16:07:16 +0200	[thread overview]
Message-ID: <201003101607.16364.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4B97A29B.7090707@libertytrek.org>

On Wednesday 10 March 2010 15:46:03 Tanstaafl wrote:
> On 2010-03-10 8:38 AM, Dale wrote:
> > I use make oldconfig all the time and have only had problems with it
> > once.  I would trust make oldconfig looong before I would even think to
> > trust genkernel.  I have never got it to work for me.
> > 
> > Using make oldconfig should be fine for the OP.
> 
> My point is, the recommended method per the official gentoo docs/kernel
> upgrade guide is


Let me correct you on your misunderstanding:

The current opinion of the current author of the kernel upgrade guide says 
what you quoted.

It's his opinion, it's what he thinks will work best for the majority of 
people. It's probably also the wording that has been proven to result in the 
least bugzilla entries and the fewest mails in his inbox from the "Help me!" 
mob.

It's not a technical data sheet, and what you quote is not a fact


> , using make oldconfig is only recommended for minor
> bumps of the same kernel version, and for major updates - and again,
> yes, even going from 2.6.30 to 2.6.31 is a 'major' update, copying the
> old .config then doing make menuconfig is the preferred/recommended way.
> 
> If you want to live dangerously, that is fine, but please do not ignore
> the fact that it is *not* the *recommended/preferred* - ie *safest* - way.

Wrong. See above.

How do I know this? I too write technical docs. I too write them to minimize 
the size of my inbox. Do you think for a minute I actually *follow* the advice 
of give to others less knowledgeable than myself?



-- 
alan dot mckinnon at gmail dot com



  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 [this message]
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
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=201003101607.16364.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