| 1 |
Thanks James and Qian, |
| 2 |
|
| 3 |
But doesn't this conflict with the advice given in kernel-upgrade.xml, which |
| 4 |
says: |
| 5 |
|
| 6 |
The only situation where this is appropriate is when upgrading from one Gentoo kernel revision to another. For example, the changes made between gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very small, so it is usually OK to use the following method. However, it is not appropriate to use it in the example used throughout this document: upgrading from 2.6.8 to 2.6.9. Too many changes between the official releases, and the method described below does not display enough context to the user, often resulting in the user running into problems because they disabled options that they really didn't want to. |
| 7 |
|
| 8 |
As I am going from 2.6.10-gentoo-r6 to 2.6.12-gentoo-r10, which is more |
| 9 |
than just a revision change, it would seen that 'make oldconfig' is not |
| 10 |
recomended. |
| 11 |
|
| 12 |
Regards, |
| 13 |
DigbyT |
| 14 |
|
| 15 |
On Thu, Oct 27, 2005 at 08:25:52PM -0400, James Hiscock wrote: |
| 16 |
> > I gather one cannot just copy the .config file for this much of a jump, |
| 17 |
> > so I guess the best thing to do is a simultaneous 'make menuconfig' in both |
| 18 |
> > old and new kernel using two different windows so that I can be sure |
| 19 |
> > to copy each of the current settings across. |
| 20 |
> |
| 21 |
> Easier solution: copy the .config, and then run "make oldconfig" -- |
| 22 |
> it'll prompt you for any changes made in the new kernel, and dump any |
| 23 |
> invalid options... |
| 24 |
> |
| 25 |
> -- |
| 26 |
> gentoo-user@g.o mailing list |
| 27 |
|
| 28 |
-- |
| 29 |
Digby R. S. Tarvin digbyt@××××××.com |
| 30 |
http://www.digbyt.com |
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives