From: "Gino!" <ginolovesyou@gmail.com>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel] Re: Which Kernel?
Date: Mon, 25 Feb 2013 12:27:21 -0500 [thread overview]
Message-ID: <512B9EF9.7080509@gmail.com> (raw)
In-Reply-To: <20130225142608.GA13945@kroah.com>
Firstly thanks for all your great responses...
On 02/25/2013 09:26 AM, Greg KH wrote:
> On Mon, Feb 25, 2013 at 01:05:01AM -0500, Gino! wrote:
>> So, it seems like gentoo-sources loves EOL kernels..
>> can anybody tell me why this is, it seems like that would be a bad thing...
>> I always move up to the latest amd64 stable, but 3.7.9 is super buggy
>> (nvidia and aufs3 complain among others)
>
> What is "super buggy" about 3.7.9? Have you reported this anywhere?
>
I as a stable packages only, style gentoo user have an (perhaps
unrealistic), expectation that kernels that go stable have some vetting
process with all other stable packages, and I can expect no failed
interactions between things.. this is not yet true with 3.7.9...
> Also, 3.7.y upstream is about to go end-of-life, so you really should
> move to 3.8 soon.
>
>> so I'm staying at 3.6.11...
>
> Why that one? It's been end-of-life for a while now, with known
> security issues...
>
I just happen to be here at the moment, I will probably roll back to
3.4.9, my computer is fairly new but not bleeding edge..
>> although I would feel allot more comfortable with something like
>> 3.4.33!! but its at 3.4.9...
>>
>> Do you gentoo-sources folks recommend a particular release for Long Term
>> Stable ongoing support???
>
> If you have to have something like this, then use the versions that
> upstream is saying is going to be "long term", meaning the 3.0 or 3.4
> releases. But note that new hardware will not work on these releases,
> so you will be out of luck if you have really modern hardware, sorry.
>
>> Thats the one i want to use.
>
> Why? What does something like this buy you in a rolling-release distro
> like Gentoo?
I would prefer to not constantly use new kernel implementations,
sometimes new features come out, and I may need some old package, that
depends on the older feature.. I would like for it to operate smoothly..
my most recent example of this would be changes to how wireless drivers
are implemented,
the new stuff is great but if my old packages don't work, its no good
for me.
I would like an (*slightly) older kernel that maintains security patches
and maintenance repairs for a long period of time..
I don't feel I *need any new features, what I got is great feature wise
:).. just keep it repaired and tidy! thats what I look for in a kernel.
does that answer your question?
>
> thanks,
>
> greg k-h
>
>
TA.
Gino
next prev parent reply other threads:[~2013-02-25 17:27 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 ` [gentoo-kernel] " Gino!
2013-02-25 14:26 ` [gentoo-kernel] " Greg KH
2013-02-25 17:27 ` Gino! [this message]
2013-02-25 18:00 ` [gentoo-kernel] " 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=512B9EF9.7080509@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