Even that claim is a red herring. Internet traffic is routed through, and visible to, many many entities that I would consider equally untrustworthy, and yet no one makes a stink about that. You have to have end-to-end encryption between authenticated peers if you want to have even a chance of keeping your data out of the hands of nogoodniks.
X.org *is* X11. I think you meant XFree86 (which is also X11, by the way). That issue was political squabbling and an argument over whether or not forks are bad for open source projects. This is something entirely different.
No it won't. Contrary to popular belief, Wayland is not a panacea for poorly-written window managers or compositors (except that you won't be able to run kwin4 on it, so it'll force you to use something different and -- since kwin4 is so terrible -- likely better).
Seriously, Slashdot gets it wrong EVERY TIME. Next time, would it kill the editor to go to http://www.caltech.edu/ and, you know, read any of the words on the page?
I bought my hybrid because it's tall enough for me to sit in it comfortably, my double bass fits in the back easily, and I can drive in the carpool lane by myself. Also, it's been perfectly reliable. The fact that it costs a pittance to fill the tank is a nice bonus.
The town I grew up in had an ice cream shop run by a guy with Tourette's. He never swore, he'd just shout, "Hey!" sometimes. What I found fascinating, though, was that it would never happen while he was playing the trumpet. Somehow, concentrating on that kept the symptoms in check. Needless to say, he was a fantastic trumpet player because he practiced all the time.:)
Unlike the (what appears to be purely speculative) complaining here, modern graphics boards have thermal and voltage protection circuitry that operates independently of the software to protect the GPU from exactly this sort of situation. That's why the Blizzard report talks about a lot of "my game slowed down" complaints rather than "my GPU blew up" complaints.
They renamed the Linux Action Show to the "Computer Action Show", but it's still the same show. Is this LAS an entirely new show starting at season 11, then, or are they just renaming CAS back to LAS?
False. The advisory that claimed that was mistaken because they didn't contact NVIDIA first and confused it with an earlier X server bug (which was also remotely exploitable, thank you very much). The actual problem only existed in two beta driver releases and never existed in the legacy drivers.
Yeah, totally. I've come to the conclusion that the best programmers are the ones who delete the most code (while improving functionality, obviously). The only code that clearly has no bugs is code that doesn't exist.
It's not a flaw in X, the problem is that screens can have vastly different capabilities, e.g. one could be running at depth 24 and one at depth 8. That's not usually a problem these days, but the bigger issue is that they could also be running on vastly different drivers. For example, trying to move an OpenGL window from an NVIDIA screen to a screen running the VESA driver just plain isn't going to work.
This fundamental disconnect between screens is exactly what Xinerama is designed to fix. However, like you said, window managers often rely on windows not being able to move between screens to *implement* virtual desktops. With most implementations, they're fundamentally tied together. A window manager *could* implement virtual desktops in a way that allowed you to switch them independently, but nobody's bothered to implement it.
It does know the boundaries, that's what the Xinerama extension is for. Try running "xdpyinfo -ext XINERAMA" and it should tell you where your screen edges are.
The inability for window managers to switch workspaces on your screens independently is purely a window manager limitation and not a limitation in X itself.
Likewise, the inability for the kernel to know about your card state was purely a limitation in the X drivers and not in XFree86/X.org itself. That part is mostly fixed now (and was never a problem on NVIDIA).
--update
Connect to the NVIDIA FTP server ’ ftp://download.nvidia.com ’ and determine the lat
est available driver version. If there is a more recent driver available,
automatically download and install it. Any other options given on the commandline
will be passed on to the downloaded driver package when installing it.
Is that what those are? I saw a bazillion of them in Angels & Demons and thought they were some kind of mistake or error transferring it to film. Thanks for letting me know that the filmmakers aren't incompetent, just stupid.
CUDA and OpenCL are not exclusive, they're at different layers in the driver stack. If you look at the NVIDIA slides, you'll see that C, OpenGL, DX11 Compute, and Fortran are all just frontend languages that compile to/run on top of CUDA.
The technical restrictions of VGA mean that you can't do that without adding some sort of new extension, at which point you might as well just fire up X and use a real driver. You could maybe recognize a certain fixed set of fonts and replace those with higher-res versions, but what's the point when you can just run the card in a real graphics mode?
The point here is that the card scales the text to your display's native resolution, which every other graphics card has already done for ages.
Slashdot Mirror
The Kin and Zune HD use the original Tegra. All these new devices coming out use Tegra 2.
Even that claim is a red herring. Internet traffic is routed through, and visible to, many many entities that I would consider equally untrustworthy, and yet no one makes a stink about that. You have to have end-to-end encryption between authenticated peers if you want to have even a chance of keeping your data out of the hands of nogoodniks.
Addresses are assigned to the RIRs by the Internet Assigned Numbers Authority, NOT the Internet Corporation for Assigned Names and Numbers. I know, all of these acronyms made up of Is, As, and Ns blur together.
X.org *is* X11. I think you meant XFree86 (which is also X11, by the way). That issue was political squabbling and an argument over whether or not forks are bad for open source projects. This is something entirely different.
No it won't. Contrary to popular belief, Wayland is not a panacea for poorly-written window managers or compositors (except that you won't be able to run kwin4 on it, so it'll force you to use something different and -- since kwin4 is so terrible -- likely better).
Use the space bar (and shift+spacebar, to go backwards, at least in Chrome).
Seriously, Slashdot gets it wrong EVERY TIME. Next time, would it kill the editor to go to http://www.caltech.edu/ and, you know, read any of the words on the page?
I bought my hybrid because it's tall enough for me to sit in it comfortably, my double bass fits in the back easily, and I can drive in the carpool lane by myself. Also, it's been perfectly reliable. The fact that it costs a pittance to fill the tank is a nice bonus.
I think that predates vi. Good ol' "ed", the line editor, has s/foo/bar/g command.
I like this part:
fuckedup[0]=timer[0].totaltime;
fuckedup[1]=timer[1].totaltime;
fuckedup[2]=timer[2].totaltime;
fuckedup[3]=timer[3].totaltime;
fuckedup[4]=timer[4].totaltime;
fuckedup[5]=timer[5].totaltime;
fuckedup[6]=timer[6].totaltime;
fuckedup[7]=timer[7].totaltime;
fuckedup[8]=timer[8].totaltime;
fuckedup[9]=frame.numoflights;
fuckedup[10]=numofsounds;
fuckedup[11]=game.bonus[7];
fuckedup[12]=numofanimations;
*/
fuckedup[7]=game.levelnum;
for (count=0;count<16;count++)
{
if (fuckedup[count]<8000000)
drawtext("/i",0,128+count*12,12,1.0f,1.0f,1.0f,1.0f,fuckedup[count]);
else
drawtext("/i",0,128+count*12,12,1.0f,0.0f,0.0f,1.0f,fuckedup[count]);
}
Plus, the tagline is, "You have to *see it*, to see it."
The town I grew up in had an ice cream shop run by a guy with Tourette's. He never swore, he'd just shout, "Hey!" sometimes. What I found fascinating, though, was that it would never happen while he was playing the trumpet. Somehow, concentrating on that kept the symptoms in check. Needless to say, he was a fantastic trumpet player because he practiced all the time. :)
I wonder how he's doing now.
Unlike the (what appears to be purely speculative) complaining here, modern graphics boards have thermal and voltage protection circuitry that operates independently of the software to protect the GPU from exactly this sort of situation. That's why the Blizzard report talks about a lot of "my game slowed down" complaints rather than "my GPU blew up" complaints.
They renamed the Linux Action Show to the "Computer Action Show", but it's still the same show. Is this LAS an entirely new show starting at season 11, then, or are they just renaming CAS back to LAS?
False. The advisory that claimed that was mistaken because they didn't contact NVIDIA first and confused it with an earlier X server bug (which was also remotely exploitable, thank you very much). The actual problem only existed in two beta driver releases and never existed in the legacy drivers.
See the NVIDIA response for more details: http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=1971
Yeah, totally. I've come to the conclusion that the best programmers are the ones who delete the most code (while improving functionality, obviously). The only code that clearly has no bugs is code that doesn't exist.
It's not a flaw in X, the problem is that screens can have vastly different capabilities, e.g. one could be running at depth 24 and one at depth 8. That's not usually a problem these days, but the bigger issue is that they could also be running on vastly different drivers. For example, trying to move an OpenGL window from an NVIDIA screen to a screen running the VESA driver just plain isn't going to work.
This fundamental disconnect between screens is exactly what Xinerama is designed to fix. However, like you said, window managers often rely on windows not being able to move between screens to *implement* virtual desktops. With most implementations, they're fundamentally tied together. A window manager *could* implement virtual desktops in a way that allowed you to switch them independently, but nobody's bothered to implement it.
It does know the boundaries, that's what the Xinerama extension is for. Try running "xdpyinfo -ext XINERAMA" and it should tell you where your screen edges are.
The inability for window managers to switch workspaces on your screens independently is purely a window manager limitation and not a limitation in X itself.
Likewise, the inability for the kernel to know about your card state was purely a limitation in the X drivers and not in XFree86/X.org itself. That part is mostly fixed now (and was never a problem on NVIDIA).
The nv driver doesn't support interlace at all and the developers refuse to implement it.
Interlace support for G8x and up:
http://cgit.freedesktop.org/xorg/driver/xf86-video-nv/tree/src/g80_display.c#n434
Interlace support for pre-G80:
http://cgit.freedesktop.org/xorg/driver/xf86-video-nv/tree/src/nv_dac.c#n169
From the nvidia-installer man page:
--update
Connect to the NVIDIA FTP server ’ ftp://download.nvidia.com ’ and determine the lat
est available driver version. If there is a more recent driver available,
automatically download and install it. Any other options given on the commandline
will be passed on to the downloaded driver package when installing it.
Because, you know, that "unfamiliar environment" will kill your children and steal your wife!
Is that what those are? I saw a bazillion of them in Angels & Demons and thought they were some kind of mistake or error transferring it to film. Thanks for letting me know that the filmmakers aren't incompetent, just stupid.
CUDA and OpenCL are not exclusive, they're at different layers in the driver stack. If you look at the NVIDIA slides, you'll see that C, OpenGL, DX11 Compute, and Fortran are all just frontend languages that compile to/run on top of CUDA.
Folding@Home runs its computations in short bursts. gustgr is talking about a single computation kernel that takes more than 5-6 seconds.
The technical restrictions of VGA mean that you can't do that without adding some sort of new extension, at which point you might as well just fire up X and use a real driver. You could maybe recognize a certain fixed set of fonts and replace those with higher-res versions, but what's the point when you can just run the card in a real graphics mode?
The point here is that the card scales the text to your display's native resolution, which every other graphics card has already done for ages.