Looks like more and more projects are capitalising on "free speech."
Personally, I have made lots of money selling and installing modified/original BSD software, and donated a considerable amount of that back to those projects.
The GPL prevents me from doing this, because I don't necessarily want to release the source code to the changes which I have invested in. And I certainly don't want to release my code under the GPL.
This 'ransom' thing prevents people like me from donating to the project at all. Ironic, really.
*shrug* I took your "but that wouldn't be too hard" as being the whole process, not just the stripping out the tcp header, which is sufficiently trivial to not require a statement like that.
Your post came off as being rather pretentious, a convoluted approach to something which could be much more easily solved by changing only the port, to 53.
Games may not use 128MB of texture memory (or they may), but video memory is used by other stuff too.
There are colour, depth, stencil, alpha buffers (probably others.) Another big thing is vertex information. A static model can be loaded into video memory. Newer cards support programs (shaders) which are executed on the GPU. All this could add up.
RAM is cheap enough that adding more has a minimal effect on price, but could be useful for various things (even down the road.)
I vaguely recall some hack which let you use your video memory as a swap device. That's nice for a system which is only used as a gaming machine part of the time.
Slashdot Mirror
Looks like more and more projects are capitalising on "free speech."
Personally, I have made lots of money selling and installing modified/original BSD software, and donated a considerable amount of that back to those projects.
The GPL prevents me from doing this, because I don't necessarily want to release the source code to the changes which I have invested in. And I certainly don't want to release my code under the GPL.
This 'ransom' thing prevents people like me from donating to the project at all. Ironic, really.
Of course it won't make a CPU faster. However, better scheduling and memory management results in less time being spent elsewhere.
sh
Their little icons are really nice. Somebody should make them into Mac OS X icons.
sh
I'm not sure if you're being sarcastic.
"I think you've got it confused with xor, which
means either this or that but not both."
XOR is also false when neither operand is true. I wasn't correcting you, just clarifying for any readers who may be thrown off.
sh
Or neither.
sh
*shrug* I took your "but that wouldn't be too hard" as being the whole process, not just the stripping out the tcp header, which is sufficiently trivial to not require a statement like that.
Your post came off as being rather pretentious, a convoluted approach to something which could be much more easily solved by changing only the port, to 53.
sh
This guy hasn't got a clue what he's talking about. The receiving OS would throw this packet away and send an ICMP error back, raw sockets or none.
sh
Games may not use 128MB of texture memory (or they may), but video memory is used by other stuff too.
There are colour, depth, stencil, alpha buffers (probably others.) Another big thing is vertex information. A static model can be loaded into video memory. Newer cards support programs (shaders) which are executed on the GPU. All this could add up.
RAM is cheap enough that adding more has a minimal effect on price, but could be useful for various things (even down the road.)
I vaguely recall some hack which let you use your video memory as a swap device. That's nice for a system which is only used as a gaming machine part of the time.
sh