OT: SCO/Patchck
Jay Ashworth
jra at baylink.com
Wed Jun 15 09:47:46 PDT 2011
Has anyone here used Patchck to update a SCO system?
Successfully?
I blew about 4 hours yesterday because, as nearly as I could tell, it
downloaded 2 patches to my 5.0.6 system (which already had rs506a) which
had files that did not match the package manifest in size or checksum...
and installed the patches anyway, and left them installed even after it
detected the error (and it *did* detect the error).
One of the files was libc.so.
I don't have to explain how poorly things went after that, right? Happily,
they apparently build custom(1m) with static libraries, so *it* could tell
me it thought those patches were only partially installed, and back them
out (though I had to ignore precisely the errors that caused the problem
in the first place).
But... really?
We really *have* a manifest, and we don't appear to actually *check* it
until *after* we install the bad packages? And, more to the point: there
*were* bad patch packages on their server?
I reinstalled the two problematic ones: oss646 and 648 (processor and
execution environment supplements, probably not respectively), each
separately... and each failed again. Failed the entire system, I mean;
you know what happens when libc gets borken.
So: was this just me? Has anyone else seen this? Is there actually
a contact channel to complain up?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
More information about the Filepro-list
mailing list