1 |
On Sat, 31 Mar 2007 01:55:10 -0400, Walter Dnes wrote: |
2 |
|
3 |
> Partial "df" output before unmerging a bunch of kernels |
4 |
> Filesystem 1K-blocks Used Available Use% Mounted on |
5 |
> /dev/sda1 11726996 7325372 4401624 63% / |
6 |
> |
7 |
> |
8 |
> Partial "df" output after unmerging a bunch of kernels |
9 |
> Filesystem 1K-blocks Used Available Use% Mounted on |
10 |
> /dev/sda1 11726996 4183616 7543380 36% / |
11 |
> |
12 |
> Yes folks, 3.14 gigs. Having gotten rather tired of doing this |
13 |
> manually... again... |
14 |
|
15 |
At around 300MB per kernel, that's ten excess kernels, so you can't be |
16 |
doing it that often. Once you're happy with the current kernel, you only |
17 |
need "emerge -P gentoo-sources" to remove the rest. I use a script that |
18 |
removes all but the last two, and also cleans out /lib/modules and /boot. |
19 |
|
20 |
> I went into /etc/portage/package.mask and added |
21 |
> |
22 |
> >sys-kernel/gentoo-sources-2.6.19-r5 |
23 |
> |
24 |
> It won't hurt me now, but is there anything that might depend on newer |
25 |
> kernels? It's assumed I'll upgrade when required by a security alert. |
26 |
> Other than that, how long can I get away between kernel upgrades? |
27 |
|
28 |
As long as you like, some people are still running 2.4 kernels! As long |
29 |
as you don't add hardware supported only by a newer kernel, your system |
30 |
will work exactly the same in six months as it does now, although you |
31 |
should bear in mind that -r updates are generally problem fixes. |
32 |
|
33 |
I usually read the Changelog when a new kernel is released and then |
34 |
decide whether it's worth installing. There's no point in forcing a |
35 |
reboot when the old kernel works for me. |
36 |
|
37 |
|
38 |
-- |
39 |
Neil Bothwick |
40 |
|
41 |
Reality is for people who can't handle Star Trek |