About the Upgrade installation type

The Upgrade option

is available if your previous installation is SCO OpenServer Release 5.0.0, 5.0.2, 5.0.4, or 5.0.5 and your hard disk has sufficient space available for SCO OpenServer Release 5.0.6. (See the Release Notes for disk space requirements, and for other information about the Upgrade option.) This option leaves all non-root filesystems and partitions as they are. On the root filesystem, it removes the old system and installs new versions of all the previously installed packages. The Upgrade option appears near the beginning of the installation prompts, under Installation type.

If an upgrade fails, the installation program attempts to
restore the previous system. The program displays a message about the expected state of the system, depending on the phase in which the upgrade failed, and may direct you to check whether you need to restore the system from backups.

Here are the paths available for Upgrade installations:

      If you are upgrading from:        You can upgrade to:

      SCO OpenServer 5.0.0 Host         SCO OpenServer 5.0.6 Host
      SCO OpenServer 5.0.0 Desktop      SCO OpenServer 5.0.6 Desktop
      SCO OpenServer 5.0.0 Enterprise   SCO OpenServer 5.0.6 Enterprise
      SCO OpenServer 5.0.2 Host         SCO OpenServer 5.0.6 Host
      SCO OpenServer 5.0.2 Desktop      SCO OpenServer 5.0.6 Desktop
      SCO OpenServer 5.0.2 Enterprise   SCO OpenServer 5.0.6 Enterprise
      SCO OpenServer 5.0.4 Host         SCO OpenServer 5.0.6 Host
      SCO OpenServer 5.0.4 Desktop      SCO OpenServer 5.0.6 Desktop
      SCO OpenServer 5.0.4 Enterprise   SCO OpenServer 5.0.6 Enterprise
      SCO OpenServer 5.0.5 Host         SCO OpenServer 5.0.6 Host
      SCO OpenServer 5.0.5 Desktop      SCO OpenServer 5.0.6 Desktop
      SCO OpenServer 5.0.5 Enterprise   SCO OpenServer 5.0.6 Enterprise

Because the default configuration for SCO OpenServer Release 5.0.6


is larger than the default configuration for SCO OpenServer Release 5.0.0, 5.0.2, 5.0.4, 5.0.5, the root filesystem on your primary hard disk might not be large enough to hold the upgraded system. Check the Release Notes for space requirements. If you want to choose the Upgrade option, but your root filesystem will not hold the new release, you have three options:

• Increase the size of your root filesystem by reconfiguring your hard disk.

• Install a larger primary disk.
  

• Install components of the new system on non-root filesystems. If your total disk space is sufficient and you have available partitions, the installation prompts you to relocate components
  
  to other filesystems (including filesystems on non-primary disks).

Do not rely on being able to put additional data (such as user accounts) on the filesystems you choose for relocation. The relocation program uses nearly all the space in the chosen filesystems, in an attempt to create free space in the root filesystem.

Only filesystems in /etc/default/filesys are offered for relocated components. If you want to relocate components to filesystems that are not displayed at this stage of the installation, abort the installation,


reboot your previous system, and run mkdev fs to place the filesystems in /etc/default/filesys.

See the Release Notes for more information on relocated filesystems.

Data retained with the Upgrade installation type

User data retained on the root filesystem includes:

• home directories

• user-created files and directories

• user IDs

• group IDs
  

• passwords

• file permissions

• mailboxes

System data retained on the root filesystem includes:

• system configuration files

• job scheduling files

• filesystems

• filesystem nodes

• mount points

• terminal control database

• auditing parameters

• file control database

• system defaults

• mail aliases

• configuration files for incoming and outgoing PPP lines

• UUCP dialer files