An underlying thread of this thread is that government run operations are inherrently wasteful and privately run operations are efficient. If you consider the hardware and utility costs for private versus public wireless coverage for the same area, they should be the same. Now factor in the wages of the people that manage the system and those that manage the workers. If the price of both systems were equal, either the workers of the public run system must be overpaid or over staffed, or the private run operation workers are underpaid or understaffed. The assumption here is that the private run firm must have some profit left to divy up to the stockholders after the CEO has been compensated way more than a public official.
Realize that this thread has come and gone, but that makes this comment approriate - RAID systems toward end of life. Dell gives warranties for effectively five years (initial three year period + 2 one year renewals), this means that their equipment actuaries see the writing on the wall rather than unquestioningly accept the 2 million hour numbers spouted by the disk drive manufacturer. Have a replacement strategy in place as you approach the end, factor in how long it will take you to transfer the data that you've accumulated during the years of successfully operation. And as an aside, my biggest problems resulted from the ON-OFF cycle. Implement a source of constantly supplied power as well as some system to actually be able to "hot swap" the drives and the cooling fans, cycling the drives to replace a failed or failing drive may push additional drives to failure.
I'm blest with an older group of computer-resistant users, a draconian 1 strike, you're out policy and forced password changes every three months in an NTNovell linked operating environment. Every three months, I can count on two weeks of password changes and rechanges as the users stumble through the procedure. The upshot is that yes, we've got the stickies and drawer plaques, and for that matter, the abysmally easy to crack passwords, no program needed.
All the technical fixes are nice, but your supervisor needs to back you up or you'll be walking soon, either out of disgust or management defined incompetance - both of which won't get you unemployment. Present to your supervisor not only the why (you need to impose rules for the operability of the system), but also the legal implications of letting it continue this way, and a method of implementing it. Have several proposed implementations, and for each include costs/benefits and it wouldn't hurt to include newspaper articles as to the legal possibilities (the more mainstream the news, the better). And yes, it sounds like a lot of work, but if you don't do this, absolutely nothing will happen in the bureacracy of which you are now a part of.
Called the support line stated in the story, was passed on several times by helpful phone support personnel, but in the end, the CD doesn't exist, and here I am, behind several firewalls and caring for a supposedly isolated (reality or theory ???) server.
Slashdot Mirror
Oh great, now we can have robotic pointy headed managers
But do they eat paper ballots as well as Diebold voting machines?
An underlying thread of this thread is that government run operations are inherrently wasteful and privately run operations are efficient. If you consider the hardware and utility costs for private versus public wireless coverage for the same area, they should be the same. Now factor in the wages of the people that manage the system and those that manage the workers. If the price of both systems were equal, either the workers of the public run system must be overpaid or over staffed, or the private run operation workers are underpaid or understaffed. The assumption here is that the private run firm must have some profit left to divy up to the stockholders after the CEO has been compensated way more than a public official.
Realize that this thread has come and gone, but that makes this comment approriate - RAID systems toward end of life. Dell gives warranties for effectively five years (initial three year period + 2 one year renewals), this means that their equipment actuaries see the writing on the wall rather than unquestioningly accept the 2 million hour numbers spouted by the disk drive manufacturer. Have a replacement strategy in place as you approach the end, factor in how long it will take you to transfer the data that you've accumulated during the years of successfully operation. And as an aside, my biggest problems resulted from the ON-OFF cycle. Implement a source of constantly supplied power as well as some system to actually be able to "hot swap" the drives and the cooling fans, cycling the drives to replace a failed or failing drive may push additional drives to failure.
And how much time do you need every three months to keep this policy working - the policy is fine, but is the actual buyin.
I'm blest with an older group of computer-resistant users, a draconian 1 strike, you're out policy and forced password changes every three months in an NTNovell linked operating environment. Every three months, I can count on two weeks of password changes and rechanges as the users stumble through the procedure. The upshot is that yes, we've got the stickies and drawer plaques, and for that matter, the abysmally easy to crack passwords, no program needed.
All the technical fixes are nice, but your supervisor needs to back you up or you'll be walking soon, either out of disgust or management defined incompetance - both of which won't get you unemployment. Present to your supervisor not only the why (you need to impose rules for the operability of the system), but also the legal implications of letting it continue this way, and a method of implementing it. Have several proposed implementations, and for each include costs/benefits and it wouldn't hurt to include newspaper articles as to the legal possibilities (the more mainstream the news, the better). And yes, it sounds like a lot of work, but if you don't do this, absolutely nothing will happen in the bureacracy of which you are now a part of.
Called the support line stated in the story, was passed on several times by helpful phone support personnel, but in the end, the CD doesn't exist, and here I am, behind several firewalls and caring for a supposedly isolated (reality or theory ???) server.