public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <dirk.heinrichs.ext@nsn.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] best practice for kernel mainteneance
Date: Fri, 28 Nov 2008 09:53:49 +0100	[thread overview]
Message-ID: <200811280954.00685.dirk.heinrichs.ext@nsn.com> (raw)
In-Reply-To: <492FAED3.3060704@asyr.hopto.org>

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

Am Freitag 28 November 2008 09:41:55 schrieb ext Thanasis:

> Regarding kernel maintenance, mostly from the point of view of security,
> which is the best way to go:
> 1) Having gentoo-sources in /var/lib/portage/world, which would mean the
> sources would be upgraded whenever portage marks a newer version as
> stable (provided someone follows stable)?
> 2) Not having gentoo-sources in /var/lib/portage/world, which would mean
> the sources would be upgraded only as a dependency for some other
> package (which is quite improbable/rare)?
>
> (or, I may be missing something :-) )

Yes. Having the _sources_ upgraded doesn't gain you anything. You have to 
actually compile a new kernel from them and reboot the system with that new 
kernel. Do you do this right after every kernel source update? I don't. I only 
do this when it's possible to reboot the machine.

That's the reason why I don't care kernel source upgrades via package manager 
on any system. Only when it's possible to reboot the machine, I update the 
kernel sources via git (much faster than installing a complete package), build 
the new kernel and eventually update all out-of-tree modules via 
portage/paludis beforehand.

HTH...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-11-28  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28  8:41 [gentoo-user] best practice for kernel mainteneance Thanasis
2008-11-28  8:53 ` Dirk Heinrichs [this message]
2008-11-28 12:47   ` Thanasis
2008-11-28 13:22     ` Dirk Heinrichs
2008-11-28  9:54 ` Alan McKinnon
2008-11-28 12:48   ` Thanasis
2008-11-28 13:25     ` Dirk Heinrichs
2008-11-28 17:59     ` [gentoo-user] " Nikos Chantziaras
2008-11-28 18:57       ` [gentoo-user] Re: best practice for kernel maintenance Thanasis
2008-11-28 19:27         ` Nikos Chantziaras
2008-11-28 19:47           ` Thanasis
2008-11-28 10:31 ` [gentoo-user] best practice for kernel mainteneance Jorge Peixoto de Morais Neto
2008-11-28 12:46   ` Thanasis
2008-11-28 11:19 ` Dale
2008-11-28 12:47   ` [gentoo-user] best practice for kernel maintenance Thanasis

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=200811280954.00685.dirk.heinrichs.ext@nsn.com \
    --to=dirk.heinrichs.ext@nsn.com \
    --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