| 1 |
On 17 Jul 2007, at 21:11, Billy Wayne McCann wrote: |
| 2 |
> |
| 3 |
>> It is sometimes possible to save time by re-using the |
| 4 |
>> configuration file |
| 5 |
>> from your old kernel when configuring the new one. Note that this is |
| 6 |
>> generally unsafe -- too many changes between every kernel release for |
| 7 |
>> this to be a reliable upgrade path. |
| 8 |
>> |
| 9 |
>> The only situation where this is appropriate is when upgrading |
| 10 |
>> from one |
| 11 |
>> Gentoo kernel revision to another. For example, the changes made |
| 12 |
>> between |
| 13 |
>> gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very |
| 14 |
>> small, |
| 15 |
>> so it is usually OK to use the following method. However, it is not |
| 16 |
>> appropriate to use it in the example used throughout this document: |
| 17 |
>> upgrading from 2.6.8 to 2.6.9. |
| 18 |
|
| 19 |
Whilst I'll admit to having been caught out when upgrading from |
| 20 |
2.6.19 to 2.6.20, I can't imagine that many people go through the |
| 21 |
entire list of options in `make menuconfig` every time they upgrade |
| 22 |
the kernel. |
| 23 |
|
| 24 |
I tend to run `emerge sync once a week or once a month, and I ignore |
| 25 |
trivial kernel version bumps (-r2 to -r3 &c), so the only time I |
| 26 |
upgrade is in exactly the circumstances described. |
| 27 |
|
| 28 |
For a long time I copied the old .config file over verbatim and it's |
| 29 |
only recently I even realised to use `make oldconfig`. This apparent |
| 30 |
change in the way the options are laid out between the 2.6.19 and |
| 31 |
2.6.20 config files is the first time it's failed on me in over 3 |
| 32 |
years, so I don't see the need to be overly paranoid about it. |
| 33 |
|
| 34 |
Stroller. |
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives