On 2011-08-01, Pandu Poluan pa...@poluan.info wrote:
Let's say I have a .config from an older kernel version (for example,
2.6.38), and now I want to install a newer kernel (let's say, 3.0).
Is it necessary to first do `make oldconfig`, or is it safe to go
directly to `make menuconfig`?
It's
On Mon, Aug 1, 2011 at 21:09, Grant Edwards grant.b.edwa...@gmail.com wrote:
On 2011-08-01, Pandu Poluan pa...@poluan.info wrote:
Let's say I have a .config from an older kernel version (for example,
2.6.38), and now I want to install a newer kernel (let's say, 3.0).
Is it necessary to first
On Mon, Aug 1, 2011 at 10:09 AM, Grant Edwards
grant.b.edwa...@gmail.com wrote:
On 2011-08-01, Pandu Poluan pa...@poluan.info wrote:
Let's say I have a .config from an older kernel version (for example,
2.6.38), and now I want to install a newer kernel (let's say, 3.0).
Is it necessary to
On Mon, 1 Aug 2011 21:39:29 +0700, Pandu Poluan wrote about Re:
[gentoo-user] Re: make oldconfig necessary?:
What I meant was:
If I want a kernel config as close as possible to the older kernel,
can I just use `make menuconfig`, or do I have to first run `make
oldconfig`.
Just copy your
On 2011-08-01, Michael Orlitzky mich...@orlitzky.com wrote:
Use oldconfig. Running 'oldconfig' will prompt you for any new
sections/drivers that have appeared since your last kernel. Running
'menuconfig' will silently accept all of the defaults for these new
options.
Why is it safer if only
On Monday 01 August 2011 17:58:18 David W Noon wrote:
The make menuconfig will silently do a make oldconfig on the
existing .config file before it puts the menu on the screen. This
means that the options in the menu hierarchy will reflect the options
that were in your old .config file, with
6 matches
Mail list logo
