| 1 |
On Sat, Mar 9, 2013 at 2:39 PM, Graham Murray <graham@×××××××××××.uk> wrote: |
| 2 |
> Mike Gilbert <floppym@g.o> writes: |
| 3 |
> |
| 4 |
>> On Fri, Feb 22, 2013 at 1:52 PM, Jarry <mr.jarry@×××××.com> wrote: |
| 5 |
>>> So my question is: how is this possible? Is maybe ".config" |
| 6 |
>>> file from the old sources-tree copied to new sources-tree? |
| 7 |
>>> Or is the actual configuration of running kernel somehow |
| 8 |
>>> detected and ".config" file generated? |
| 9 |
>>> |
| 10 |
>> |
| 11 |
>> The latter. Have a look at DEFCONFIG_LIST init/Kconfig. |
| 12 |
> |
| 13 |
> So is it no longer necessary to run 'zcat /proc/config.gz > .config' to |
| 14 |
> transfer the current configuration as a 'seed' when installing a new |
| 15 |
> kernel? |
| 16 |
> |
| 17 |
|
| 18 |
That is porting your existing config to new kernel. You can't miss the |
| 19 |
step, lol. |
| 20 |
If you have genkernel, the simplest one would be |
| 21 |
|
| 22 |
genkernel --kernel-config=/proc/config.gz |
| 23 |
|
| 24 |
-- |
| 25 |
Nilesh Govindrajan |
| 26 |
http://nileshgr.com |
Archives