public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "b.n." <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Any consequences to package.mask'ing newer kernels?
Date: Sun, 01 Apr 2007 22:51:34 +0000	[thread overview]
Message-ID: <46103776.9010700@gmail.com> (raw)
In-Reply-To: <200704011448.18361.volker.armin.hemmann@tu-clausthal.de>

Hemmann, Volker Armin ha scritto:
> On Sonntag, 1. April 2007, b.n. wrote:
>> Hemmann, Volker Armin ha scritto:
>>> In almost every kernel release a security problem is found, that is fixed
>>> in a stable release.
>> Stable release? AFAIK, *all* 2.6.x releases are stable releases.
> 
> No, they aren't. There are the 'normal' releases (for example 2.6.20) and 
> the 'stable' releases which fix important bugs and security holes (like, for 
> example 2.6.20.2).

Yes, I know that. I didn't call them "unstable" and "stable", that's why 
I was confused, however I know.
Now my questions are:
1)I only see gentoo-sources-2.6.X-rY, I never see 
gentoo-sources-2.6.X.a.b-rY .What am I installing when I install 
gentoo-sources-2.6.x-rY?

2)How do the binary distribution people cope with this?

>> The 
>> days of double trees (2.4.x and 2.5.x) are gone.
> 
> Today we have at least 4 trees.
> Linus.
> Morton.
> The 'stable releases' (2.6.XY.Z)
> Bunk's 2.6.16.XY

Well, there have ALWAYS been a lot of different trees, but Morton, for 
example, AFAIK is not an "official" tree (although it is maintained 
closely to the official).

However that's just nitpicking. :)

>>> Which risk? Which mess? There is not a risk, if you use oldconfig.
>> oldconfig doesn't always work well between major releases (2.6.x vs
>> 2.6.x+1).
>>
> I works like a charm for me....

Not for me. And I've sometimes read of newer kernels breaking things on 
the gentoo mailing list. Upgrading a kernel is never straightforward, 
imho (maybe it's me being unexperienced, however it's my years-old only 
desktop box and I hate to b0rk it).

m.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-04-01 20:50 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
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. [this message]
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=46103776.9010700@gmail.com \
    --to=brullonulla@gmail.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