From: "Gino!" <ginolovesyou@gmail.com>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel] Re: Which Kernel?
Date: Mon, 25 Feb 2013 12:43:01 -0500 [thread overview]
Message-ID: <512BA2A5.7080703@gmail.com> (raw)
In-Reply-To: <20130225125109.2344b99e@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks for the response..
I think I will go with 3.4 release and stay there for a while.
Gino
On 02/25/2013 06:51 AM, Tom Wijsman wrote:
> On Mon, 25 Feb 2013 01:05:01 -0500
> "Gino!" <ginolovesyou@gmail.com> wrote:
>
>> So, it seems like gentoo-sources loves EOL kernels..
>
> Well, if they EOL both 3.5 and 3.6 there isn't much we can do
> about that. Although, since we're now with at least two we try to
> provide everything in 3.x. So the only thing we don't do for the moment
> is the 2.x kernels, there is one in the vanilla sources if needed.
>
>> I always move up to the latest amd64 stable, but 3.7.9 is
>> super buggy (nvidia and aufs3 complain among others)
>
> The problem here is those external drivers are not following along the
> kernel changes in a timely matter, not the other way around. If needed,
> you can find patches for them by now; there is even a patch to run
> NVIDIA on 3.8, it's just that NVIDIA takes their time to apply them.
>
>> so I'm staying at 3.6.11... although I would feel allot more
>> comfortable with something like 3.4.33!! but its at 3.4.9...
>
> What's wrong with 3.6.11 then?
>
> And yes, I'll try to check up with mpagano if it is possible to
> stabilize one or two kernels from those gaps.
>
>> Do you gentoo-sources folks recommend a particular release for Long
>> Term Stable ongoing support??? Thats the one i want to use.
>
> You've named them, if you want to go for "stable" versions you can take
> your pick between 3.4.9, 3.5.7, 3.6.11 or 3.7.9. I assume you will want
> to avoid the EOL kernels, so you might end up deciding between 3.4.9
> (where we might stabilize ~3.4.33) or 3.7.9 (for which NVIDIA and
> other external drivers will eventually work, you can patch them).
>
>
> With kind regards,
>
> Tom Wijsman (TomWij)
> Gentoo Developer
>
> E-mail address : TomWij@gentoo.org
> GPG Public Key : 6D34E57D
> GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAlEroqQACgkQ4qXYIPju5+LN/gD+L0H61ORPGVqh4guDPzVdlc4+
6U/wmLqg8EyueiL4HWMA/1tk5DT4j2/rHyxcbyB6ICrzrnLOhXfnwGqL5EpM9XY1
=Mctc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-25 17:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 6:05 [gentoo-kernel] Which Kernel? Gino!
2013-02-25 11:51 ` Tom Wijsman
2013-02-25 17:35 ` Peter Gantner (nephros)
2013-02-26 10:28 ` Marc Schiffbauer
2013-02-26 17:37 ` Peter Gantner (nephros)
2013-02-26 18:13 ` Tom Wijsman
2013-02-27 12:07 ` Marc Schiffbauer
2013-02-27 12:49 ` Tom Wijsman
2013-02-27 15:39 ` Marc Schiffbauer
2013-02-27 16:24 ` Tom Wijsman
2013-02-28 13:26 ` Marc Schiffbauer
2013-02-25 17:43 ` Gino! [this message]
2013-02-25 14:26 ` Greg KH
2013-02-25 17:27 ` [gentoo-kernel] " Gino!
2013-02-25 18:00 ` Tom Wijsman
2013-02-26 7:01 ` Thierry
2013-02-26 14:27 ` Greg KH
2013-02-26 17:45 ` Tom Wijsman
2013-02-26 19:10 ` Gino!
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=512BA2A5.7080703@gmail.com \
--to=ginolovesyou@gmail.com \
--cc=gentoo-kernel@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