Not entirely true... There are two purposes for advertising: Make people want to buy the product, and make people *aware* of the product. You're correct about the former, but the latter isn't exactly chopped liver, and is far less malicious.
The usual response to someone loudly complianing about a missing feature in a free software package or lack of free equivalent to a commercial feature...
If a redhat ISO is 650MB, then BitTorrent will have to move 10^14 MB (10^17 bytes, or 100 quadrobytes, two orders of magnitude more than the number quoted for Kazaa in the other thread) to be spared.
There are few ways you could _accidently_ end up in a situation where your code is in violation of the GPL (i.e. a situation where you are required to release your code under the GPL or remove GPLd parts of it).
The problem is that this is exactly what has happened. Someone pointed out that the circumstances under which code release was required were different than previously understood. The meaning of the LGPL has been changed, and that means the license in every LGPLed package everywhere requires that the user adhere to different rules, and it now is indeed possible to end up in a situation where the LGPL dictates that your own code be released even if you have diligently followed proper usage until this point.
If the potential profit of a space program outweighed the cost of investment, the companies would be champing at the bit. There just hasn't been enough space experience to find something guaranteed to be exploitable. Chicken and egg.
There were tons of paintings, sonnets, Old English epics, symphonies, plays, statues, and so on that were just as awful as any of the movies you mentioned. We've just forgotten about them.
I think MacOS has something a little bit similar with disk mountable images (.dmg) files, but the MacOS filing system is rather poor, and I don't know how easy it is for users to create them.
It's *very* easy to create a disk image. Drag a folder onto the Disk Copy app and select a destination to store the image. There's no step 3!
One fairly important point that the article didn't mention: There are now *two* open-source browsers/HTML libraries being backed by major industry players.
In this particular case the developers really *did* clearly express their dislike for the bug (and well before this particular post). It was very nearly removed from Quake 3 and was only kept due to demands from the players.
The line between tactics and cheats/"lameness" has always been hazy (Camping? Flag camping? Spawn camping? AWP usage? Onscreen timers? Carpetbombing in Myth? Being an LPB before residential broadband? Grenade spamming? Stuffing tanks in the cave?), but I can't think of a clearer way to resolve disputes than to ask the original authors. They had the idea and (in theory) understand the game as a whole better than anyone. If you have a better idea as to how the game should work, make a mod. (I also can't think of any *other* examples of bugs/quirks that matured into recognized skills instead of being immediately patched out upon discovery.)
Yes, if, like I said, and like Zoid said, it was contrary to the developer's intentions. There's no difference between altered physical performance and "real" bugs that get you called a cheater for using them.
It is simply a bug in the physics, a divergence in game behavior from the developer's intentions. It may take practice to do it well, but it takes even more skill (in a different field) to write an aimbot, and I don't think anyone would argue that writer is a better Quake player than someone using only his reflexes. Bunnyhopping should have been removed as soon as it was discovered.
Wal-Mart could easily pressure its suppliers into inserting the RFID tags before they get to the warehouse. That's how bar codes took off in the first place.
How about doing it in a public place, and letting the populace watch you face the (theoretically unjust) consequences of your actions? That's how protest/civil disobedience is *supposed* to work.
Normally, a buffer overflow overwrites random data in the heap, which is where the program keeps the data it is processing, which does indeed cause the app to crash most of the time because the garbage from the buffer leaves the heap in an inconsistent state which the program cannot handle. The way a buffer overflow attack works is by putting in the proper amount of excess data to overwrite the stack, which is the data regarding the program's own execution. The stack is overwritten with precisely designed data that form a pointer into the new data that got dumped into memory by the faulty buffer code, so it jumps to the new data and attempts to execute it. If this is legal machine code, it will successfully run and perform whatever task the attacker would like it to do. And, yes, once the new code has finished executing, the app will run off the new valid machine code, encounter some real garbage, and crash, but the system has already been compromised (it can only take a few function calls to create a backdoor which the attacker can activate later).
You can't "give 1 CPU the entire 1Ghz bus bandwidth". The two CPUs have independent 1Ghz connections to the system controller. They only share the 400Mhz RAM bus and the rest of the system devices.
Slashdot Mirror
Heh... this Macworld sucked compared to the last few years.
Not entirely true... There are two purposes for advertising: Make people want to buy the product, and make people *aware* of the product. You're correct about the former, but the latter isn't exactly chopped liver, and is far less malicious.
The usual response to someone loudly complianing about a missing feature in a free software package or lack of free equivalent to a commercial feature...
WRITE IT YOURSELF.
If a redhat ISO is 650MB, then BitTorrent will have to move 10^14 MB (10^17 bytes, or 100 quadrobytes, two orders of magnitude more than the number quoted for Kazaa in the other thread) to be spared.
If the potential profit of a space program outweighed the cost of investment, the companies would be champing at the bit. There just hasn't been enough space experience to find something guaranteed to be exploitable. Chicken and egg.
There were tons of paintings, sonnets, Old English epics, symphonies, plays, statues, and so on that were just as awful as any of the movies you mentioned. We've just forgotten about them.
One fairly important point that the article didn't mention: There are now *two* open-source browsers/HTML libraries being backed by major industry players.
You can't deny that this is the trend. The bubble-powered free ride is over.
Well, there's the iTunes Music Store...
OK, center of solar system. Same diff.
It took thousands of years for the evidence the Earth not the center of the Universe to even be recognized as such, let alone used to prove the fact.
In this particular case the developers really *did* clearly express their dislike for the bug (and well before this particular post). It was very nearly removed from Quake 3 and was only kept due to demands from the players.
The line between tactics and cheats/"lameness" has always been hazy (Camping? Flag camping? Spawn camping? AWP usage? Onscreen timers? Carpetbombing in Myth? Being an LPB before residential broadband? Grenade spamming? Stuffing tanks in the cave?), but I can't think of a clearer way to resolve disputes than to ask the original authors. They had the idea and (in theory) understand the game as a whole better than anyone. If you have a better idea as to how the game should work, make a mod. (I also can't think of any *other* examples of bugs/quirks that matured into recognized skills instead of being immediately patched out upon discovery.)
Yes, if, like I said, and like Zoid said, it was contrary to the developer's intentions. There's no difference between altered physical performance and "real" bugs that get you called a cheater for using them.
It is simply a bug in the physics, a divergence in game behavior from the developer's intentions. It may take practice to do it well, but it takes even more skill (in a different field) to write an aimbot, and I don't think anyone would argue that writer is a better Quake player than someone using only his reflexes. Bunnyhopping should have been removed as soon as it was discovered.
Should have just dug his grave 12 feet deep then.
Wal-Mart could easily pressure its suppliers into inserting the RFID tags before they get to the warehouse. That's how bar codes took off in the first place.
Yes, trucks that are moving at very high speed directly towards brick walls and/or sheer cliffs.
Try doing heroin for a month, stopping for a month, and then making that post again.
How about doing it in a public place, and letting the populace watch you face the (theoretically unjust) consequences of your actions? That's how protest/civil disobedience is *supposed* to work.
Normally, a buffer overflow overwrites random data in the heap, which is where the program keeps the data it is processing, which does indeed cause the app to crash most of the time because the garbage from the buffer leaves the heap in an inconsistent state which the program cannot handle. The way a buffer overflow attack works is by putting in the proper amount of excess data to overwrite the stack, which is the data regarding the program's own execution. The stack is overwritten with precisely designed data that form a pointer into the new data that got dumped into memory by the faulty buffer code, so it jumps to the new data and attempts to execute it. If this is legal machine code, it will successfully run and perform whatever task the attacker would like it to do. And, yes, once the new code has finished executing, the app will run off the new valid machine code, encounter some real garbage, and crash, but the system has already been compromised (it can only take a few function calls to create a backdoor which the attacker can activate later).
That's not such a rare case - It happens on every memory access when running programs in more than 4G of address space.
You can't "give 1 CPU the entire 1Ghz bus bandwidth". The two CPUs have independent 1Ghz connections to the system controller. They only share the 400Mhz RAM bus and the rest of the system devices.