Comment Unixware a reasonable unix? (Score 1) 40
I'm a self-respecting Unix person who works for Ingram Micro supporting SCO (as well as HP-UX and Linux in an unofficial capacity).
I'll admit that my we haven't had a huge amount of experience with Unixware, as most customers are staying with Openserver, but what experience I have had does not impress me.
First, why is it that you cannot set up dial-in and dial-out on the same port? And why does the first serial port always reset to PPP irregardless of what you have configured it as?
And why don't the ported administation tools reflect differences in the two operating systems (e.g. the username field in the accound administrator only accepts 8 character usernames whereas the rest of the tools accept 256 iirc.
And on that note, why is there little to no error handling in the tcl admin tools. I've had to go through dozens of tcl stack dumps from admin tools that wouldn't even start, only to discover it was because of a bad entry in a config file.
Openserver is even worse - the 5.0.5 print subsystem is 100% fubar, fixing a mistake in adding a device often requires editing half a dozen files some of which are C code, the amird driver in rs504c and 5.0.5 somehow screws up all console logins except for X's login, etc.
It is understandable why you would suggest skunkware tools over your own, as SCO tar doesn't have support for backup of empty directories or special files; cpio in one of its incarnations (I do not recal which) hangs when piped to more, etc.
And SCO has a major problem with support. A fair amount of techs working on the priority lines are definitely talented, but a lot of the front line support is imho (as well as most people I deal with) utter carp.
I'll admit that my we haven't had a huge amount of experience with Unixware, as most customers are staying with Openserver, but what experience I have had does not impress me.
First, why is it that you cannot set up dial-in and dial-out on the same port? And why does the first serial port always reset to PPP irregardless of what you have configured it as?
And why don't the ported administation tools reflect differences in the two operating systems (e.g. the username field in the accound administrator only accepts 8 character usernames whereas the rest of the tools accept 256 iirc.
And on that note, why is there little to no error handling in the tcl admin tools. I've had to go through dozens of tcl stack dumps from admin tools that wouldn't even start, only to discover it was because of a bad entry in a config file.
Openserver is even worse - the 5.0.5 print subsystem is 100% fubar, fixing a mistake in adding a device often requires editing half a dozen files some of which are C code, the amird driver in rs504c and 5.0.5 somehow screws up all console logins except for X's login, etc.
It is understandable why you would suggest skunkware tools over your own, as SCO tar doesn't have support for backup of empty directories or special files; cpio in one of its incarnations (I do not recal which) hangs when piped to more, etc.
And SCO has a major problem with support. A fair amount of techs working on the priority lines are definitely talented, but a lot of the front line support is imho (as well as most people I deal with) utter carp.
