From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Any consequences to package.mask'ing newer kernels?
Date: Sat, 31 Mar 2007 09:21:22 +0100 [thread overview]
Message-ID: <20070331092122.3d47cc07@hactar.digimed.co.uk> (raw)
In-Reply-To: <20070331055510.GA29960@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
On Sat, 31 Mar 2007 01:55:10 -0400, Walter Dnes wrote:
> Partial "df" output before unmerging a bunch of kernels
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 11726996 7325372 4401624 63% /
>
>
> Partial "df" output after unmerging a bunch of kernels
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 11726996 4183616 7543380 36% /
>
> Yes folks, 3.14 gigs. Having gotten rather tired of doing this
> manually... again...
At around 300MB per kernel, that's ten excess kernels, so you can't be
doing it that often. Once you're happy with the current kernel, you only
need "emerge -P gentoo-sources" to remove the rest. I use a script that
removes all but the last two, and also cleans out /lib/modules and /boot.
> I went into /etc/portage/package.mask and added
>
> >sys-kernel/gentoo-sources-2.6.19-r5
>
> It won't hurt me now, but is there anything that might depend on newer
> kernels? It's assumed I'll upgrade when required by a security alert.
> Other than that, how long can I get away between kernel upgrades?
As long as you like, some people are still running 2.4 kernels! As long
as you don't add hardware supported only by a newer kernel, your system
will work exactly the same in six months as it does now, although you
should bear in mind that -r updates are generally problem fixes.
I usually read the Changelog when a new kernel is released and then
decide whether it's worth installing. There's no point in forcing a
reboot when the old kernel works for me.
--
Neil Bothwick
Reality is for people who can't handle Star Trek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-31 8:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 5:55 [gentoo-user] Any consequences to package.mask'ing newer kernels? Walter Dnes
2007-03-31 8:21 ` Neil Bothwick [this message]
2007-04-02 5:02 ` Walter Dnes
2007-04-02 8:37 ` Neil Bothwick
2007-03-31 10:05 ` Boyd Stephen Smith Jr.
2007-03-31 11:06 ` Hemmann, Volker Armin
2007-03-31 11:03 ` Hemmann, Volker Armin
2007-03-31 16:05 ` b.n.
2007-03-31 14:11 ` Hemmann, Volker Armin
2007-04-01 14:21 ` b.n.
2007-04-01 12:48 ` Hemmann, Volker Armin
2007-04-01 22:51 ` b.n.
2007-04-01 21:35 ` Hemmann, Volker Armin
2007-04-01 22:21 ` Neil Bothwick
2007-04-02 5:35 ` Walter Dnes
2007-04-02 8:38 ` Neil Bothwick
[not found] ` <200704130133.49396.bo.andresen@zlin.dk>
[not found] ` <20070413005947.27416382@hactar.digimed.co.uk>
2007-04-13 0:11 ` Bo Ørsted Andresen
2007-04-13 7:40 ` Neil Bothwick
2007-04-16 13:00 ` Neil Bothwick
2007-04-16 13:06 ` Bo Ørsted Andresen
2007-04-16 13:48 ` Neil Bothwick
2007-04-13 22:49 ` Anthony E. Caudel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070331092122.3d47cc07@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox