| 1 |
On 11/04/2009 06:16 AM, james wrote: |
| 2 |
> Graham Murray <graham <at> gmurray.org.uk> writes: |
| 3 |
> |
| 4 |
> You have to copy the .config from the running (old) |
| 5 |
>> kernel to the new kernel directory before running make oldconfig. If you |
| 6 |
>> start with the default config, then you have to run make menuconfig (or |
| 7 |
>> config or xconfig) to customise it every time. |
| 8 |
> |
| 9 |
> |
| 10 |
> Hmmmmm, |
| 11 |
> |
| 12 |
> |
| 13 |
> I thought when you install a new kernel, you just change the symbolic link. |
| 14 |
> |
| 15 |
> example (old kernel linux-2.6.30-gentoo-r4) |
| 16 |
> New kernel (linux-2.6.30-gentoo-r5) |
| 17 |
> |
| 18 |
> |
| 19 |
> cd /usr/src |
| 20 |
> rm linux |
| 21 |
> ls -sf /usr/src/linux-2.6.30-gentoo-r5 linux |
| 22 |
> cd linux |
| 23 |
> make menuconfig |
| 24 |
|
| 25 |
Well, if you really want to use menuconfig first, you need to repeat the |
| 26 |
entire configuration process from the beginning. Make oldconfig is there |
| 27 |
exactly so you *don't* need to repeat everything manually. |
| 28 |
|
| 29 |
> At this point the new kernel sources (linux-2.6.30-gentoo-r5) |
| 30 |
> automatically copies over the .config from the version |
| 31 |
> of the kernel you are actually running... |
| 32 |
|
| 33 |
That sentence doesn't make sense. You said the sources automatically copy |
| 34 |
the .config -- but the sources don't do anything. Only a program could do |
| 35 |
something automatically, not source code files. It may be that genkernel |
| 36 |
does something like that, but I've never used it so I don't know. |
| 37 |
|
| 38 |
If you are building your kernel manually (as you seem to be doing) then *you* |
| 39 |
need to copy the .config from the old sources over to your new kernel source |
| 40 |
directory and *then* do make oldconfig. That's when the magic happens, not |
| 41 |
before. |
| 42 |
|
| 43 |
You'll see lots of interesting stuff if you run 'make help' in the kernel |
| 44 |
source directory. |
Archives