From: Coert Waagmeester <lgroups@waagmeester.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SOLVED gentoo-sources menuconfig feature/weirdness
Date: Thu, 23 Feb 2012 13:16:41 +0200 [thread overview]
Message-ID: <4F462019.4020703@waagmeester.co.za> (raw)
In-Reply-To: <20120223130822.1a260044@khamul.example.com>
On 02/23/2012 01:08 PM, Alan McKinnon wrote:
> On Thu, 23 Feb 2012 12:48:35 +0200
> Coert Waagmeester<lgroups@waagmeester.co.za> wrote:
>
>> On 02/23/2012 11:17 AM, Neil Bothwick wrote:
>>> On Thu, 23 Feb 2012 10:51:43 +0200, Coert Waagmeester wrote:
>>>
>>>> The only thing I can currently think of is maybe the kernel config
>>>> files in /boot?
>>>
>>> I'd say it's more likely to be getting it from /proc/config.gz.
>>>
>>> But why start with a clean config each time? That means you have
>>> plenty of opportunities to produce a broken kernel on every update.
>>>
>>>
>>
>> Is there a way to import old config files with newer kernel sources?
>> I tried it once by simply copying .config into the newer src dir, but
>> I read somewhere that there could be incompatibilities.
>>
>
> That is exactly how you do it. Copy a .config over and run make
> oldconfig
I am definitely going to try this.
>
> Yes, there could be incompatibilities. This might happen once every few
> years when you do an upgrade over 10 version numbers. But that can be
> fixed.
>
> Not doing it this way means a very high likelyhood of the machine not
> booting with every single upgrade, plus the huge amount of work it
> takes to go through everything in menuconfig.
indeed, especially when the server is stuck in a far away rack.
>
> The choices are simple,
>
> - low risk of occasional breakage
> - high risk of frequent breakage
>
>
>
Thank you all
next prev parent reply other threads:[~2012-02-23 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:10 [gentoo-user] gentoo-sources menuconfig feature/weirdness Coert Waagmeester
2012-02-23 8:25 ` Mick
2012-02-23 8:51 ` Coert Waagmeester
2012-02-23 9:17 ` Neil Bothwick
2012-02-23 10:48 ` Coert Waagmeester
2012-02-23 11:08 ` Alan McKinnon
2012-02-23 11:16 ` Coert Waagmeester [this message]
2012-02-23 11:25 ` [gentoo-user] SOLVED " Alan McKinnon
2012-02-23 12:24 ` J. Roeleveld
2012-02-23 14:04 ` Mark Knecht
2012-02-24 22:11 ` [gentoo-user] " ny6p01
2012-02-24 23:02 ` Neil Bothwick
2012-02-24 23:44 ` David W Noon
2012-02-24 23:49 ` Dale
2012-02-25 1:52 ` ny6p01
2012-02-25 2:10 ` Dale
2012-02-25 2:50 ` Pandu Poluan
2012-02-25 11:38 ` Dale
2012-02-24 22:08 ` ny6p01
2012-02-23 9:25 ` William Kenworthy
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=4F462019.4020703@waagmeester.co.za \
--to=lgroups@waagmeester.co.za \
--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