From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel upgrade question: is it adviseable?
Date: Wed, 3 Jun 2009 21:14:03 +0200 [thread overview]
Message-ID: <200906032114.04014.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4A26A75C.3050001@gmail.com>
On Wednesday 03 June 2009 18:39:56 Dale wrote:
> >> will it respect the settings I've compiled
> >> into 2.6.28 or will they need to be reset again before 2.6.29 is
> >> compiled?
> >
> > No. Not unless you give it the old config to use. IIRC it has some
> > feature to use the config for the currently running kernel
> > (/proc/config.gz) if the running kernel supports it. But I could be may
> > off course here too.
>
> Why not copy the config from the old kernel over and run make
> oldconfig? May need to do some cleaning after genkernel tho.
That's the correct way :-)
But the OP asked if there was some magic way to get genkernel to use the same
config as #SOME_OTHER_KERNEL.
Which of course makes no sense as there can be multiple versions and configs
present.
The small remaining part of me that is still mostly unaffected by the onset of
senility seems to remember genkernel being able to do something expressed as:
zcat /proc/config.gz > /usr/src/linux/.config
genkernel [....]
Which I suppose is a reasonable thing for an app like genkernel to do.
But I could also just be imagining it. It happens :-)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-06-03 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:43 [gentoo-user] Kernel upgrade question: is it adviseable? James Homuth
2009-06-03 15:50 ` Alan McKinnon
2009-06-03 16:39 ` Dale
2009-06-03 19:14 ` Alan McKinnon [this message]
2009-06-03 20:40 ` Dale
2009-06-04 3:01 ` Rumen Yotov
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=200906032114.04014.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