Release Notes
Chapter 2, Read this after installation
System configuration

System configuration

No user license found, PMD unable to start
If you see an error saying that no user license is found, check that the system is set to the correct date. If the system date is in the future, you might see problems with expiring licenses.

New scoterm fonts
Four larger scoterm fonts are available (11 by 18, 15 by 25, 16 by 26, 17 by 28). To choose one of these IBM glyph fonts for use on larger resolution screens, in a scoterm window, select Options, then Font Size.

SCSI tape configuration
The SCSI tape device driver, Stp, is not automatically configured into the kernel during installation. If you need this driver, you must configure it after installation using the Hardware Manager or mkdev tape.

Cannot access SCSI tape drive with /dev/rct0
After an upgrade, /dev/rct0 might no longer exist. When you try to access a configured SCSI tape drive, you might see the error: 
   cannot open: /dev/rct0
If the device is correctly configured with mkdev tape, you can access the tape drive using /dev/rStp0.

Remote administration
To administer systems across the network with SCOadmin, you must configure your system appropriately. See ``Administering other systems with SCOadmin'' in the SCO OpenServer Handbook for more information.

Check filesystem permissions
After completing a Fresh or Upgrade installation, make sure the permissions are correct on any filesystems you had previously created (including mounted filesystems).

find -mount not reporting mount points
When cpio(C) is used in conjunction with the -mount option to find(C) on the root filesystem, mount points are not backed up. This is because -mount skips mounted filesystems. Unless these filesystems are unmounted, the mount points are skipped as well. When restoring the root filesystem, you may need to recreate the mount points manually before restoring the filesystems associated with them. For example, after you restore the root filesystem, you may need to create the /stand directory before restoring your backup of the boot filesystem.

NOTE: The Backup Manager takes this behavior into account and automatically re-creates mount points as needed.

PPP Manager does not configure the PPP driver
The PPP Manager does not add the PPP driver to the link kit. To work around this problem, configure your WAN device and protocol stack with the Network Configuration Manager, then use either the Network Configuration Manager or the PPP Manager to configure PPP. For more information, see Chapter 1, ``Configuring network connections'' in Configuring Network Connections and ``Configuring PPP'' in the Networking Guide.

scologin now uses authorization
To avoid potential security problems, scologin(XC) now uses authorization by default to control X display access. To turn off authorization, edit the /usr/lib/X11/scologin/Xconfig file and set the authorize resource to false:

DisplayManager*authorize: false

See also:


Floppy drive I/O errors
If you receive I/O errors when accessing the floppy drive on high-activity machines and you know the floppy media is sound, your system might be sending data faster than the floppy drive can process it. You can fix the problem by enabling FIFO buffering for the floppy device. To do so, edit /etc/conf/pack.d/fd/space.c and reset these variables from the initial value of 0:

fd_enable_FIFO
Set to 1 to enable FIFO buffering.

fd_FIFOthresh
Set the buffer threshold (in bytes) to a sufficiently high value for your system; the range is 1-15. We recommend setting the value to 13 for most Pentium processors, although you may have to experiment to find the appropriate value for your system.

Internet Services programs depending on termcap do not run on console Multiscreen displays
Only in systems localized for European use, the default TERM value for Multiscreen® displays is ``ansi-850'' and there is no entry for ansi-850 entry in the /etc/termcap file (although there is one in /usr/lib/terminfo). As a result, older applications depending on termcap will fail with a ``Can't load ansi-850'' error message. This does not affect scoterm windows, for which TERM is set to ``scoansi''.

Only if you run into this problem, enter one of:

For sh or ksh: TERM=scoansi; export TERM
For csh: setenv TERM scoansi

Add that line to your .profile (sh, ksh) or .login (csh) if you want this change to persist from session to session.

The system administrator can fix this for the entire system by editing /etc/ttytype to replace ``ansi-850'' with ``scoansi'' on each of these lines: 

       ansi-850	tty01
       ansi-850	tty02
       ansi-850	tty03
       ansi-850	tty04
       ansi-850	tty05
       ansi-850	tty06
       ansi-850	tty07
       ansi-850	tty08
       ansi-850	tty09
       ansi-850	tty10
       ansi-850	tty11
       ansi-850	tty12

We recommend changing the TERM type in the most limited way that fixes your problem (per-session change preferred over per-user change preferred over system-wide change), and then only when you actually encounter this problem. 

Changing your system's hostname
To change the hostname of your SCO OpenServer system, follow the steps described in ``Changing the system name'' in the Mail and Messaging Guide, skipping step 4 unless you are running MMDF. Before rebooting (step 7), edit the following files and replace all occurrences of the old name with the new name:

/usr/internet/ns_httpd/admserv/ns-admin.conf
/usr/internet/ns_httpd/httpd-80/config/magnus.conf

If you have the Netscape Proxy Server installed, edit:

/usr/internet/ns_proxy/admin/config/magnus.conf
/usr/internet/ns_proxy/admin/config/obj.conf



Configuring Domain Name Service (DNS)
The Internet Manager automatically configures a caching nameserver. This allows you to make use of the root nameservers out on the Internet to resolve domain names. However, if you already have a nameserver for your domain configured on a different machine to resolve names in your own domain as well as those out on the Internet, you may want to configure your SCO OpenServer system to use that nameserver instead.

To do so:

  1. Edit the /etc/resolv.conf file as follows: 
       domain yourdomain.COM
   nameserver IP address your nameserver
   hostresorder local bind
    For example, if your domain is foo.COM, and the IP address of your nameserver is 199.199.198.1, this file would look like this: 
       domain foo.COM
   nameserver 199.199.198.1
   hostresorder local bind

  2. Set the permissions on /etc/resolv.conf:

    chmod 644 /etc/resolv.conf

  3. Rename the /etc/named.boot file:

    mv /etc/named.boot /etc/named.boot-

  4. Kill the named daemon:

    kill `cat /etc/named.pid`

To configure a primary or secondary nameserver on your SCO OpenServer system, see Chapter 6, ``Configuring the Domain Name Service'' in the Networking Guide.

See also: