Compatibility

SCO OpenServer scoterm

If you run the SCO OpenServer scoterm command, it will corrupt the entries in /var/adm/utmpx. As a result, all further login attempts will be blocked (as well as causing invalid data for any other administration commands which use it) until the utmpx entry is removed, and a UnixWare command rebuilds it. Since this corruption can not be prevented, it is recommended that the SCO OpenServer scoterm binary is not run on UnixWare.

If you do run scoterm and corrupt /var/adm/utmpx, you can move the utmpx file and then execute the who(1) command to rebuild it from scratch. For example:

mv /var/adm/utmpx /var/adm/utmpx.save
who

After executing the above commands, users should be able to log in to the system and all administrative commands that depend on utmpx should now work correctly.

DISPLAY variable incorrectly set for SCO OpenServer applications

DISPLAY settings for applications for SCO OpenServer may not be valid for UnixWare 7. An error similar to the following may result:

   Connection broken

You may wish to try the following workaround:

   DISPLAY=localhost:0;export DISPLAY
   xhost +localhost

XENIX compatibility removed

XENIX compatibility has been removed from UnixWare 7. Various modules and commands have been removed from the system. These include the DOS commands doscat, doscp, dosdir, dosls, dosmkdir, dosrmdir, and dosrm. Equivalent DOS tools can be obtained from the ``mtools'' package found on the Open License Software Supplement CD-ROM.

The following exec modules and commands i286x, x286emul, i286emul, and xout were removed. These modules and commands provided compatibility for 286 and 386 XENIX binaries. The XENIX filesystem and all supporting commands for it have been removed. The module xnamfs has been removed which supports XENIX semaphores and shared data.

The XENIX libraries libx, libxcurses, and libxtermlib have been removed. Support for the system call nap is now in libc. The system calls creatsem, execseg, chsize, locking, nbwaitsem, opensem, proctl, sdenter, sdfree, sdgetv, sdleave, sdwaitv, sigsem, unexecseg, and waitsem that were in libx were not moved to another library. The corresponding man pages for these system calls no longer exist.

If you execute a XENIX binary you can expect exec to return ENOEXEC, and an error message similar to:

   file: cannot execute [Exec format error]

depending on your shell. You can identify whether a binary is a XENIX binary by using the file command.

The output of the file command on a XENIX binary is the following:

   file:  Microsoft a.out separate pure segmented word-swapped V2.3 V3.0 86
          executable Large Text