I'm sorry to hear of your mishap. I'd like to say, however, that as ex-vp of the users group mentioned in the article, and the guy who dealt with contacting, scheduling, and transporting ESR, he was quite professional, very personable, and gave a great talk to a distressingly small audience.
There is a chance a large object will slam into the Norteast United states. The resulting explosion and dust particles will block out the sun. Tidal waves will damage coastal property around the atlantic.
How the hell did peoples' perspectives regarding nuclear energy become so warped?
The french know what's up: Breeder Reactors are the closest things to perpetual energy machines that humans have created.
The chain reaction of splitting an isotope of plutonium (gasp! we *can't* use plutionium! oh, grow up) eventually yields the same isotope of plutonium.
Generated waste is very very small, humans get their kilowats. Stop being so damn disproportanatly scared of nuclear power.
When i first installed linux (ah, what memories) i remember being overwhelmed (in a good way). Here I had many many packages -- most of which i did not understand and many i did not use for a year or more. The title says it all _Beginning Linux Programming_ -- if you are a newbie, this book is a great asset.
A year ago I bought this book and within a month found it to be worth the price. I still have not found any reference that so clearly and succintly describes the curses/ncurses library. The philosophy of "a little bit of everything" is great -- if you want to learn more perl or tcl or... pick up an ORA book. but this book lets new users (and older users like me) know enough to find out more.
yeah, the typical slashdotter learned all this stuff long ago. and if you develop under unix, this is old hat. but for the windows users who switch over to linux, this is required reading.
It's too bad this paper got filed away instead of getting more publicity. The positive light it puts linux and GNU software could have helped a lot of projects. Imagine if linux had a few more developers at that early age -- maybe we'd be seeing some wicked bad technology in linux now (instead of meerly wicked good:> )
Then again, maybe linux was not mature enough to handle an influx of developers. Would "too many cooks" have spoiled the source code soup? ==rob
DES is solid. It's been around nearly 30 years and has proven immune to all attacks except brute-force. It's even proved strong against differential cryptanalys (for long key lengths). A 56-bit key with todays computing power is insecure. So use a 128-bit key and you data will be secure until the heat death of the universe (Scheiner, Applied Cryptography).
DES (the algorithm) is secure. There can be no argument about that -- it's 30 years old.
Slashdot Mirror
How much for a tshirt?
==rob
turn each node of your cluster into an I/O node and make use of both extra disk space and parallel I/O. It's quick, fast, and good.
There is a chance a large object will slam into the Norteast United states. The resulting explosion and dust particles will block out the sun. Tidal waves will damage coastal property around the atlantic.
How the hell did peoples' perspectives regarding nuclear energy become so warped?
The french know what's up: Breeder Reactors are the closest things to perpetual energy machines that humans have created.
The chain reaction of splitting an isotope of plutonium (gasp! we *can't* use plutionium! oh, grow up) eventually yields the same isotope of plutonium.
Generated waste is very very small, humans get their kilowats. Stop being so damn disproportanatly scared of nuclear power.
When i first installed linux (ah, what memories) i remember being overwhelmed (in a good way). Here I had many many packages -- most of which i did not understand and many i did not use for a year or more. The title says it all _Beginning Linux Programming_ -- if you are a newbie, this book is a great asset.
A year ago I bought this book and within a month found it to be worth the price. I still have not found any reference that so clearly and succintly describes the curses/ncurses library. The philosophy of "a little bit of everything" is great -- if you want to learn more perl or tcl or... pick up an ORA book. but this book lets new users (and older users like me) know enough to find out more.
yeah, the typical slashdotter learned all this stuff long ago. and if you develop under unix, this is old hat. but for the windows users who switch over to linux, this is required reading.
I've never seen such a hideous 404
It's too bad this paper got filed away instead of getting more publicity. The positive light it puts linux and GNU software could have helped a lot of projects. Imagine if linux had a few more developers at that early age -- maybe we'd be seeing some wicked bad technology in linux now (instead of meerly wicked good :> )
Then again, maybe linux was not mature enough to handle an influx of developers. Would "too many cooks" have spoiled the source code soup?
==rob
DES is solid. It's been around nearly 30 years and has proven immune to all attacks except brute-force. It's even proved strong against differential cryptanalys (for long key lengths). A 56-bit key with todays computing power is insecure. So use a 128-bit key and you data will be secure until the heat death of the universe (Scheiner, Applied Cryptography).
DES (the algorithm) is secure. There can be no argument about that -- it's 30 years old.