We’re sorry, but your Gmail account is temporarily unavailable. We apologize for the inconvenience and suggest trying again in a few minutes. You can view the Apps Status Dashboard for the current status of the service.
All the newer shelves came preloaded with Coraid-approved drives. As I said, there's hundreds of drives involved here, a lot of SATA 1TB and 2TB and some SAS 600GB. I think out of the later drives, we've had two fail. Maybe three.
Asked about it, Coraid said, yes, the warranty is better on "Enterprise-class" or "RAID-class" drives, but also, the firmware is different. They claim that drives intended for the consumer / SOHO market spend a lot of time retrying marginal reads before declaring an unreadable sector and sparing it. They say that SAN-class drives limit the retry time, because the array controller handles it more efficiently, since it has the big-picture view.
The also say that the drives are optimized for close-quarters operation, all jammed together in an array, handling vibration and heat build-up slightly differently, and that they have minor differences to keep lubrication from migrating out of the spindle bearing under continuous operation. I don't know but I imagine loss of spindle bearing lube would add vibration and make any but the best reads more marginal.
I don't know for sure, but we've spent a great deal of US dollars on their products and our experience has borne out the fact that there's a definite difference in arrays.
As for corporate desktop and/or server use, well, I don't really know. Our servers that have one to four drives were mostly shipped with those drives, so we didn't choose them. I can't tell you if they are enterprise class drives, but I imagine they are, based on the replacement costs. And I know about what some of those costs are, or anyhow I know they were way more than I personally pay for drives for home desktop and server use. I know that because occasionally they fail, and I have to buy new ones.
Babbage's Analytical Engine was never completed, right? Having those custom made castings and machined parts got really expensive.
Does anyone else find it ironic that the chosen language of the US DOD was named for the first programming project to go over-budget and behind schedule?
One thing the dairymen told me was that one of the first signs of an animal getting sick was that it would usually eat less. Our system at the time each animal had a collar with a transponder on it-- an unpowered device about the size of two decks of cards. Something like a very primitive RFID chip. How much each animal ate was recorded and any unusual patterns were brought to the attention of the owners or managers. As soon as such pattern developed, the animal could be examined and treated. This makes good economic sense, because healthy cows produce more. But it struck me as compassionate as well.
We also discovered that some cows would game the system, realizing that every time they stuck their head into the feeder, that auger would start up and dump grain into the trough. We fixed it so they would only get a healthy amount at a crack. They figured out that putting your head in, pulling it out, and putting it in again would get you another pile of goodies. We modified it again, so it wouldn't do that. The cows that had been gaming the system were fine, but certain others would never go back after it stopped delivering feed for them. So we modified it again so that even if you'd already had your allocation, sticking your head in again would still net you another handful. Just enough to keep them coming back when they got hungry, and more importantly, the next day, and the day after that, etc.
It was really fun trying to outthink cows. It wasn't nearly as easy as you'd think.
Examples of very young hams abound. Documented cases of VEs (volunteer examiners) helping examinees cheat are few, and in comparison, nearly nonexistent.
Then we have a few people that interact a great deal more with other companies, local government and etc. For them we have to buy license of Microsoft Word, because abovementioned external parties continue to mindlessly send us stuff in Word format, often @#%$@#%&^%$#*&
WordPerfect mostly works ok and about 30% of my users don't realize they aren't using Bill's program. It has a few issues. There's a piece of code that sits in memory after you print until you're done until you exit WP. After printing the second doc with complicated images and layout, that piece tends to lockup and take 100% of the cpu. It never finishes what it was doing. So we just kill that piece, don't even exit WP, and life goeth on.
I love "reveal codes." Why don't all wordprocs have that? Untangles some really twisty little problems, especially when my users import docs from another source, edit it, and the result is a tangled mess.
You want to know the funniest part of this? As part of the support team for this, I have to assume when users call and say they are having a problem with "Word" that they mean "WordPerfect:" because that's what they all call it.
Dead? No excuse for laying off work.