"...And thank God I'm only watching the game -- controlling it --
I don't see you guys rating
The kind of mate I'm contemplating
I'd let you watch, I would invite you
But the queens we use would not excite you." .
--Murray Head, "One Night In Bangkok"
.
I am betting that the "1000 rewrites" figure came out of a lab, in which the disc was never removed from the drive - and so never collected "normal" dust and/or scratches.
Plus, that disc was one of the "originals" that were probably a little bit over-engineered - and probably burned at LOW LOW speed, (1-2x) to boot.
CDRs and RW's have become a commodity item, made as cheaply as possible, and for the most part insufficiently tested as far as projected lifetime goes, especially when burned at higher speeds.
MHO, more testing needs to be done with modern equipment before "1000 rewrites" gets taken for the "average" lifetime expectancy again. Tom's Hardware, anyone? .
Sure you can make an IDE RAID setup, but with most manufacturers going with a 1-year warranty how long do you expect an "average" single IDE drive to last? .
--I like SCSI as well - IDE limits you to four devices (sometimes only 2 if you have an OLD moboard), even old ISA Adaptec SCSI AHA1542 cards support 7 (8 counting the card.)
--Now I've got 2 old(er) AHA2940 Ultra Wides that will support 15 devices out of the box - 68 *plus* 50 pin. I've spent quite a bit of money putting together my SCSI chains, even tho I bought most of the HD's on the cheap. Under Linux they're easy to LVM together so you can have (2) 2-gig drives show up as one 4-gig filesystem. I even have an old Plextor 4-plex CDRom above my 8x4x32 Sony IDE burner for disc>disc copying and audio.
--The thing about SCSI though, is that the adapter card is important! Stay away from ISA. (Even a non-BIOSed PCI Advansys gives better performance than my old ISA AHA1542.)
On a side note, how accurate can this mouse possibly be?? Imagine pointing at something in Explorer (shudder) with it, your hand slips a bit, OOPS there goes windoze... (Munching sounds and massive deleting on hard drive ensues) OH F--K I just rm -rf'ed my OS!!!
You said: "I'm happy to say that all that work was thrown in the garbage."
Actually I feel quite sorry for ESR. He put a lot of effort into coding something he believed in, got trashed quite a bit for it even though he was listening to end-user input, and eventually had his code given the boot from the main Linus kernel. Not to mention the public humiliation that goes with that.
Put yourself in his shoes; I bet you would feel pretty hurt and PO'd if that happened to you.
By getting rid of all the modules you DON'T need, you can save a lot of Megabytes in/lib/modules. Plus you can tweak the kernel into being smaller, or optimize it for your processor / architecture. .
I thought the X-files movie was pretty good. It scared the hell out of me, which isn't easy to do!
Lost in Space - TERRIBLE plot, but hey - MIMI ROGERS ( http://us.imdb.com/Name?Rogers,%20Mimi ) in that Latex space suit beats Heather Graham any day!! .
Yesh, I think they could do with a selective change in the writing staff - to rotate all the ppl who are burned out trying to think of new funny material... They should do it about every 3 yrs. .
See here ( http://lwn.net/Articles/9632/ ) and here ( http://lwn.net/Articles/10248/ )
--Linus is being pigheaded about this patch, wanting to "keep the code simple" instead of implementing Ingo's **fast** + Fixed solution.
To quote LWN: [ So it's fast - though a few extra features have been requested. But this patch has stirred up a bit of a debate. Rather than put in a complicated new PID allocator, it is asked, why not just make the maximum PID be very large? Then, in theory, the quadratic part of get_pid() will never run so the performance problems go away, and the code stays simpler. Linus prefers this approach, as do a number of other developers; he has put a simple patch along these lines into his pre-2.5.37 BitKeeper tree.
Ingo disagrees, pointing out that any reasonable maximum PID size can be exceeded eventually. He would rather fix the problem than try to hid it behind a large process ID space. In the absence of real-world examples that show people being bitten by get_pid()'s behavior in a larger PID space, though, Linus appears unlikely to accept any more complicated fix. ]
Does anyone else think it's BLOODY STUPID to put this on/. before it's even finished? This gives the PTB plenty of lead time to shut the project down!!! .
Slashdot Mirror
o Forty years of darkness! Earthquakes! Volcanoes!
o The dead rising from the grave!
o Human sacrifice, dogs and cats living together, mass hysteria!
o
o PROFIT!!
--You know, I never thought of her the same way after that... Plus she didn't look NEARLY as good with that crappy-dye-job blond hair.
.
--Hooters?! Those are ENGINES, you insensitive clod!!
.
"...And thank God I'm only watching the game -- controlling it --
.
I don't see you guys rating
The kind of mate I'm contemplating
I'd let you watch, I would invite you
But the queens we use would not excite you."
--Murray Head, "One Night In Bangkok"
.
"...Bam bam bam bam, buh bam bam bam bam...
I WANNA BE SEDATED..."
.
--That's because almost NOBODY bothers to read the EXISTING comments before reaching hurriedly for the SUBMIT button.
.
:b
.dotgoeshere
You use a language that allows Buffer Overflows by DEFAULT (the target of most Security patches lately) and QUALITY in the same sentence???
.
No, but you still get to keep your original "0" score! :P
.
I am betting that the "1000 rewrites" figure came out of a lab, in which the disc was never removed from the drive - and so never collected "normal" dust and/or scratches.
Plus, that disc was one of the "originals" that were probably a little bit over-engineered - and probably burned at LOW LOW speed, (1-2x) to boot.
CDRs and RW's have become a commodity item, made as cheaply as possible, and for the most part insufficiently tested as far as projected lifetime goes, especially when burned at higher speeds.
MHO, more testing needs to be done with modern equipment before "1000 rewrites" gets taken for the "average" lifetime expectancy again. Tom's Hardware, anyone?
.
Sure you can make an IDE RAID setup, but with most manufacturers going with a 1-year warranty how long do you expect an "average" single IDE drive to last?
.
Why the hell would you want to REDUCE the quality of a SCSI drive, you moron??
.
--I like SCSI as well - IDE limits you to four devices (sometimes only 2 if you have an OLD moboard), even old ISA Adaptec SCSI AHA1542 cards support 7 (8 counting the card.)
:)
--Now I've got 2 old(er) AHA2940 Ultra Wides that will support 15 devices out of the box - 68 *plus* 50 pin. I've spent quite a bit of money putting together my SCSI chains, even tho I bought most of the HD's on the cheap. Under Linux they're easy to LVM together so you can have (2) 2-gig drives show up as one 4-gig filesystem. I even have an old Plextor 4-plex CDRom above my 8x4x32 Sony IDE burner for disc>disc copying and audio.
--The thing about SCSI though, is that the adapter card is important! Stay away from ISA. (Even a non-BIOSed PCI Advansys gives better performance than my old ISA AHA1542.)
Oh, and don't forget to terminate the chain!
.
Actually, it is possible to setup Norton Protected Recycle Bin to delete files without prompting. :b
.
On a side note, how accurate can this mouse possibly be?? Imagine pointing at something in Explorer (shudder) with it, your hand slips a bit, OOPS there goes windoze... (Munching sounds and massive deleting on hard drive ensues) OH F--K I just rm -rf'ed my OS!!!
:b
Ah well, I wanted to try Linux anyway...
.
Since it's in a "companion" orbit, I wish they would name it K-9...
.
Actually the first thing that came to mind was the librarian from Ghostbusters - the movie...
.
I've gotten "I have no root and I must scream" a few times, as well...
.
You said: "I'm happy to say that all that work was thrown in the garbage."
Actually I feel quite sorry for ESR. He put a lot of effort into coding something he believed in, got trashed quite a bit for it even though he was listening to end-user input, and eventually had his code given the boot from the main Linus kernel. Not to mention the public humiliation that goes with that.
Put yourself in his shoes; I bet you would feel pretty hurt and PO'd if that happened to you.
Code on, Eric... Better luck next time.
.
By getting rid of all the modules you DON'T need, you can save a lot of Megabytes in /lib/modules. Plus you can tweak the kernel into being smaller, or optimize it for your processor / architecture.
.
Anyone remember the Daleks and the Cybermen from Doctor Who back in the 80's? .dotgoeshere
I thought the X-files movie was pretty good. It scared the hell out of me, which isn't easy to do!
Lost in Space - TERRIBLE plot, but hey - MIMI ROGERS ( http://us.imdb.com/Name?Rogers,%20Mimi ) in that Latex space suit beats Heather Graham any day!!
.
Dude, WW2 is worth BUYING just for the fact that Tia Carrerra is HOT, not to mention the Kung-Fu parody!
.
Yesh, I think they could do with a selective change in the writing staff - to rotate all the ppl who are burned out trying to think of new funny material... They should do it about every 3 yrs.
.
See here ( http://lwn.net/Articles/9632/ )
and here ( http://lwn.net/Articles/10248/ )
--Linus is being pigheaded about this patch, wanting to "keep the code simple" instead of implementing Ingo's **fast** + Fixed solution.
To quote LWN:
[ So it's fast - though a few extra features have been requested. But this patch has stirred up a bit of a debate. Rather than put in a complicated new PID allocator, it is asked, why not just make the maximum PID be very large? Then, in theory, the quadratic part of get_pid() will never run so the performance problems go away, and the code stays simpler. Linus prefers this approach, as do a number of other developers; he has put a simple patch along these lines into his pre-2.5.37 BitKeeper tree.
Ingo disagrees, pointing out that any reasonable maximum PID size can be exceeded eventually. He would rather fix the problem than try to hid it behind a large process ID space. In the absence of real-world examples that show people being bitten by get_pid()'s behavior in a larger PID space, though, Linus appears unlikely to accept any more complicated fix.
]
Does anyone else think it's BLOODY STUPID to put this on /. before it's even finished? This gives the PTB plenty of lead time to shut the project down!!!
.