So Linux is hopelessly broken because of some random people making noise about their possibly misconfigured or broken hardware on their possibly hacked kernel on LKML? Give me a break, troll.
A) Contrary to his "first level" of harm: proprietary software has vastly outcompeted open software despite its barriers.
Outcompeted in what way? Market share? Free software has a lower cost to the end user. Install base? Don't you think the install base of free software would be higher if the largest proprietary software vendor were not a convicted monopolist? Or are you referring to quality or performance? I don't buy your argument that free software is not competitive with proprietary software.
And now you get to provide a link to any documentation about this alleged lawsuit, or alternatively you can explain the existence of NVIDIA's prior obfuscated open source GLX driver released circa 1999.
If you are detained by an officer, he cannot search your persons without probable cause.
Wrong. The officer can search you for whatever reason he wants to. The evidence is only admissible in court if he establishes probable cause. But until you file a motion to suppress, the evidence is admitted by default. So maybe this knowledge might save you if you are the subject of some huge bust, but most of the time it's a choice between paying a fine or paying a lawyer. (Usually you pay the lawyer more, but it's nice to be able to find gainful employment later on.)
For example take a look at the nvidia driver. Since a year, there's a reverse-engineering project to create a free dri-driver for nvidia, but it's not advancing at all. I guess lack of developer interest, because there's already the proprietary driver.
Sorry, but you're nuts if you think this isn't progress! They have even been merged into Mesa/DRM!
... and all that is included is a Linux 2.6.16.27 upstream tarball and not the so-called "Killer Mods" to the kernel. They don't even include the config they used to build the kernel. IOW, useless for hosting your own OS on the KillerNIC.
Actually, this could be a nifty product. It's a 400MHz SoC processor with 64MB and USB, running Linux.
There is currently a closed beta for open source Linux drivers.
The big question is, where is the GPL source code for the embedded Linux system? With it, this card could be turned into a lot of things, especially when the price drops.
No matter how you cut it, these goods and services have a value set by the vendor
No! The price is set by the vendor. The value is set by the market. The vendor assuming that they can set the value by setting the price is the problem - this is artificial scarcity. People see that the price set by the RIAA cartel does not match the value and seek an alternate supply.
You are aware that the Java trademark prevents third party distributions from being referred to as Java, are you not? If someone hacks features into the language, they can't legally call it Java. Simple as that.
I didn't say that, just that he couldn't blame piracy on devs making bad games. But yes, the fact that people will not actually, you know, give you money for making the game will have a significant effect.
Please explain to me the difference, from the perspective of the developer's marketing strategy, of me not buying a game because I'm not confident that it won't suck, and me pirating a game, eventually determining that it sucks, and deleting it a few days later.
Spinlocking to wait on a vsync would be silly given that most hardware has the ability to generate a vertical retrace interrupt. Are you sure this is actually the problem?
Obviously, you've not a clue what you're talking about. The NDA applies to the documentation, not the developed driver. The current S3 and ATI drivers only exist because of NDA programs.
Sorry, that's bullshit. NDAs are not, and never have been, the problem. The problem is hardware that is impossible to get documentation for at ALL, such as any R300 or above chip from ATI, or any NVIDIA hardware. The vast majority of open source graphics drivers were developed under NDA!
Capitalized on a Mainstream Platform: The SNES featured a slower more processor that was more tailored for games, while the 6800 on the Genesis was a more general-purpose and well known platform
The 65816 (a 16-bit kludge of the 6502) in the SNES was *not* more tailored for games, and was probably the most inferior component of the SNES. The SNES had better sprite graphics hardware (with cool effects like scaling) and better sound hardware (most games implemented something similar to MIDI synthesizer with soft samples, but it was a completely programmable subsystem). The Genesis on the other hand had a superior 32-bit 68000 CPU, but weak graphics hardware and an FM synthesizer that was pathetic in comparison (but in line with arcade hardware of the time). Graphics and sound, along with solid 1st-party franchises, are the most appealing part of video games to consumers, so the SNES won.
Sure there is. There's just not a consistent ABI, and that's on purpose.
What in the world are you talking about? The Linux ABI is EMINENTLY stable, and *that* is on purpose. See Documentation/ABI. Application binaries compiled for Linux 1.x still run today, that is a testament to its ABI stability like no other.
Even ISA-PNP devices are handled like this. No, there is no such thing as the Win95 "Add New Hardware" scan, and for good reason - it is an unreliable way to detect hardware and can also crash the system or corrupt data. So yes, if you have a non-PNP ISA device, or serial device, or some other device that does not provide the system with a way to passively observe its presence and resource requirements without requiring the system to know how to access it, then you are out of luck with respect to automatic module loading. Fortunately, such hardware is usually quite obsolete by now.
Slashdot Mirror
CDs don't work in the arcade hardware.
So Linux is hopelessly broken because of some random people making noise about their possibly misconfigured or broken hardware on their possibly hacked kernel on LKML? Give me a break, troll.
If the driver is broken and nobody wants to maintain it, it should be marked obsolete or simply removed.
Yes, you are missing something, since you are obviously not following the developer blog: 8 8
And now you get to provide a link to any documentation about this alleged lawsuit, or alternatively you can explain the existence of NVIDIA's prior obfuscated open source GLX driver released circa 1999.
I love the slashdot tags on this article.
"Do they even have a legal right to do so?"
> haha, no, eff, microsoft (tagging beta)
Read it phonetically.
Sorry, but you're nuts if you think this isn't progress! They have even been merged into Mesa/DRM!
... and all that is included is a Linux 2.6.16.27 upstream tarball and not the so-called "Killer Mods" to the kernel. They don't even include the config they used to build the kernel. IOW, useless for hosting your own OS on the KillerNIC.
"Suicides typically make up 56.5% of all gun deaths according to the Bureau Of Justice Statistics. In fact, drugs and suicides account for more than 2 out of every 3 gun deaths in the USA."
Aha: http://www.killernic.com/killer/fna.zip
There is currently a closed beta for open source Linux drivers.
The big question is, where is the GPL source code for the embedded Linux system? With it, this card could be turned into a lot of things, especially when the price drops.
x86's local jump is two bytes long. One byte for the prefix (74/75 for conditional, EB for unconditional) and one byte for the offset.
LinuxBIOS is not compatible with legacy DOS-based PC operating systems and the GPL does not allow for proprietary extensions.
You are aware that the Java trademark prevents third party distributions from being referred to as Java, are you not? If someone hacks features into the language, they can't legally call it Java. Simple as that.
Please explain to me the difference, from the perspective of the developer's marketing strategy, of me not buying a game because I'm not confident that it won't suck, and me pirating a game, eventually determining that it sucks, and deleting it a few days later.
Spinlocking to wait on a vsync would be silly given that most hardware has the ability to generate a vertical retrace interrupt. Are you sure this is actually the problem?
Obviously, you've not a clue what you're talking about. The NDA applies to the documentation, not the developed driver. The current S3 and ATI drivers only exist because of NDA programs.
Sorry, that's bullshit. NDAs are not, and never have been, the problem. The problem is hardware that is impossible to get documentation for at ALL, such as any R300 or above chip from ATI, or any NVIDIA hardware. The vast majority of open source graphics drivers were developed under NDA!
Even ISA-PNP devices are handled like this. No, there is no such thing as the Win95 "Add New Hardware" scan, and for good reason - it is an unreliable way to detect hardware and can also crash the system or corrupt data. So yes, if you have a non-PNP ISA device, or serial device, or some other device that does not provide the system with a way to passively observe its presence and resource requirements without requiring the system to know how to access it, then you are out of luck with respect to automatic module loading. Fortunately, such hardware is usually quite obsolete by now.