1 |
Hi! |
2 |
|
3 |
On Sat, Nov 12, 2011 at 02:37:40PM -0600, Matt Thode wrote: |
4 |
> > May I ask if nvidia is still hardend unfriendly? I need CUDA available. |
5 |
> nvidia drivers still don't play well yet. |
6 |
> |
7 |
> There are ways to get it working (some people have) but I don't know what exactly they did (I know they paxmarked everything nvidia touches (I think -m). |
8 |
|
9 |
Actually it sounds much worse than it is. Usually it's enough to paxctl -m |
10 |
only few binaries: Xorg, mplayer and vmware-vmx. |
11 |
|
12 |
I'm using CUDA only for "flacuda" encoder, which is .NET's .exe executed by |
13 |
dev-lang/mono (which is already paxmarked by default). |
14 |
|
15 |
On my hardened/nvidia workstation there are several other binaries needs -m, |
16 |
but this probably have nothing with nvidia/CUDA: air-sdk, amarok, firefox. |
17 |
|
18 |
|
19 |
P.S. I'm pretty sure it's much better to have full-featured (including |
20 |
accelerated 3D and CUDA) hardened workstation with partially relaxed |
21 |
protection on some binaries, than full-featured non-hardened workstation |
22 |
or hardened workstation without these (important for workstation) features. |
23 |
|
24 |
And I don't understood why you didn't add few paxmarking commands into |
25 |
several ebuilds and just say nvidia on hardened is supported out of box... |
26 |
instead of pretending there are some unknown critical issues with nvidia |
27 |
on hardened. I don't know, maybe there are some applications which are |
28 |
really have some issues, but I'm running more or less usual hardened |
29 |
workstation with nvidia for years without any issues except needs in few |
30 |
paxmarking mentioned above. |
31 |
|
32 |
-- |
33 |
WBR, Alex. |