SCO UNIX V/386 3.2v4.0

The new version of SCO UNIX is now available. The same product will install on both MCA and AT Bus products simplifying the ordering required. A number of changes in the product are covered below including configuration issues. The new features are included in UNIX NEWS 15.

1. There are now four security levels from C2+ down to low security. Most systems only need traditional UNIX security which is either chosen at installation or can be set later by root using the command:

   /etc/relax traditional

   which will then request a kernel build and reboot if necessary.

2. Any system being upgraded and not using one of the SCO standard gettydefs entries (such as 'm') for the console will need the word SCANCODE appended to the gettydefs entry in a manner similar to the new 'sc_m' entry. Otherwise the keyboard may be interpreted as generating graphics characters. If the consoles are configured to use the 'm' entry they will be changed in /etc/inittab and /etc/conf/cf.d/init.base to the 'sc_m' entry.
   
3. Installing the tape version of 3.2v4.0 requires a tape device to be seen by the kernel, otherwise the system may panic
   
4. Tape installation can now be achieved even if the tape is not using id 2. The target id should be changed, if 2 is not correct, the host adapter and LUN will remain 0 in almost all cases.
   
5. When booting up the kernel, SCO kernel interrupt values are now reported in decimal not octal BUT drivers written before 3.2v4.0 still use octal. This can lead to two devices appearing to use the same interrupt when in fact they are not. For example the UPS software reports interrupt 13 (decimal 11) but the co-processor is also reported on 13 but this is a decimal value.
   
6. Under "traditional" UNIX settings if you get the message: "Cannot obtain database information on this terminal" the system will correct the error it if you try to login a second time.
   
7. The absolute minimum memory recommended by Apricot is 5MB.
   
8. To convert an existing filesystem to the new EAFS filesystem, unmount the filesystem and type the command:

   fsck -E <device name>

   Only this filesystem type supports names up to 255 characters and symbolic links.

9. Installations on 1.3GB and 2.0GB Winchesters must place the whole of the root filesystem within the first 1.0GB and 1024 cylinders.
   
10. It is now possible to boot and use MS-DOS partitions of greater than 32MB. A primary partition of > 100MB and MS-DOS 5 can be booted from the UNIX Boot prompt and accessed when UNIX is booted, as a filesystem.
    
11. On the console some processes which display boxes or line drawing may use the wrong graphics character. SCO are working on this problem.
    
12. On 3.2v2.0 systems an upgrade can be performed without complete reinstallation, on 3.2.0 it is necessary to completely reinstall with either the upgrade or new product. The 3.2v2.0 running upgrade procedure will also keep TCP/IP 1.1.3f and NFS 1.1.1 and XSight 2.3 intact but other products in the kernel will require reinstallation (such as Apricot Security and UPS).
    
13. Installations where the TCP/IP 1.1.3f Maintenance Supplement is installed will get the warning

    /./usr/include/sys/nb/ncb.h: 36: M_I386 redefined

    This can be ignored, to remove the error amend lines 35-37 to

    #ifndef M_I386
    #ifdef i386
    #define M_I386
    #endif
    #endif
    
    which will remove the error

14. MCA Adaptec cards should be of at least revision 03E for the card with Rev A microcode and Rev A BIOS for use with 3.2v4.0.
    
15. The serial and parallel ports are no longer configured in by default. The internal parallel port is now /dev/lp0, however we recommend both parallel ports and on-board serial ports are not configured on machines with intelligent serial cards like the Specialix.
    
16. Symbolic link support has been added to find, cpio and tar. Where filesystems are being backed up the most secure routine is to use the -follow option to find but to avoid the -L option to cpio. For example.

    find . -follow -print | cpio -ov > /dev/rct0

    will ensure symbolic links are checked for infinite loops and do not corrupt a backup.

    The -L option to cpio or tar will result in the file on the remote filesystem being backed up as if on the local filesystem, the symbolic link being destroyed.

    ----------oOo----------