1 |
On 11/3/2009 11:10 PM, Harry Putnam wrote: |
2 |
> hamilton<hamilton@×××××.com> writes: |
3 |
|
4 |
>> Just checking - but you didn't mention: did you copy the .config to the |
5 |
>> new kernel src directory? If not, that would certainly explain the |
6 |
>> disparity in configuration settings you're seeing. |
7 |
>> |
8 |
> |
9 |
> I think you can say make `oldconfig' and the `old config' is supposed to |
10 |
> be incorporated so no I didn't |
11 |
> |
12 |
> If I had put .confg into the new sources, then plain make menuconfig |
13 |
> is what I would have used. |
14 |
> |
15 |
> Do you know where the man pages or docs for that stuff is .. its not in |
16 |
> `man make' |
17 |
|
18 |
The 'make' man page wouldn't know anything about the kernel's makefile. |
19 |
You want the README file that's included in the top of the kernel |
20 |
source folder. That file says, among other things: |
21 |
|
22 |
"make oldconfig" Default all questions based on the contents of |
23 |
your existing ./.config file and asking about |
24 |
new config symbols. |
25 |
|
26 |
You need to already have a .config file in the source tree in order for |
27 |
'make oldconfig' to work; otherwise you are going to get the default |
28 |
answers to just about every question. The benefit of this is that you |
29 |
don't have to search through the entire menu tree in the UI to find |
30 |
what's new. |
31 |
|
32 |
When you're ready to build a new kernel version, you should copy the |
33 |
.config file from your current kernel into the new source tree. For |
34 |
example, if you use 'make install' it will copy .config to |
35 |
/boot/config-<kernel version>; from there you can copy it back to |
36 |
/usr/src/linux/.config for the next version. |
37 |
|
38 |
When you run 'oldconfig' you should rarely get more than a few dozen |
39 |
questions, and it should all be on truly new items that didn't exist in |
40 |
your previous kernel. The hardware drivers you selected should all |
41 |
carry over as-is. |
42 |
|
43 |
--Mike |