Don't like glibc? Run FreeBSD. Compare the size of glibc to the size of the BSD libc. Not even in the same ballpark.
For a FreeBSD developer to introduce non-backwards compatible changes is a cardinal sin. I doubt you would find more than a handful -- if any -- of instances where you needed both the old and new C libraries for any reason other than old apps linked against the old lib.
This is the kind of thinking you get when the kernel, libs, and userland tools are all reviewed by the same people. With FSF, each project is doing their own thing and breaking each other's software. NOT GOOD.
You really need to read the papers on the attacks. 128-bit encrpytion and 56-bit encryption are both just as susceptible to attacking. MAC addresses are NOT encrypted IIRC and I can steal one of those when your client is down. One potential attack is to send a packet of known content from the Internet TO your network. Then I grab the encrypted packet, and I can XOR out a piece of the cipher stream and (because the way this 802.11b works) I am able to identify future packets that use this piece of the stream and decrpyt them. Other statistical attacks allow me to, over time, build up a database that will allow me to decrypt everything on your network. The more traffic you send, the faster this happens.
Knowing what I know, I would treat every wireless network as if ALL the traffic was being transmitted over a hostile network.
I read a few of the whitepapers on the subject, and the attack is so simple that someone who has no more knowledge than what is in Applied Cryptography understands perfectly what the attack is and how it works. If I knew more about writing drivers for wavelan cards, I could easily whip out some software for attacking any 802.11b network.
I have to agree on this. If Napster can raise $1B with 1.67/user, they are obviously going to want a piece for themselves -- which the RIAA sees as theirs. If napster makes a billion as well, then (in my best de niro voice) the record companies don't see it as making a billion but LOSING a billion.
They want total end-to-end control of the distribution and use of the content.
Actually, someone should create a napster "proxy" that will make queries on your behalf. Since a connection TO napster is not necessary to exchange files, you can still trade for free.
The SDMI/DRM requirements will be what "kills" napster
Linux will never be better than FreeBSD because it lacks refinement. Every single release sees practically every subsystem rewritten. It's always back to the drawing board because no one actually spends enough time AT THE DRAWING BOARD. Three firewall interfaces in as many kernel releases? 2 SCSI systems? Rewritten VM nearly every time? TCP stack rewritten more times than I can count? I don't know WHICH fucking filesystem to use.
Slashdot Mirror
Don't like glibc? Run FreeBSD. Compare the size of glibc to the size of the BSD libc. Not even in the same ballpark.
For a FreeBSD developer to introduce non-backwards compatible changes is a cardinal sin. I doubt you would find more than a handful -- if any -- of instances where you needed both the old and new C libraries for any reason other than old apps linked against the old lib.
This is the kind of thinking you get when the kernel, libs, and userland tools are all reviewed by the same people. With FSF, each project is doing their own thing and breaking each other's software. NOT GOOD.
You really need to read the papers on the attacks. 128-bit encrpytion and 56-bit encryption are both just as susceptible to attacking. MAC addresses are NOT encrypted IIRC and I can steal one of those when your client is down. One potential attack is to send a packet of known content from the Internet TO your network. Then I grab the encrypted packet, and I can XOR out a piece of the cipher stream and (because the way this 802.11b works) I am able to identify future packets that use this piece of the stream and decrpyt them. Other statistical attacks allow me to, over time, build up a database that will allow me to decrypt everything on your network. The more traffic you send, the faster this happens. Knowing what I know, I would treat every wireless network as if ALL the traffic was being transmitted over a hostile network.
I read a few of the whitepapers on the subject, and the attack is so simple that someone who has no more knowledge than what is in Applied Cryptography understands perfectly what the attack is and how it works. If I knew more about writing drivers for wavelan cards, I could easily whip out some software for attacking any 802.11b network.
from a country that has banned guns.
I have to agree on this. If Napster can raise $1B with 1.67/user, they are obviously going to want a piece for themselves -- which the RIAA sees as theirs. If napster makes a billion as well, then (in my best de niro voice) the record companies don't see it as making a billion but LOSING a billion.
They want total end-to-end control of the distribution and use of the content.
I think the 'make world' he is referring to is the BSD 'make world'. Quite the benchmark if you ask me.
Actually, someone should create a napster "proxy" that will make queries on your behalf. Since a connection TO napster is not necessary to exchange files, you can still trade for free. The SDMI/DRM requirements will be what "kills" napster
Linux will never be better than FreeBSD because it lacks refinement. Every single release sees practically every subsystem rewritten. It's always back to the drawing board because no one actually spends enough time AT THE DRAWING BOARD. Three firewall interfaces in as many kernel releases? 2 SCSI systems? Rewritten VM nearly every time? TCP stack rewritten more times than I can count? I don't know WHICH fucking filesystem to use.