| 1 |
On 08/01/2011 12:00 PM, kashani wrote: |
| 2 |
> On 7/31/2011 7:06 PM, Pandu Poluan wrote: |
| 3 |
>> Let's say I have a .config from an older kernel version (for example, |
| 4 |
>> 2.6.38), and now I want to install a newer kernel (let's say, 3.0). |
| 5 |
>> |
| 6 |
>> Is it necessary to first do `make oldconfig`, or is it safe to go |
| 7 |
>> directly to `make menuconfig`? |
| 8 |
> |
| 9 |
> Necessary to run make old config? No. |
| 10 |
> |
| 11 |
> Easier and simpler most of the time? Yes. |
| 12 |
> |
| 13 |
|
| 14 |
Use oldconfig. Running 'oldconfig' will prompt you for any new |
| 15 |
sections/drivers that have appeared since your last kernel. Running |
| 16 |
'menuconfig' will silently accept all of the defaults for these new options. |
| 17 |
|
| 18 |
Why is it safer if only the new stuff gets defaulted? Because on more |
| 19 |
than one occasion, there has been a group of drivers, e.g. wireless |
| 20 |
chipsets, that got a new "enable anything" option. So while you may have |
| 21 |
had your Atheros chipset enabled in the old kernel, the new kernel has a |
| 22 |
"enable wireless networking" option that defaults to "no" despite the |
| 23 |
fact that your old kernel had one or more wireless chipsets enabled. |
| 24 |
|
| 25 |
This also happened with the entire SATA subsystem, resulting in at least |
| 26 |
one extra trip to the office for me. I'm not bitter, though. |
Archives