| 1 |
On Thu, 23 Feb 2012 12:48:35 +0200 |
| 2 |
Coert Waagmeester <lgroups@××××××××××××××.za> wrote: |
| 3 |
|
| 4 |
> On 02/23/2012 11:17 AM, Neil Bothwick wrote: |
| 5 |
> > On Thu, 23 Feb 2012 10:51:43 +0200, Coert Waagmeester wrote: |
| 6 |
> > |
| 7 |
> >> The only thing I can currently think of is maybe the kernel config |
| 8 |
> >> files in /boot? |
| 9 |
> > |
| 10 |
> > I'd say it's more likely to be getting it from /proc/config.gz. |
| 11 |
> > |
| 12 |
> > But why start with a clean config each time? That means you have |
| 13 |
> > plenty of opportunities to produce a broken kernel on every update. |
| 14 |
> > |
| 15 |
> > |
| 16 |
> |
| 17 |
> Is there a way to import old config files with newer kernel sources? |
| 18 |
> I tried it once by simply copying .config into the newer src dir, but |
| 19 |
> I read somewhere that there could be incompatibilities. |
| 20 |
> |
| 21 |
|
| 22 |
That is exactly how you do it. Copy a .config over and run make |
| 23 |
oldconfig |
| 24 |
|
| 25 |
Yes, there could be incompatibilities. This might happen once every few |
| 26 |
years when you do an upgrade over 10 version numbers. But that can be |
| 27 |
fixed. |
| 28 |
|
| 29 |
Not doing it this way means a very high likelyhood of the machine not |
| 30 |
booting with every single upgrade, plus the huge amount of work it |
| 31 |
takes to go through everything in menuconfig. |
| 32 |
|
| 33 |
The choices are simple, |
| 34 |
|
| 35 |
- low risk of occasional breakage |
| 36 |
- high risk of frequent breakage |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Alan McKinnnon |
| 42 |
alan.mckinnon@×××××.com |
Archives