From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
Date: Thu, 22 Mar 2012 16:18:58 -0500 [thread overview]
Message-ID: <20120322211857.GA25467@crud> (raw)
In-Reply-To: <CAK2H+efpFzTvjWOaBajkw-a3MxK3P9syqCNsySVWvHP6D5dHJQ@mail.gmail.com>
Mark Knecht <markknecht@gmail.com> skribis:
> Anyway, I don't much know what the Gentoo devs do to patch
> gentoo-sources. I've gone back and forth between the two at different
> times. One reason to stick with gentoo-sources is that vanilla-sources
> (and presumably source directly from kernel.org) isn't supported by
> Gentoo Security. Not sure how important that is to an individual
> though.
I have found gentoo-sources utterly unreliable and finally settled on
using only vanilla sources, using the ebuild for convenience. The
Gentoo Security warning means essentially nothing to me; it’s not as
if the kernel project is out there purposely creating backdoors that
we can depend on Gentoo to nail shut.
(I’ve recently migrated my system from ~amd64 to amd64 -- yes, it can
be done -- but am still running 3.2.7 rather than the stable
3.2.2. Nevertheless I had to mask the latest ‘stable’ nvidia-drivers;
it made gkrellm crash. In the process of fixing that problem, I
noticed that OpenCL is around as a more generic alternative to CUDA,
so maybe use of that will pick up.)
next prev parent reply other threads:[~2012-03-23 0:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:12 [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Frank Peters
2012-03-19 16:35 ` Mark Knecht
2012-03-19 19:05 ` Frank Peters
2012-03-19 19:16 ` Mark Knecht
2012-03-19 19:30 ` Frank Peters
2012-03-19 20:08 ` Mark Knecht
2012-03-19 20:25 ` Paul Hartman
2012-03-19 19:14 ` Cheng Renquan
2012-03-19 19:17 ` Mark Knecht
2012-03-19 21:28 ` Barry Schwartz
2012-03-19 21:40 ` Mark Knecht
2012-03-20 0:34 ` Barry Schwartz
2012-03-20 4:03 ` Frank Peters
2012-03-20 6:20 ` Barry Schwartz
2012-03-20 18:31 ` [gentoo-amd64] " Duncan
2012-03-20 18:27 ` Duncan
2012-03-22 16:03 ` [gentoo-amd64] " Mark Knecht
2012-03-22 18:41 ` Frank Peters
2012-03-22 18:58 ` Mark Knecht
2012-03-22 21:18 ` Barry Schwartz [this message]
2012-03-22 21:21 ` Barry Schwartz
2012-03-22 21:32 ` Outside of portage (was Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers) Barry Schwartz
2012-03-22 23:04 ` Paul Hartman
2012-03-22 23:28 ` Barry Schwartz
2012-03-22 23:33 ` Harry Holt
2012-03-23 8:42 ` Benny Pedersen
2012-03-23 13:50 ` Harry Holt
2012-03-23 0:14 ` Gary E. Miller
2012-03-23 1:30 ` Mark Knecht
2012-03-23 1:56 ` Barry Schwartz
2012-03-23 4:05 ` [gentoo-amd64] Re: Outside of portage (was " Duncan
2012-03-23 12:41 ` Outside of portage (was Re: [gentoo-amd64] " Frank Peters
2012-03-23 15:49 ` Barry Schwartz
2012-03-23 18:09 ` Dale
2012-03-23 18:28 ` [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Mark Knecht
2012-03-23 19:11 ` Mark Knecht
2012-03-24 0:20 ` Frank Peters
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=20120322211857.GA25467@crud \
--to=chemoelectric@chemoelectric.org \
--cc=gentoo-amd64@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