Java glitch hits OS X update

TalkBack 7 of 27:

Next »

« Previous

• Thread View
• Flat View

Many variables

exist when patching software. Two identically configured systems purchased at the same time become two radically different systems a few months down the road after different software has been installed, different patches have been applied, and new hardware has been installed. There is no way a vendor of any size can test against all permutations of hardware, software, and patch insatallations.

Diligence is a necessity when you are patching production systems. Take the guy in the article, Geller. He had TWO systems that experienced the same failure after applying the patch. He should have patched one, worked with it for a few days or a week or whatever, and if everything is okay, patch the other. This way, he always has at least one working system. In his case, he would have seen his development environment fail after the patch, and still been able to work on the other machine while Apple figured out what went wrong.

There is a saying in the service sector (of any industry), 'Lack of planning on your part does not necessarily constitute an emergency on our part.'

Posted by: Hugh Jass   Posted on: 04/19/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Get top-ranked Novell support for Red Hat at 50% less Novell A simplified IT environment isn't just less complex, it's more reliable. ... Download Now
• Building the Virtualized Enterprise with VMware Infrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now
• Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now