Basic system requirements for upgrades

Release Notes
Chapter 1, Read this before installation

The current release of SCO OpenServer is larger than previous releases. See ``Disk space'' for specific space requirements for each upgrade path.

If you do not actually have SCO IPX/SPX configured on your system, you should remove the /etc/ipx.d/NPSConfig file before installation. A default IPX/SPX configuration in this file (created if IPX/SPX configuration was deferred during a previous installation, but then was never actually configured) will cause installation problems (even in the case of a Fresh installation).

Upgrades and the relocation of software

After an Upgrade installation which relocated software to non-root filesystems, the following error message might appear before the prompt to enter System Maintenance Mode:

   mount: /dev/root is already mounted, / is busy,
   or allowable number of mount points exceeded: Device busy

This message is spurious; the root filesystem is mounted and your system is usable.

In some Upgrade installations, you might be offered the option to relocate software when doing so is not necessary.

After calculating the free disk space on your computer to determine the suitability of your system for an Upgrade installation, you might see the message, Your system can be upgraded, however your root filesystem does not have enough free space to hold all the new software, followed by the ``Using non-root filesystems for Software Storage'' screen.

If this screen is displayed and the only filesystem option under ``Available filesystems'' is root, you can safely accept this choice and proceed with the installation. There will be enough disk space in the root filesystem to complete the install successfully.

Adding a disk for an upgrade

If you have insufficient disk space for an Upgrade installation, you can add a disk before beginning the upgrade. Install and configure the disk on your current system, relink the kernel, then reboot; see Chapter 18, ``Adding hard disks'' in the SCO OpenServer Handbook for more information. Run mkdev fs to create any filesystems that you need. Then, verify that you can access the disk (for example, with the mount(ADM) command) before beginning the upgrade.

The installation (Fresh or Upgrade) can use as many as two non-SCSI disks. If you have a SCSI subsystem, you can add one or more SCSI disks.

Upgrading third-party LLI drivers

If you upgrade from a previous SCO operating system with a network adapter driver that was not provided by SCO, you might see an error message similar to:

Error:  Cannot configure lo0 under sco_tcp

Press <i> to ignore this error message; TCP/IP will be fully functional after the upgrade.

Upgrading cron and at jobs

If you upgrade from a system that uses /usr/lib/cron/cron.deny instead of /usr/lib/cron/cron.allow, then both files will exist on the system after an Upgrade installation. To continue using /usr/lib/cron/cron.deny, you should remove /usr/lib/cron/cron.allow. (If you are using /usr/lib/cron/cron.allow, you do not need to change.)

Similarly, if you upgrade from a system that uses /usr/lib/cron/at.deny instead of /usr/lib/cron/at.allow, then both files will be present after the upgrade, and you should remove /usr/lib/cron/at.allow. (If you are using /usr/lib/cron/at.allow, you do not need to change.)

Upgrading a system with user crontab(C) entries might produce an error message similar to:

Error:  Unable to add custom symlinks report to crontab file

Press <Enter> to ignore this error message and continue; your crontab files will be preserved during the Upgrade installation.

Upgrading the sendmail aliases database

After an Upgrade installation of a system that uses sendmail as the Mail Transfer Agent, run the newaliases(ADMN) command as root. This rebuilds the sendmail aliases database.

Upgrading with scodb

If you are running scodb, turn it off before beginning an Upgrade installation. Performing an upgrade with scodb running may cause kernel relink errors. Start scodb after the upgrade is complete.

Upgrading Netscape Communicator

Netscape Communicator is not installed as part of an Upgrade installation. To use Communicator, after upgrading, use the Software Manager to install it from the SCO OpenServer CD-ROM. You do not need an additional license.

If your existing system has Netscape Navigator, installing Communicator will overwrite Navigator. Information in a user's .netscape directory, such as bookmarks and preferences, will be preserved. (If you remove Navigator before installing Communicator, back up the .netscape directory first, so you can restore this information later.)

Upgrading UDK OSRcompat module

The UnixWare/OpenServer Development Kit (UDK) compatibility package (OSRcompat) is no longer installed by default with SCO OpenServer.

If you are upgrading a system that has OSRcompat installed (which includes SCO OpenServer Release 5.0.5 systems, for which it was installed by default), you should remove it and install the new OSRcompat module. For more information, see ``UDK and OSRcompat module'' in SCO OpenServer Features and Limitations.