| 1 |
On Wednesday 10 March 2010 15:22:41 Tanstaafl wrote: |
| 2 |
> On 2010-03-09 8:36 PM, Walter Dnes wrote: |
| 3 |
> > Today is when running a lilo menu with "production" and "experimental" |
| 4 |
> > kernels saved me. "production" is 2.6.30-r8. "experimental" is |
| 5 |
> > 2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set |
| 6 |
> > /usr/src/linux to point at 2.6.31-r6 (or 10), copied .config from |
| 7 |
> > 2.6.30-r8 and ran "make oldconfig". |
| 8 |
> |
| 9 |
> I *never* use make oldconfig between major kernel versions... |
| 10 |
|
| 11 |
A major kernel upgrade is from 2.6 to 2.7 |
| 12 |
|
| 13 |
2.6.30 to 2.6.31 is a small incremental upgrade and |
| 14 |
2.6.30.1 to 2.6.30.2 is a bug fix |
| 15 |
|
| 16 |
Common sense tells me that you will forget something important using your |
| 17 |
method much more often than oldconfig will trip over a new option (eg the pata |
| 18 |
shuffle about 2 years ago) |
| 19 |
|
| 20 |
> I do as the kernel upgrade guide says - when going between major |
| 21 |
> versions (yes, even one), copy the old .config to the new kernel dir, |
| 22 |
> then run make menuconfig, and make sure all of your critical options are |
| 23 |
> set. This is much safer, though it does take more time. |
| 24 |
|
| 25 |
Well, that guide is someone's opinion. It is not a technical fact. |
| 26 |
|
| 27 |
I write wiki pages that seem to be to be 100% spot on and the best advice |
| 28 |
ever. But some of my colleagues ignore it and do it their way. Stuff they do |
| 29 |
does not break. |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
alan dot mckinnon at gmail dot com |
Archives