| 1 |
On Wednesday 03 June 2009 18:39:56 Dale wrote: |
| 2 |
> >> will it respect the settings I've compiled |
| 3 |
> >> into 2.6.28 or will they need to be reset again before 2.6.29 is |
| 4 |
> >> compiled? |
| 5 |
> > |
| 6 |
> > No. Not unless you give it the old config to use. IIRC it has some |
| 7 |
> > feature to use the config for the currently running kernel |
| 8 |
> > (/proc/config.gz) if the running kernel supports it. But I could be may |
| 9 |
> > off course here too. |
| 10 |
> |
| 11 |
> Why not copy the config from the old kernel over and run make |
| 12 |
> oldconfig? May need to do some cleaning after genkernel tho. |
| 13 |
|
| 14 |
That's the correct way :-) |
| 15 |
|
| 16 |
But the OP asked if there was some magic way to get genkernel to use the same |
| 17 |
config as #SOME_OTHER_KERNEL. |
| 18 |
|
| 19 |
Which of course makes no sense as there can be multiple versions and configs |
| 20 |
present. |
| 21 |
|
| 22 |
The small remaining part of me that is still mostly unaffected by the onset of |
| 23 |
senility seems to remember genkernel being able to do something expressed as: |
| 24 |
|
| 25 |
zcat /proc/config.gz > /usr/src/linux/.config |
| 26 |
genkernel [....] |
| 27 |
|
| 28 |
Which I suppose is a reasonable thing for an app like genkernel to do. |
| 29 |
But I could also just be imagining it. It happens :-) |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
alan dot mckinnon at gmail dot com |
Archives