Valid XHTML 1.0 Transitional

SCO Unix and Proftpd

I recently had the misfortune to be compelled to install Proftpd on SCO Unix. There’s nothing wrong with Proftpd of course, but everything is wrong with SCO.

LDFLAGS=-L/usr/ucblib ./configure –libdir=/usr/ucblib --enable-builtin-getnameinfo

To get it to compile the above ./configure line is needed. It uses /usr/ucblib because having the basic BSD sockets API residing in a non-default directory makes things more exciting. The --enable-builtin-getnameinfo option is needed because the getnameinfo library call in SCO Unix doesn’t work properly. On a real OS I would have downloaded the source to libc to figure out where the problem might be, but on SCO I had no option other than to disable that functionality.

Then once I got it working I had to put UseIPv6 off in the configuration file, otherwise I got the error No Route to Host (from memory) when I tried to start proftpd.

Finally the process was dying from an unhandled SIGALRM every 10 seconds. According to truss (a vastly inferior equivalent to strace) the sigaction() system call was being entered four times to handle SIGALRM (as was reported for every time the application code called sigaction() but the default action of terminating the application remained in place. I ended up running proftpd from inetd which removed the need for the alarm handling code. Then it all worked.

SCO sucks.

Last month Darl McBride was terminated from his position with the SCO group [1]. It’s unfortunate that Darl wasn’t terminated a lot earlier, if so then maybe SCO could have focussed on improving the quality of their products and delivering value for stock holders. Hopefully Darl will be sued by some of the people who lost money when SCO went bankrupt.

It would be good if Darl could also be sued by companies that lost money due to the poor quality of SCO Unix – that means every company that runs SCO servers or that writes software for it. The truly awful nature of SCO Unix is in large part due to the fact that all of SCO’s money was spent on litigation that was well known to be baseless.

2 comments to SCO Unix and Proftpd

  • To be fair, the original Santa Cruz Operation had already sold itself to a Linux vendor (Caldera) before McBride showed up. The legacy Un*x products were already in the dreaded “we’re committed to supporting our existing customers” mode. They didn’t go from Un*x vendor to litigation, they went from Un*x vendor to Linux vendor to litigation. (The real mistake was firing Ransom Love, with his Novell connections, shortly before Novell came looking for a Linux company to buy. Novell had to settle for SUSE.)

  • Craig Ringer

    The “SCO” you refer to isn’t the original company – the “Santa Cruz Operation,” maker of SCO¬†Unix – in any meaningful way.

    The original SCO sold its UNIX assets and the rights to the “SCO” name to the Linux company Caldera years ago, then renamed its self to Tarantella and washed its hands of UNIX. Even before then SCO UNIX (OpenServer) was basically dead – SCO were putting all their efforts into the marginally less decrepit UnixWare OS.

    So – even without McBride and friends’ intervention, you’d still be stuck with a miserable lemon of an OS.

    I have a fair bit of empathy for you as I have a mission-critical system stuck on SCO OpenServer 5.0.5 … in Microsoft Xenix emulation mode. The binaries are from 1983. Thankfully I’m getting there on the rewrite, but … eek.