Linked by Thom Holwerda on Tue 22nd May 2007 15:22 UTC, submitted by kev009
Permalink for comment 242734
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2007-05-22
I have been using Solaris 10 since it was released originally. When it was released originally patch clusters were not happening very often. That is why I started using smpatch and updatemanager. I don't think it was them forcing people, just they didn't keep up with things for Solaris 10. So I continued to use smpatch, patchadd, and updatemanager. After using it for awhile it eventually put 2 systems into a corrupted state.
But I will agree with you, I suggest anyone doing patching on Solaris stick with the Patch Clusters. As you said you, and I know I, have both had issues with the smpatch and updatemanager tools.
Also I found that some 3rd party packages can corrupt things also. Which is another reason why I would like to see a better package management system.
So your safe bet, use only Sun packages, and use patch clusters. At least until they fix the package management to prevent 3rd party apps from corrupting things, and smaptch/updatemanager.
But it is hard to tell what works or not until you get bitten.