public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: kernel panic -- finding proper config diff
Date: Sat, 24 Oct 2009 11:41:40 +0100	[thread overview]
Message-ID: <63AD5AF6-71CC-407B-888C-458352BA708B@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200910222050.19932.alan.mckinnon@gmail.com>


On 22 Oct 2009, at 19:50, Alan McKinnon wrote:
> On Thursday 22 October 2009 20:17:46 Maxim Wexler wrote:
>>> Why not copy over the .29 config and run make oldconfig?
>>
>> I thought of that, but isn't there too much difference in the
>> versions? I read somewhere that taking to big a leap between versions
>> is unsafe. Not to mention the great whack of new options. If you do a
>> diff -y between the two configs there are lots of gaps.
>
>
> That's version jumps like 2.4 to 2.6
>
> The 2.6 development model is small incremental steps, so the odds  
> are always
> in your favour that it will work just fine. Occasionally you might  
> find two
> versions that don't like to play nicely with oldconfig but that  
> isn't the
> norm.
>
> FWIW, I haven't encountered a single problem with the entire 2.6  
> range.

There was a change between 2.6.x and 2.6.x+1 where the whole .config  
was rearranged and `make oldconfig` no longer worked. It was a while  
ago, so maybe you don't recall it. I think x was circa 22 or so. It  
was discussed on here at the time, IIRC, and caused filesystems such   
as ext2 (at least) to be unselected if you just ran `make oldconfig`.

Stroller.




  reply	other threads:[~2009-10-24 10:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 18:25 [gentoo-user] kernel panic -- finding proper config diff Maxim Wexler
2009-10-21 18:56 ` [gentoo-user] " Maxim Wexler
2009-10-21 19:07 ` Jonathan Callen
2009-10-21 19:13   ` Alan McKinnon
2009-10-21 20:22     ` Maxim Wexler
2009-10-21 20:35       ` Albert Hopkins
2009-10-21 20:45   ` Maxim Wexler
2009-10-22  1:19     ` walt
2009-10-22  3:28       ` Maxim Wexler
2009-10-22  3:37         ` William Kenworthy
2009-10-22  3:45           ` Maxim Wexler
2009-10-22 14:18         ` Neil Bothwick
2009-10-22 18:17           ` Maxim Wexler
2009-10-22 18:29             ` Neil Bothwick
2009-10-22 18:36             ` Maxim Wexler
2009-10-22 18:53               ` Alan McKinnon
2009-10-22 20:43                 ` Maxim Wexler
2009-10-22 19:31               ` Neil Bothwick
2009-10-22 18:50             ` Alan McKinnon
2009-10-24 10:41               ` Stroller [this message]
2009-10-22  1:48     ` Maxim Wexler
2009-10-22 23:31 ` walt
2009-10-23  0:31   ` Neil Bothwick
2009-10-23 16:02   ` walt
2009-10-23 21:57     ` Maxim Wexler
2009-10-23 22:54       ` walt
2009-10-24  1:33         ` Richard Marza
2009-10-24  4:05           ` Maxim Wexler
2009-10-24  7:44             ` Neil Bothwick
2009-10-24  7:44       ` Neil Bothwick
2009-10-26  4:52         ` Maxim Wexler
2009-10-26  9:10           ` Neil Bothwick
2009-10-29  4:38             ` waltdnes
2009-10-29  5:45               ` Maxim Wexler
2009-10-29  5:42             ` Maxim Wexler
2009-10-23  0:56 ` Jonathan Callen

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=63AD5AF6-71CC-407B-888C-458352BA708B@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.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