An Objective Review of UnixWare 7.1.4
Roblimo writes "Yes, SCO is evil and all that, but in between lawsuits it still puts out a product called UnixWare. NewsForge decided to review the latest version -- 7.1.4 -- just like we would any other Unix-based operating system. To ensure impartiality, we hired respected freelancer Logan G. Harbaugh, who wrote: 'On the server side, UnixWare Enterprise edition is more expensive for 150 users than either Windows 2003 Server Datacenter Edition, any of the Enterprise Linux distributions, or Solaris, with fewer available applications, fewer drivers for recent HBAs and other new hardware, and no currently available 64-bit version for either Opteron or Itanium processors.'"
There are a lot of interesting observations in the review, including:
We use Unixware 7 at work. It was the system recommended by a specific software vendor at the time (and that is the only application we run on the box).
/etc configure what services, this entire area of development is missing. Again, refer to points 1 and 2 and see what a nightmare this could potentially be.
We have been trying to identify the best migration plan for the following reasons:
- SCO's lack of hardware makes upgrading a nightmare of its own. With Windows and Linux, I can buy virtually anything (server hardware, that is) and expect it to "just work".
- The fact that SCO is at least at serious risk of collapse in the foreseeable future means that we now need to keep a copy of the hardware compatibility list and Unixware installation media in case of catastrophe (see point 1 and now imagine no tech support). This is a non-concern with any other reasonable alternative.
- Documentation sucks. From man pages either being non-existent or missing critical information such as what files in
- Related to the last point, Unixware expects you to use the scoadmin tool to do everything, including configure network cards. The location of even a basic ifconfig file is well hidden. To make this matter worse, scoadmin is non-intuitive to maneuver and also does not support termcap/terminfo -- you must use an ANSI terminal or the display will be garbled. Our vendor provides a custom telnet application to ensure you are always in ANSI.
- No support of PAM. We would like to simply integrate our logins with our Windows domain controller. Not possible with Unixware.
The very recent adoption of open source tools is actually the best thing they've done. In the version we have installed, SCO included VisionFS which provides SMB shares but is just not the same quality as Samba. More recent versions have dropped VisionFS and added more open source tools.
That's a quick review off the top of my head from somebody who uses it every day and looks forward to the day that we can be done with it.