Central NJ former client of a friend was using an old office automation system, most likely run on SCO Xenix, from ~20years ago.
In January, client converted to a new "standard" system for his industry. He ran the two systems "in parallel" since January and continued to pay a "consultant" from out of state to maintain his old SCO-based system. Recently, the client told the consultant he was planning to terminate the old contract. Then, earlier this week, the client couldn't bring up the old system AT ALL. Client took the Xenix box to his Windows hardware vendor (they rent desktop PCs from this guy for the office workers). The vendor claims there is "nothing on this system." The bad news is that there was some "historic" data that had not yet been "moved" to the new system. They do have an old tape backup which might have "most" of the history. Local sysadmin volunteered to look at the system with a Linux CD / memstick to see if there is "anything" on the hardware, but expects the consultant may have either wiped the hard drive or at least the boot sector (he's been remotely administering the system for years, and probably had a "back door" user id as well). Said sysadmin has asked me if I have any ideas, resources or references that might be able to assist with the problem. They're hoping NOT to get into true Xenix "forensics", but it might come to that. They are also not sure if current Linux distributions can read an SCO-based file systems. I of course thought of LOPSA folks first and foremost. The local sysadmin in question is a family member whose skills I entirely respect and who helped set up the system for the client eons ago. Any help, advice, or offers of assistance are truly welcomed. ---pam
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
