1 |
Kevin O'Gorman wrote: |
2 |
> On 5/29/07, Denis <denis.che@×××××.com> wrote: |
3 |
> > I usually dread kernel updates because then I have to go |
4 |
> > through kernel menuconfig all over again, and for me, that |
5 |
> > takes some time. I guess one can reuse the old .config file, |
6 |
> > but I understand it's not always a safe thing to do. |
7 |
> |
8 |
> You can use the old .config safely if you "make oldconfig" before |
9 |
> anything else. It will prompt you for replies to any new things, |
10 |
> and quietly ditch anything it doesn't recognize. |
11 |
|
12 |
And this can ditch needed options when they get renamed or replaced, |
13 |
like happened with the netfilter stuff on the upgrade to 2.6.17, |
14 |
and with some IDE/ATA stuff on the upgrade to 2.6.20. Just running |
15 |
'make oldconfig' on a 2.6.x to 2.6.y upgrade will not always give |
16 |
you a fully working kernel. |
17 |
|
18 |
> > Is it reasonably ok to wait for every "major" 2.6.x release to |
19 |
> > update, or is it necessary to update on every minor 2.6.x.y |
20 |
> > release also? |
21 |
|
22 |
If your kernel does everything you need and you are content with its |
23 |
performance, there's no need to upgrade to a new 2.6.y. Just put a |
24 |
~sys-kernel/gentoo-sources-2.6.y into /etc/portage/package.mask and |
25 |
forget about it. But the -rn upgrades for your current version you |
26 |
normally _do want to install because they fix serious bugs. Often |
27 |
those bugs affect only specific hardware, but there's no harm in |
28 |
blindly upgrading: these little rev bumps _are safe. |
29 |
|
30 |
Benno |
31 |
-- |
32 |
gentoo-user@g.o mailing list |