OpenBSD is on a fast track to losing its most favored secure OS status if they keep this up.
First they refused to implement WPA (despite the other BSDs having it), because it "doesn't provide real security" and "just use IPSEC".
Now they're refusing to address a weakness in their network stack (despite the other BSDs addressing it), again with the implication that everybody should just jump to IPSEC. What if you're in a situation where an IPSEC rollout is impractical or impossible?
Whatever happened to defense in depth? Whatever happened to "secure by default"? Whatever happened to constructive paranoia, such as randomizing of libc addresses, that was unlikely to have any real impact on security but was a nice extra, just in case? Why must I now upgrade to NetBSD to get security features that are lacking in OpenBSD? Isn't the shoe on the wrong foot?
What happened? Was there a change of management? Is OpenBSD under the thumb of a douchebag patch manager lately? Is this going to go away at some point? Those of us that sleep with OpenBSD firewalls like a gun under our pillow are taking notice.
So, because the system is capable of addressing up to 2^14 racks / 2^26 nodes, naturally it's going to be sold in that ridiculously huge configuration and going to "run the entire Internet"? That's like saying your 64-bit PC is going to have 16 exabytes of RAM next year and is going to store every word ever spoken by humans.
Buried as inaccurate... well... buried as inaccurate when Digg ran the same story 2 days ago.
Anonymous parent is right - the Eee is 630 MHz. It is NOT 900 MHz, even though all the press articles and even some of the retailer descriptions say this. This was a major disappointment when I bought one.
Why does anybody do the things that they do? Maybe Linus was more interested in making Linux work than in worrying about the legal issues, and didn't realize what a hardline stance the FSF would take in the years to come. As for Eric, I think making a political statement is his practicality.
Why have I released code under the GPL? Because it's for code that I'd like to have wide exposure, and I otherwise truly don't care what happens to it.
I'm glad GPL exists and I'm sure there'll always be a place for it. I'm just saying its entire raison d'être is counterculture. It's fighting the system.
Maybe if these Gamasutra authors want to keep their reputations as professionals who know what they're talking about and say things for a reason, they should think things through before posting an article.
No, actually, WAV is a container. WAV files can contain ADPCM or even MP3 compressed streams. See "compression code" under http://www.sonicspot.com/guide/wavefiles.html
"IDE sucks the life out of PC, even newer 3ghz+ pc's still pause when you put in a floppy or eject a cdrom in windows"
That's because Explorer blocks until the media is picked up and recognized, regardless of the underlying hardware. Granted, it's stupid (they really should do that in a separate thread), but it's totally not a IDE vs. SCSI issue.
How do I know? I'm using a SCSI CD-RW drive and it does exactly the same thing.
Except that almost every MP3 encoder begins by running the input through a lowpass filter, and some even hardcode this to 16KHz regardless of bitrate. So yes, MP3 compression does involve throwing out high frequencies, even if that's not the bulk of it.
My bowling instructor at State (yes, I took bowling, stop laughing) once said that we could easily build robots that could bowl. But then, what would the point be? They'd bowl a perfect game every time.
And now I have the answer to that question. We need robots that can bowl through minefields! It's all clear to me now.
Slashdot Mirror
OpenBSD is on a fast track to losing its most favored secure OS status if they keep this up.
First they refused to implement WPA (despite the other BSDs having it), because it "doesn't provide real security" and "just use IPSEC".
Now they're refusing to address a weakness in their network stack (despite the other BSDs addressing it), again with the implication that everybody should just jump to IPSEC. What if you're in a situation where an IPSEC rollout is impractical or impossible?
Whatever happened to defense in depth? Whatever happened to "secure by default"? Whatever happened to constructive paranoia, such as randomizing of libc addresses, that was unlikely to have any real impact on security but was a nice extra, just in case? Why must I now upgrade to NetBSD to get security features that are lacking in OpenBSD? Isn't the shoe on the wrong foot?
What happened? Was there a change of management? Is OpenBSD under the thumb of a douchebag patch manager lately? Is this going to go away at some point? Those of us that sleep with OpenBSD firewalls like a gun under our pillow are taking notice.
So, because the system is capable of addressing up to 2^14 racks / 2^26 nodes, naturally it's going to be sold in that ridiculously huge configuration and going to "run the entire Internet"? That's like saying your 64-bit PC is going to have 16 exabytes of RAM next year and is going to store every word ever spoken by humans.
Buried as inaccurate... well... buried as inaccurate when Digg ran the same story 2 days ago.
Spy sappin' my salary.
Anonymous parent is right - the Eee is 630 MHz. It is NOT 900 MHz, even though all the press articles and even some of the retailer descriptions say this. This was a major disappointment when I bought one.
(watch me get modded down for mentioning Dig)
I was also going to say the original Gone in 60 was the best of the above, but that would have been editorializing unnecessarily.
Why have I released code under the GPL? Because it's for code that I'd like to have wide exposure, and I otherwise truly don't care what happens to it.
I'm glad GPL exists and I'm sure there'll always be a place for it. I'm just saying its entire raison d'être is counterculture. It's fighting the system.
The sequel to The Fast and the Furious was 2 Fast 2 Furious.
The anti-DRM provisions are just the next logical step in the GPL's evolution - as a political statement.
The end result of this fiasco should just be that people disable Autoplay.
The Geforce 6800GS is available in AGP.
"Encrypted to discourage hacking?"
The question was: Will a 75dB sound cause hearing damage?
What you pasted says: If you cannot hear sounds below 75dB, then you are deaf.
But it's got fancy scientifical words like "cochlear" so I guess that means it's important, am I rite?
If you're going to be anal about Legos, at least do it right.
And of course this technology will NEVER be used for ads.
But not as cool as my 403.
No, actually, WAV is a container. WAV files can contain ADPCM or even MP3 compressed streams. See "compression code" under http://www.sonicspot.com/guide/wavefiles.html
That's because Explorer blocks until the media is picked up and recognized, regardless of the underlying hardware. Granted, it's stupid (they really should do that in a separate thread), but it's totally not a IDE vs. SCSI issue.
How do I know? I'm using a SCSI CD-RW drive and it does exactly the same thing.
2. Install OpenBSD/macppc
Next on Neill's Slashdot Comments: How to secure Linux.
Hitler.
Just trying to be helpful.
Except that almost every MP3 encoder begins by running the input through a lowpass filter, and some even hardcode this to 16KHz regardless of bitrate. So yes, MP3 compression does involve throwing out high frequencies, even if that's not the bulk of it.
And now I have the answer to that question. We need robots that can bowl through minefields! It's all clear to me now.
I had an idea to make There into an Unreal Tournament mod once, but that unfortunately never panned out.
See, you guys should just buy a Mac. We don't have this sort of problem.