On Tue, Apr 19, 2016 at 5:01 AM, James wrote:
> Hello,
>
> After copying the current ".config" to the newly linked sources
> (/usr/src/linux) I use to run 'make oldconfig'. Now, looking at
> the gentoo wiki [1] I see (2) choices but no 'make oldconfig'::
>
> 1) #make silentoldconfig
>
> 2) #make
On Tue, Apr 19, 2016 at 4:01 AM, James wrote:
>
> After copying the current ".config" to the newly linked sources
> (/usr/src/linux) I use to run 'make oldconfig'. Now, looking at
> the gentoo wiki [1] I see (2) choices but no 'make oldconfig'::
>
> 1) #make silentoldconfig
>
> 2) #make olddefconf
On 04/18/2016 07:01 PM, James wrote:
> Hello,
>
> After copying the current ".config" to the newly linked sources
> (/usr/src/linux) I use to run 'make oldconfig'. Now, looking at
> the gentoo wiki [1] I see (2) choices but no 'make oldconfig'::
>
> 1) #make silentoldconfig
>
> 2) #make olddefc
Hello,
After copying the current ".config" to the newly linked sources
(/usr/src/linux) I use to run 'make oldconfig'. Now, looking at
the gentoo wiki [1] I see (2) choices but no 'make oldconfig'::
1) #make silentoldconfig
2) #make olddefconfig
3) #make oldconfig
(3) still seems to work. (2)
On 08/01/2011 12:00 PM, kashani wrote:
> On 7/31/2011 7:06 PM, Pandu Poluan 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
On 7/31/2011 7:06 PM, Pandu Poluan 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`?
Necessary to run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 1 Aug 2011 09:06:17 +0700, Pandu Poluan wrote about
"[gentoo-user] make oldconfig necessary?":
>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 (l
On Sunday, July 31 at 21:23 (-0500), Jeremy McSpadden said:
> Better to run make oldconfig. It merges the changes.
>
> --
> Jeremy McSpadden
> def...@uberpenguin.net
>
>
>
>
> On Jul 31, 2011, at 9:06 PM, Pandu Poluan wrote:
>
> > Let's say I have a .config from an older kernel version (fo
On Jul 31, 2011 7:06 PM, "Pandu Poluan" 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`?
>
Y
On Sun, Jul 31, 2011 at 7:06 PM, Pandu Poluan 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`?
Jeremy McSpadden wrote:
Better to run make oldconfig. It merges the changes.
--
Jeremy McSpadden
def...@uberpenguin.net
Yep. I always run make oldconfig then just run make && make
modules_install. Once oldconfig is done, the kernel should be
configured and ready to build.
Dale
:-)
Better to run make oldconfig. It merges the changes.
--
Jeremy McSpadden
def...@uberpenguin.net
On Jul 31, 2011, at 9:06 PM, Pandu Poluan 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).
>
> I
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`?
Rgds,
--
--
Pandu E Poluan - IT Optimizer
My website: http:
Eric Martin wrote:
Dale wrote:
Daniel Pielmeier wrote:
At least in the kernel Makefile there is no hint about /proc/config.gz
which contains the running kernel configuration, so I think make
oldconfig or your favourite kernel configuration tool is still needed.
If there is no .config o
Dale wrote:
> Daniel Pielmeier wrote:
>> 2008/8/4, James <[EMAIL PROTECTED]>:
>>
>>> Hello,
>>>
>>> It seems like I remember that 'make oldconfig' is not
>>> needed any more, to pass the current (booted) kernel
>>> option to the .config for building a new kernel.
>>>
>>> Of is 'make oldconfig' s
Daniel Pielmeier wrote:
2008/8/4, James <[EMAIL PROTECTED]>:
Hello,
It seems like I remember that 'make oldconfig' is not
needed any more, to pass the current (booted) kernel
option to the .config for building a new kernel.
Of is 'make oldconfig' still a good idea?
James
At least
2008/8/4, James <[EMAIL PROTECTED]>:
> Hello,
>
> It seems like I remember that 'make oldconfig' is not
> needed any more, to pass the current (booted) kernel
> option to the .config for building a new kernel.
>
> Of is 'make oldconfig' still a good idea?
>
>
> James
At least in the kernel Makefi
James wrote:
> Hello,
>
> It seems like I remember that 'make oldconfig' is not
> needed any more, to pass the current (booted) kernel
> option to the .config for building a new kernel.
>
> Of is 'make oldconfig' still a good idea?
>
>
> James
>
>
>
>
You still need make oldconfig AFAIK.
Hello,
It seems like I remember that 'make oldconfig' is not
needed any more, to pass the current (booted) kernel
option to the .config for building a new kernel.
Of is 'make oldconfig' still a good idea?
James
Hi all,
I faced an ethernet driver miss during my kernel configuration,
because I had a wrong idea of what 'make oldconfig' did. I thought the
oldconfig target build up a new .config file starting from the
/proc/config.gz one then asking for new options.
But It was not the case here:
sd-4421 li
20 matches
Mail list logo