Yes, linux and the other x86-based os's have thier flaws, but christ on an intel chip, can anyone deney that Wundows is infact a virus/exploit contruction kit? I thought not.
Funny comment, but his point is valid. Why is it so damn nessessary to register for every goddamn thing that some one publishes on the fucking net for godsakes? After registering for every little piss-assed spot of print on the thing I admit I'm a bit jaded myself.
Can you name any good reason why the linuxites wouldn't attempt to cross linux with anything else left on the planet? I guess a linux-enabled can opener is a bit off the list of possibilities, then again...
And why would one do that? Pelts suck anyway, I don't use them. I use GlobalWin FOPS and liquid cooling. Pelts have a strange cooling graph and fall short even when compared to plain air cooling. Plus the condensation is too much of a pain to deal with. Forget Peltiers.
I'll agree, if you have a mission critical box, you probably don't want to oc it. But after a number of years of ocing chips I can honestly say that I don't see the volume of failures that you seem to be implying. A chip oc'ed to a reasonable degree seems to offer the same stability that a chip at the rated speed offers.
I agree; I have a number of i86 platforms running a variety of os's. I never reboot my PII@200MHz running freeeeBSD 3.3 doing firewall/natd duty and its been up for two years. My linux box doesn't crash, I simply reboot it more often becuase I need more configuration changes. The only machine that crashes is my overclocked (yes) PIII flipchip, and only when I'm running 98, for games. It dual boots that and 2K. The 2K side doesn't crash, and I'm pushing a 700MHz chip up over a gig.
You've got to be kidding. You're suggesting that everytime I install some blorb of code that I need for *whatever* reason, from some kind of domain security package to a cron job in perl to move a file from one directory to the other once a day forever needs to be personally re-tooled (re-compiled, essentially, don't tell me you can do decent optimizations of anything without a re-build) by me. You have forever? I don't. That's a cynical, and typically geek attitude. The real world doesn't have the time, the patience, or the expertise for that kind of nonsend. You are suggesting that everytime a bridge be built each part be built with tweezers and micometer. No f-ing way. Ain't gonna happen Gungadin.
How much of the "smart thing" is the onus of the programmer/designer, at least within the context of a level platform (one code line?) Certainly I have to give creedance to x-platform compatibility and the misfires that come from trying to optimize once-compiled code, but come on... you ultra-geeks have to realize there is a larger world out there, one that doesn't give a whit about "properly" optimizing a code chuck.
Cool. Never the less, its also cool to buy a chip
rated for 700 MHz and push that sucker up over a Gig; let us not forget the overclockability of the recent cC0 stepping of Intel FC-PGA PIIIs... I have one. If you use liquid cooling you can keep that baby humming at 1.03 gigs rock solid. Not bad for a $170 processor.
No, you're not the only one. It was absolute fluff. The essence of the art. was as though oc'ing were some mysterious, dangerous, sport of kings or something. Which may very well be the case as I suspect the author was trying to generate some excitment for this weak peice of crap. The article, should it have been written at all, might have well consisted only of links to the sites you mention above. Thats It. Who needs this? Also, I'm a little surprised at the negative responses on oc-ing here on Slashdot. OC-ing isn't something you have to do, its something you see if you CAN do. Like climbing a mountain. Can I do it? Will this peice of crap MSI/PIII do 1.2 gigs? Its something computer hobbyists do. So what if it voids the damn warranty? If your so worried about it then obviously you need to ditch the BMF who is holding a gun to your head making you do it. Remember that personal computing used to be purely a hobbyists pursuit. That's how the Apple II came to be.
Slashdot Mirror
Yes, linux and the other x86-based os's have thier flaws, but christ on an intel chip, can anyone deney that Wundows is infact a virus/exploit contruction kit? I thought not.
Funny comment, but his point is valid. Why is it so damn nessessary to register for every goddamn thing that some one publishes on the fucking net for godsakes? After registering for every little piss-assed spot of print on the thing I admit I'm a bit jaded myself.
Can you name any good reason why the linuxites wouldn't attempt to cross linux with anything else left on the planet? I guess a linux-enabled can opener is a bit off the list of possibilities, then again...
F*ckin' frog.
No.
And why would one do that? Pelts suck anyway, I don't use them. I use GlobalWin FOPS and liquid cooling. Pelts have a strange cooling graph and fall short even when compared to plain air cooling. Plus the condensation is too much of a pain to deal with. Forget Peltiers.
I'll agree, if you have a mission critical box, you probably don't want to oc it. But after a number of years of ocing chips I can honestly say that I don't see the volume of failures that you seem to be implying. A chip oc'ed to a reasonable degree seems to offer the same stability that a chip at the rated speed offers.
I agree; I have a number of i86 platforms running a variety of os's. I never reboot my PII@200MHz running freeeeBSD 3.3 doing firewall/natd duty and its been up for two years. My linux box doesn't crash, I simply reboot it more often becuase I need more configuration changes. The only machine that crashes is my overclocked (yes) PIII flipchip, and only when I'm running 98, for games. It dual boots that and 2K. The 2K side doesn't crash, and I'm pushing a 700MHz chip up over a gig.
You've got to be kidding. You're suggesting that everytime I install some blorb of code that I need for *whatever* reason, from some kind of domain security package to a cron job in perl to move a file from one directory to the other once a day forever needs to be personally re-tooled (re-compiled, essentially, don't tell me you can do decent optimizations of anything without a re-build) by me. You have forever? I don't. That's a cynical, and typically geek attitude. The real world doesn't have the time, the patience, or the expertise for that kind of nonsend. You are suggesting that everytime a bridge be built each part be built with tweezers and micometer. No f-ing way. Ain't gonna happen Gungadin. How much of the "smart thing" is the onus of the programmer/designer, at least within the context of a level platform (one code line?) Certainly I have to give creedance to x-platform compatibility and the misfires that come from trying to optimize once-compiled code, but come on... you ultra-geeks have to realize there is a larger world out there, one that doesn't give a whit about "properly" optimizing a code chuck.
Cool. Never the less, its also cool to buy a chip rated for 700 MHz and push that sucker up over a Gig; let us not forget the overclockability of the recent cC0 stepping of Intel FC-PGA PIIIs... I have one. If you use liquid cooling you can keep that baby humming at 1.03 gigs rock solid. Not bad for a $170 processor.
No, you're not the only one. It was absolute fluff. The essence of the art. was as though oc'ing were some mysterious, dangerous, sport of kings or something. Which may very well be the case as I suspect the author was trying to generate some excitment for this weak peice of crap. The article, should it have been written at all, might have well consisted only of links to the sites you mention above. Thats It. Who needs this? Also, I'm a little surprised at the negative responses on oc-ing here on Slashdot. OC-ing isn't something you have to do, its something you see if you CAN do. Like climbing a mountain. Can I do it? Will this peice of crap MSI/PIII do 1.2 gigs? Its something computer hobbyists do. So what if it voids the damn warranty? If your so worried about it then obviously you need to ditch the BMF who is holding a gun to your head making you do it. Remember that personal computing used to be purely a hobbyists pursuit. That's how the Apple II came to be.