1 |
Harry Putnam <reader@×××××××.com> writes: |
2 |
|
3 |
> I think you can say make `oldconfig' and the `old config' is supposed to |
4 |
> be incorporated so no I didn't |
5 |
> |
6 |
> If I had put .confg into the new sources, then plain make menuconfig |
7 |
> is what I would have used. |
8 |
|
9 |
That is the wrong way round! make oldconfig uses the .config in the |
10 |
kernel directory, which in the case of an upgrade is the *default* (ie |
11 |
without any customisations) config. make oldconfig does *not* operate on |
12 |
the running kernel. You have to copy the .config from the running (old) |
13 |
kernel to the new kernel directory before running make oldconfig. If you |
14 |
start with the default config, then you have to run make menuconfig (or |
15 |
config or xconfig) to customise it every time. |