I'm sure someone will have a kernel patch to prevent this from happening in linux in very short order.
Not likely. This is valid user code that is being executed. On other CPUs, the same code wouldn't cause a problem. Something like the F00F bug is fixable in the kernel by mucking with exception handler. This is pure user-land code.
you know, it turns out that pirates were extremely smelly and extrememly homosexual. This should be obvious if you think it over -- hundred of men confined to a small space. Anyhow, when you consider that, "piracy" is the right word for slashdotters downloading warez.
While we all hate DRM, that shouldn't even be the issue. The issue: does the federal government even have the authority to regulate streaming mp3s? The answer should be pretty clear: No. The fact that it's not even questioned shows how fucked we are.
Interestingly thing.... around 50-75% of slashdot stories/links were previously on digg. When a link is "slashdotted after 3 comments", chances are it was actually still reeling from a deep digging.
businessweek confirms it -- the slashdot effect is dying.
web developers like you? You mean retards that specify font sizes and offsets in pixels? Good riddance, loser. This won't be a problem for real web devlopers. The kind that use points, percentages, and ems.
IE provides conditional html evaluation. It's a couple extra lines of html to make IE (and only IE) import a css file (or whatever). Personally, it's a lot cleaner than exploiting css parsing bugs.
Even GNU systems will differ because of differences among CPU types--for example, difference in byte ordering and alignment requirements. It is absolutely essential to handle these differences. However, don't make any effort to cater to the possibility that an int or a pointer will be other than 32 bits. We don't support 16-bit machines in GNU.
A lot of gnu (and unix) code assumed 32 bit ints, 32 bit pointers. Could have been worse... a lot of early macintosh code used 24 bit pointers with the high 8 bits being used for flags and such... going 32-bit clean was painful.
I can see them shifting from an OS vendor to "THE" application vendor as their next plan of attack. Since, at this point OSes are pretty much worthless when you consider how little distinction there is between them anymore for the average user.
That's just silly. Windows has 95% of the desktop OS market. The "average user" uses Windows 98, 2K, or XP. They make a lot of money from their Windows Tax. Do you really think they want to give up that lucrative stream of income just so an extra 5% of users might buy MS Word? (Wait, they already sell Word for Macintosh).
If they wanted their APIs on other platforms, they would probably do it via.Net/rotor -- compile once, run anywhere. Plus far fewer APIs to support.
Actually, Windows Services for Unix (STFU, oops, SFU), formerly the interix stuff, has been free for a while. It's a posix layer and includes standard utilities/headers/libraries, ksh, and even gcc.
this is the thread in question. Though the moderation history has been purged, it was moderated 851 times. (Also check out this journal entry about it).
Seriously, stop and think it over for a moment. The comment has only 2 children with a score >= 1 - 1 that was posted 14 days later (with the moderation totals), and 1 that was posted a day later and is completely unrelated to the thread.
Do you believe that normal user-moderators went through and moderated down 266 replies? Not to mention the 426 down-mods of the original comment? Then everybody that up-modded it was then knocked around in m2?
Or do you suppose there is a "bitchslap.pl" script that will moderate a comment (and all replies) to a score of -1 offtopic.
The existance of the bitchslap.pl script is well known. This is an email from CmdrTaco referring to it. This was after a user lost mod privileges by down-modding signal 11.
>"Rob 'CmdrTaco' Malda" wrote:
>Pater, this guy was another victim of the too-powerful-bitchslap
>punishing comment posters for bad moderation. Give him back his
>defaultstatus.
>
>Jeff: we were using one script to solve 2 problems: Bots autoposting
>comments to Slashdot (moderating down all comments to -1 and
>setting defaultpoints to -1) and invalid moderation (karma -1 and
>remove all moderator points).
Not likely. This is valid user code that is being executed. On other CPUs, the same code wouldn't cause a problem. Something like the F00F bug is fixable in the kernel by mucking with exception handler. This is pure user-land code.
drinkmoreovaltine
you know, it turns out that pirates were extremely smelly and extrememly homosexual. This should be obvious if you think it over -- hundred of men confined to a small space. Anyhow, when you consider that, "piracy" is the right word for slashdotters downloading warez.
While we all hate DRM, that shouldn't even be the issue. The issue: does the federal government even have the authority to regulate streaming mp3s? The answer should be pretty clear: No. The fact that it's not even questioned shows how fucked we are.
businessweek confirms it -- the slashdot effect is dying.
I can't be the only one that remembers the Slashdot PT Cruiser.
Intel started shipping desktop CPUs with virtualization technology last year. The virus doesn't need to implement the entire virtual machine.
linspire is "a shitty equivalent".
"embracing the community" is a good way to get smelly.
It would be better for Sierra if King's Quest 8 was forgotten from the game playing consiousness.
wait, an "M" rating means you should be able to interact with kids in a "meaningful way"? Are you a pedophile?
web developers like you? You mean retards that specify font sizes and offsets in pixels? Good riddance, loser. This won't be a problem for real web devlopers. The kind that use points, percentages, and ems.
IE provides conditional html evaluation. It's a couple extra lines of html to make IE (and only IE) import a css file (or whatever). Personally, it's a lot cleaner than exploiting css parsing bugs.
it was posted by Zonk. That's a pretty good indication that the article is vague and lacks a point.
for Microsoft, a WORD is 16 bits, a DWORD is 32 bits, and a QWORD is 64 bits.
it could be the fact that the preprocessor doesn't understand sizeof()
Even GNU systems will differ because of differences among CPU types--for example, difference in byte ordering and alignment requirements. It is absolutely essential to handle these differences. However, don't make any effort to cater to the possibility that an int or a pointer will be other than 32 bits. We don't support 16-bit machines in GNU.
A lot of gnu (and unix) code assumed 32 bit ints, 32 bit pointers. Could have been worse... a lot of early macintosh code used 24 bit pointers with the high 8 bits being used for flags and such... going 32-bit clean was painful.
That's just silly. Windows has 95% of the desktop OS market. The "average user" uses Windows 98, 2K, or XP. They make a lot of money from their Windows Tax. Do you really think they want to give up that lucrative stream of income just so an extra 5% of users might buy MS Word? (Wait, they already sell Word for Macintosh).
If they wanted their APIs on other platforms, they would probably do it via .Net /rotor -- compile once, run anywhere. Plus far fewer APIs to support.
Maybe they don't support classic because they're trying to kill it.
They already can choose. Kernel threads (via clone(2)) allow you to specify what (memory, files, signal handlers, etc) is cloned.
Why fork? Because you're going to exec*(2) another program. Otherwise, you'd usually be better off using a thread.
"E4"
Actually, Windows Services for Unix (STFU, oops, SFU), formerly the interix stuff, has been free for a while. It's a posix layer and includes standard utilities/headers/libraries, ksh, and even gcc.
Actually, it's Zonk's blog now. But your point is valid.
Moderation Totals: Offtopic=377, Flamebait=4, Troll=27, Redundant=5, Insightful=98, Interesting=205, Informative=49, Funny=12, Overrated=11, Underrated=63, Total=851.
Seriously, stop and think it over for a moment. The comment has only 2 children with a score >= 1 - 1 that was posted 14 days later (with the moderation totals), and 1 that was posted a day later and is completely unrelated to the thread.Do you believe that normal user-moderators went through and moderated down 266 replies? Not to mention the 426 down-mods of the original comment? Then everybody that up-modded it was then knocked around in m2?
Or do you suppose there is a "bitchslap.pl" script that will moderate a comment (and all replies) to a score of -1 offtopic.
The existance of the bitchslap.pl script is well known. This is an email from CmdrTaco referring to it. This was after a user lost mod privileges by down-modding signal 11.
>"Rob 'CmdrTaco' Malda" wrote:
>Pater, this guy was another victim of the too-powerful-bitchslap
>punishing comment posters for bad moderation. Give him back his
>defaultstatus.
>
>Jeff: we were using one script to solve 2 problems: Bots autoposting
>comments to Slashdot (moderating down all comments to -1 and
>setting defaultpoints to -1) and invalid moderation (karma -1 and
>remove all moderator points).
Hey slashdot, I hear Apple will be releasing iTunes 6.0.5 for Windows any day now!!!!