If you encounter problems during the installation, see Chapter 3, ``Troubleshooting the installation''.
Before you begin:
See also:
After installation, keep this checklist with your system log.
1. Boot-time Loadable Drivers [] No
(BTLDs) required? [] Yes, enter
Also consult your BTLD software package names:
supplier's documentation. --------------------
--------------------
--------------------
--------------------
2. Installation media [] ATAPI/EIDE CD-
If you use your primary drive, ROM
autodetection will probably (ATAPI-2-
fill in the correct entry. See compliant)
SCO's Compatible Hardware Web IDE Controller
Pages for device names. See Primary or
this book for SCSI secondary:
configuration Master or slave:
[] SCSI CD-ROM
SCSI Adaptor Type:
SCSI Host Adaptor:
SCSI ID:
SCSI LUN: 0
(always 0 for
SCO-provided
drivers)
SCSI BUS:
3. Keyboard language --------------------
(For example, UK English.)
4. License number --------------------
Copy answers 4, 5, and 6 from --------------------
the Certificate of License and
Authenticity (COLA.) If you
are performing an Upgrade
installation, you must have the
license keys for both the
original system as well as the
upgrade.
5. License code --------------------
--------------------
6. License data --------------------
(This field appears only during --------------------
certain installations.)
7. Installation type [] Fresh
An Upgrade preserves your [] Upgrade (if
existing filesystems, but may system is suitable)
not provide all the new If upgrading, stop
functionality that a Fresh here and begin the
installation offers. (Some upgrade procedure.
systems cannot be upgraded.)
8. System name --------------------
Must be unique, begin with a
letter, and contain only
lowercase letters and numbers
(a maximum of 8 characters).
9. Domain name --------------------
10. Security profile [] High (above C2)
Use High for systems with [] Improved (C2)
confidential information and [] Traditional
many users, Improved for [] Low
systems with users who share
information, Traditional to
maintain compatibility with
existing UNIX systems, or Low
for systems not widely or
publically accessed.
11. Time zone Continent or
geographic area:
--------------------
Time zone name:
--------------------
Daylight savings
observed?
[] Yes [] No
12. Language --------------------
If you will be running a
language product other than US
English (for example, French or
German), specify it here.
13. Initial system profile [] Standard system
Standard Enterprise installs [] Lightweight
all software except Microsoft character terminal
LAN Manager Client, SCO [] Database
Gateway, and PC-Interface® services (add to
Server. Lightweight character either Standard or
terminal also leaves out the Lightweight)
X11 server and clients,
graphical administration tools,
and the IPX/SPX runtime.
Database services adds the suds
driver for large database
products.
14. Hard disk setup, first disk [] Preserve (if
Preserve maintains current available)
partitions and divisions (some [] Use whole disk
systems cannot be preserved). for UNIX
Use whole disk for UNIX [] Customized
configures default partitions layout
and divisions. Customize lets [] Interactive
you create and resize fdisk/divvy
partitions and divisions.
Interactive invokes fdisk(ADM)
and divvy(ADM) for more
precision.
Customized or Interactive
layout
(Also see the Release Notes for
a description of filesystem
types.)
UNIX partition size (MB) --------------------
DOS partition size (MB) --------------------
Other partition size (MB) --------------------
boot filesystem size (MB) --------------------
swap space size (MB) --------------------
(recommend 1.5 to 2 times RAM)
root filesystem size (MB) --------------------
(new filesystem types no longer require small root
filesystems)
Other filesystems size (MB) --------------------
15. Bad track/block, first disk [] None
Thorough/destructive ensures []
the highest disk integrity, but Thorough/destructive
takes longer. Less thorough [] Thorough/non-
choices increase the risk of destructive
installation failure due to bad []
spots on the disk. Quick/destructive
[] Quick/non-
destructive
16. Hard disk setup, second disk [] Preserve (if
(If applicable) available)
[] Use whole disk
for UNIX
[] Customized
layout
[] Defer
Customized layout
UNIX partition size (MB) --------------------
DOS partition size (MB) --------------------
Other partition size (MB) --------------------
boot filesystem size (MB) --------------------
swap space size (MB) --------------------
Other filesystems size (MB) --------------------
17. Bad track/block, second disk [] None
(If applicable) []
Thorough/destructive
[] Thorough/non-
destructive
[]
Quick/destructive
[] Quick/non-
destructive
18. Software components [] Operating system
To override the initial system [] Graphical
profiles, you can install whole environment
and partial components in any [] Connectivity
combination. (See the Release [] Online
Notes for disk space documentation
requirements.) After initial
installation, you can add or
remove software
19. Network card Vendor and model:
You do not need this --------------------
information if you Interrupt vector
autodetect the network (IRQ):
card or defer networking --------------------
configuration. (If the Base I/O address (if
address you want to use applicable):
for your network card --------------------
does not appear on the ROM address (if
list of valid addresses, applicable):
defer network --------------------
configuration until after DMA (if applicable):
installation.) See your --------------------
hardware documentation Base RAM address (if
for more information. applicable):
--------------------
RAM size (if
applicable):
--------------------
Local Ring Broadcast
(Token-Ring only):
--------------------
Slot number (if
applicable):
--------------------
Cable type (if
applicable):
--------------------
20. IP address --------------------
Four decimal numbers
separated by periods (for
example, 132.145.80.9).
If you do not already
have an IP address, defer
network configuration.
21. Network mask --------------------
If you are not
configuring a subnetwork,
accept the default value.
22. Broadcast address --------------------
23. Domain name service (DNS) Gateway address:
client configuration --------------------
Enter the IP address of --------------------
the gateway machine on Primary nameserver
your network to set the address:
default route. For more --------------------
information, see Chapter --------------------
5, ``Configuring Internet Secondary nameserver
Protocol (IP) routing'' address:
Enter the IP addresses of --------------------
the primary and secondary --------------------
name servers. Entering a
name server creates a
default resolv.conf(SFF)
file. For more
information, see Chapter
6, ``Configuring the
Domain Name Service''
These fields are
optional. If no values
are entered, /etc/tcp
does not add a default
route (although routed is
started) and resolv.conf
is not created.
24. IPX/SPX network number --------------------
Links DOS Workstation
clients and SCO
system software over the
NetWare network.
25. IPX/SPX internal network --------------------
number
26. IPX/SPX framing type --------------------
27. Video card --------------------
Also consult SCO's
Compatible Hardware Web
Pages.
28. Video mode --------------------
29. Video monitor --------------------
30. Graphical login [] On
If you plan to use the [] Off
graphical environment,
leave the graphical login
on. See ``Starting a
Graphical Environment
session''
31. Mouse Type (vendor):
Also consult your --------------------
hardware documentation. [] Bus mouse
For a bus mouse, specify [] IRQ2 (INTR2)
the interrupt. For a [] IRQ3 (INTR3)
serial mouse, specify the [] IRQ5 (INTR5)
COM1 port. If your [] Serial mouse:
serial mouse is connected COM1
to COM2, specify COM1 and (COM2 not
then reconfigure your supported)
mouse after installation [] Keyboard mouse
[] low
resolution
[] high
resolution
32. E-mail system [] MMDF
Choose sendmail if you [] sendmail
will use advanced
features of SCO Internet
Services, such as virtual
domains, or if your
systems currently use
sendmail. Otherwise,
choose MMDF. For more
information on sendmail
and the Internet Manager,
see Chapter 26,
``Configuring Internet
services'' For a detailed
comparison of sendmail
and MMDF, see the Mail
and Messaging Guide.
---------------------------------------------------------------- To: Press: ---------------------------------------------------------------- Get help <F1> Abort the installation <F2> Display other choices <Space> Restore defaults <F5> Return to the previous screen <Esc> Exit help screen <Esc> Move down one line <If you make an error while entering information:↓ > Move up one line <↑ > Scroll up one screen <PgUp> Scroll down one screen <PgDn> Select or deselect multiple items in a list <Space> Accept an item <Enter> Accept the current configuration <Enter>
To stop the installation, press <F2> in any window, or select q at a prompt to quit. Once you quit the installation, any information you have already entered is lost. You must start the installation again from the beginning.
To restart the installation, verify that the
Boot Disk is in the drive and press <Enter>.
At the Boot: prompt, press <Enter> again.
If you are using the BTLD utility and you need to
restart the installation, insert the Boot Disk and enter
restart link=pkg1 at the Boot: prompt
(where pkg1 is the name of the package from which to extract
the required BTLD drivers).
To stop the installation process after the software
loading begins, verify that the Boot Disk is in the
drive, then press the computer ``reset'' button or turn the
power off and on.
At the Boot: prompt, press <Enter> to
start the installation again from the beginning.
If you stop the installation after the software starts loading,
the previous system cannot reliably be restored.
If the previous system is not restored, the Upgrade
installation type and the Preserve disk layout option
may not be available in the restarted installation, even though
they were available in the first (aborted) installation.
Installing boot-time loadable drivers
If you are installing boot-time loadable drivers (BTLDs):
Boot: prompt.
Booting from CD-ROM
The SCO OpenServer installation CD-ROM is now bootable. This allows for
a faster installation and allows you to skip the steps which require you
to insert and load the installation boot floppy.
You can use this feature if your system BIOS supports CD-ROM as a boot option. You cannot use this feature if your system BIOS recognizes only a proprietary bootable CD-ROM format.
To use this feature:
For step 6, press <Enter> without inserting any additional media, unless you have a Boot Time Loadable Driver to install.
For step 7, you do not need to insert the CD-ROM as it is already present.
If you are using the bootable CD-ROM feature, assume that messages you receive that refer to installation media pertain to the CD-ROM drive.
The installation and upgrade procedure
Follow these steps, remembering to press <Enter> after responding to each prompt:
This is very important. If you do not gather this information first, you might have to stop the installation and start again from the beginning.
Press any key to reboot prompt,
insert the Boot Disk into the drive.
If you have more than one floppy disk drive, make sure the 3.5-inch drive is the primary drive (sometimes called the boot drive). Check your computer hardware manual if you are unsure which is the primary drive.
Boot: prompt.
Boot: prompt.
The installation starts again from the beginning.
If you are using the BTLD utility and you need to
restart the installation, insert the Boot Disk and enter
restart link=pkg1 at the Boot: prompt
(where pkg1 is the name of the package from which to extract
the required BTLD drivers).
Boot: prompt:
The system checks to see what hardware is present and if there are any hardware problems. Each stage of checking generates a letter ranging from D through M. See Appendix G, ``Kernel initialization check letters'' for an explanation of these letters.
A RESTRICTED RIGHTS LEGEND appears
after the kernel initialization letters.
Do not forget the root password. To restore a forgotten root password, you must contact your support provider for assistance.
If you encounter an error at this point, reboot the system and
start the installation again from the beginning.
Do not attempt to move backwards through the installation screens.
As the installation loads each software component onto the hard disk, you see messages such as:
Installing: SCO UNIX System V Operating system (Ver 5.0.5E) Installing Phase: Copying files from the media Installation Status: Copying fileThese messages are logged in the custom log file, /var/opt/K/SCO/SoftMgr/*/custom/custom.log, for future reference.
After the software is loaded, the kernel (/stand/unix) is rebuilt. This takes several minutes. The /stand directory also contains two other bootable kernels, to use in case unix will not boot. unix.safe is the same as unix, but with all third-party drivers removed. unix.install is the kernel used during installation. It contains most drivers. See ``Booting an old kernel'' and kernel(ADM) for more information.
Press any key to reboot.
Remove the floppy disk or bootable CD-ROM from the drive,
then press any key.
Boot: prompt, press <Enter>.
If you have a serial mouse that is not installed on COM1, configure it now. See Chapter 21, ``Adding serial and parallel ports'' and Chapter 22, ``Adding mice and bitpads''.
To install or remove software, see Chapter 4, ``Installing and managing software components''.
If you installed the ``Connectivity'' components
and deferred network configuration during initial installation,
you can configure the network now.
See
Chapter 1, ``Configuring network connections'' in Configuring Network Connections.
If you selected a full installation on your Enterprise or Desktop system, Netscape FastTrack server and Netscape Communicator were automatically installed. If you did not select a full installation, follow the instructions in Chapter 4, ``Installing and managing software components'' to install Netscape components. See the Release Notes for notes about configuring and using Netscape FastTrack and Netscape Communicator.
If you chose sendmail during installation, you can use the Internet Manager to configure your mail system and can make use of advanced features such as creating virtual domains. If you chose MMDF, you cannot use the Internet Manager to configure mail. You can switch mail systems by removing the SCO MMDF (MMDF) package and adding the SCO sendmail (SendMail) component. See Chapter 4, ``Installing and managing software components''. Also see ``Mail'' for information on configuring sendmail.
PPP from Morning Star allows you to use the Internet Manager to configure your dial-up connections. By default, PPP from Morning Star is not installed when you install your SCO OpenServer system. To install and use PPP from Morning Star, remove the SCO PPP (tcp:PPP) package and add the SCO PPP from Morning Star (mstppp) package, then configure connections with the Internet Manager. See Chapter 4, ``Installing and managing software components'', ``Accessing the network'', and Chapter 26, ``Configuring Internet services''.
INIT: SINGLE USER MODE prompt
by pressing <Ctrl>D.
(Or, from single-user mode, press <Ctrl>D at the
# prompt.
Then, when you see INIT: SINGLE USER MODE,
press <Ctrl>D again.)
As the system starts up, you see copyright credits, followed by
software component start-up messages.
When you see the graphical scologin screen on
tty02, or the login: prompt on tty01,
the system is ready.
To log in on a character screen, switch from the graphical login screen on tty02 by pressing <Ctrl><Alt><Fn> (where n is the function key associated with another tty, such as <F1>). Then, log in as root.
For more information about scologin, see ``Starting a Graphical Environment session'' and ``Using multiscreens'' in the System Administration Guide.
If your system should become corrupted, you can use this backup, along with the emergency boot floppy disk set that you create in the next step, to restore it without having to reinstall the software completely. See Chapter 3, ``Backing up filesystems'' in the System Administration Guide for a complete discussion of backups.
These disks allow you to recover your root filesystem quickly if it becomes so corrupted that you cannot start the system from your hard disk. See Chapter 5, ``Creating an emergency boot floppy disk set'' for instructions. Then, test the emergency floppy disk set, and verify that you can read the backup you made in the previous step according to the directions in ``Examining the contents of a backup'' in the System Administration Guide.
After installation
The SCO OpenServer system is now installed and registered.
Review Chapter 2 of the Release Notes for tasks you need to
complete immediately following installation.
For further information on administering the system,
see the remaining chapters in the SCO OpenServer Handbook (especially
Chapter 3, ``Troubleshooting the installation'',
Chapter 9, ``Administering SCO systems'',
and
Chapter 13, ``Troubleshooting system-level problems'').
Also see the System Administration Guide.
To help system administration, troubleshooting, and future upgrades go more smoothly, keep a copy of the completed installation checklist with the system log.
To configure Internet services, including the Netscape FastTrack Server,
sendmail, and ppp, refer to
Chapter 26, ``Configuring Internet services''
Choosing an upgrade path
Read this and the following sections on upgrading your
system thoroughly before beginning an upgrade installation.
They describe:
We recommend that you use cpio(C) format for the backups (the Backup Manager uses cpio), and that you back up one filesystem per tape.
If you currently run an earlier version of an SCO UNIX operating system, one or more of the following methods are available for you to upgrade to an SCO OpenServer system. Read the referenced sections and the Release Notes to decide which method works best for your system.
Before reinstalling your system, read the Release Notes for instructions on how to migrate your current Internet FastStart data. This information will help you save sendmail, ppp, and server configuration information so that you do not need to completely reconfigure these services.
See also:
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
See also
``Upgrading to the Enterprise configuration from Host or Desktop''.
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:
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.
User data retained on the root filesystem includes:
System data retained on the root filesystem includes:
If the list of hard disk setup options does not include Preserve, the installation could not find an active UNIX partition with a valid root filesystem and /etc/default/filesys. To preserve your existing partitions and filesystems, see ``About the Interactive disk setup option''. When using the Interactive fdisk/divvy option to retain your previous hard disk layout, you must assemble the hard disk layout information from your previous system before beginning the new installation.
The Preserve option is also available for the second
hard disk.
See
``Upgrading a non-primary hard disk''.
About the Interactive disk setup option
The disk setup option for Interactive fdisk/divvy
is available for any installation that starts as
a Fresh (rather than Upgrade) installation type.
Interactive fdisk/divvy defers disk setup until the end
of the installation prompts.
The installation then runs the utilities
fdisk(ADM)
and
divvy(ADM)
interactively.
To retain your previous partitions and divisions on the new system,
assemble the hard disk layout information from your
previous system (including any pre-existing DOS partitions)
before beginning the new installation, as follows:
Table 2-1 Primary Hard Disk Filesystems
-----------------------------------------------------
| Name| Type| New FS| #| First Block| Last Block|
|-----|------|--------|---|-------------|------------|
|-----|------|--------|---|-------------|------------|
The Interactive fdisk/divvy option is not available for the second
hard disk.
See
``Upgrading a non-primary hard disk''.
About other hard disk setup options
Other hard disk setup options available from Partitions & filesystems
(under Hard disk setup)
are Use whole disk for UNIX and Customize.
The Use whole disk for UNIX option clears any existing
partitions and divisions from your hard disk and creates a
default UNIX partition and division, which you cannot modify.
The Customize option clears any existing partitions
and divisions and creates the same default layout, then allows
you to modify it with new partitions and divisions.
(The Interactive fdisk/divvy option gives you more
precise control over the size and location of partitions
and divisions, but the Customize option is simpler.)
Neither of these options preserves previous data or disk setups.
If you select the Use whole disk for UNIX
or Customize option, you must
restore any previous data from backups after the installation
is complete.
The Use whole disk for UNIX and Customize options
are also available for the second hard disk.
See
``Upgrading a non-primary hard disk''.
Issues with any upgrade
This section covers issues that could potentially apply
to any upgrade, no matter what SCO system you are
upgrading from or what SCO OpenServer system configuration
you are installing.
Restoring user accounts
If the
upgrade path you choose
does not retain the user account profiles on your system, use
ap(ADM)
to preserve the account profiles.
Before beginning the installation, run:
ap -dg > filename
This copies the account profiles, including group membership information, of every user listed in the password file into the file filename. Back up this output file.
After completing the installation, copy the file filename
to the new system, and run:
ap -ro -ffilename
This restores the account profiles for every user, overwriting any
existing account profiles of the same name (including root).
User-configured files and directories
This is a list of files and directories that are often configured,
and may have changes that you need to restore after
installing a new SCO system.
(The Upgrade installation type attempts to
preserve configurable files.)
This list is not exhaustive, nor will every file on this
list have changes that you want to save.
The list is simply a starting-point for deciding which files
have important user-specific or system-specific information.
Files likely to be configured:
/etc/checklist /etc/inittab /etc/default/* /etc/mscreencap /etc/conf/init.d/* /etc/passwd /etc/cshrc /etc/profile /etc/ddate /etc/rc /etc/dialups /etc/systemid /etc/d_passwd /etc/termcap /etc/motd /etc/ttys /etc/gettydefs /etc/ttytype /etc/group /etc/wtmp users' home directories under /usr /usr/adm/hwconfig /usr/adm/messages /usr/adm/pacct /usr/lib/mail/aliases /usr/lib/mail/aliases.hash /usr/lib/mail/faliases /usr/lib/mail/maliases /usr/lib/mail/mailrc /usr/lib/mkuser/* /usr/lib/uucp/* /usr/lib/X11/app-defaults/* /usr/lib/X11/Mosaic/* /usr/lib/X11/scologin/Xservers /usr/lib/X11/system.mwmrc /usr/lib/X11/sys.startrc /usr/man/cat.LOCAL (local man pages) /usr/man/man.LOCAL (local man pages) /usr/mmdf/mmdftailor /usr/mmdf/table/*.dom (mmdf configuration) /usr/mmdf/table/*.chn (mmdf configuration) /usr/mmdf/table/alias* (mmdf configuration) /usr/spool/cron/crontabs (cron jobs) /usr/spool/lp/admins/lp/interfaces/* (printer scripts) /usr/spool/lp/pstatus /usr/spool/lp/qstatus /usr/spool/mail/* /var/opt/httpd/htdocs/* /.profile
You can protect any filesystems on a non-primary hard disk by selecting the Upgrade installation type or the Preserve option for setting up the secondary hard disk. If neither of these options is available, or if you do not select either one, select the Defer disk setup option during the installation, or remove the additional hard disks before beginning the installation.
If you select Preserve for the second hard disk, you must run divvy for that disk after the installation is complete. Within divvy, select n and name the preserved partitions, then exit. Then, run mkdev fs, as described in step 4.
Follow the numbered procedure in this section for any non-primary disk that you plan to remove before the installation, or for which you plan to select the Defer disk setup option.
Enter 1 at the main fdisk menu.
Record the numbers of the fdisk
partitions that hold your UNIX filesystems,
then exit fdisk.
Copy the information from your screen into the following table:
Table 2-2 Secondary Hard Disk Filesystems
-----------------------------------------------------
| Name| Type| New FS| #| First Block| Last Block|
|-----|------|--------|---|-------------|------------|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
|-----|------|--------|---|-------------|------------|
Exit divvy by selecting quit, then exit.
Select option 1 to add a new filesystem. When prompted, enter the full pathname of the device from /dev. For example, to add a filesystem called u, enter /dev/u.
When prompted, enter the name of the directory on which the
filesystem is mounted.
For example, a filesystem called u is usually mounted on
the directory /u.
Specify how you want the filesystem mounted when the system enters multiuser mode:
When asked whether or not users will be allowed to mount the filesystem, it is usual to respond n for security reasons. (In any case, users running backups must have both sysadmin and backup authorizations. See ``Assigning subsystem authorizations'' in the System Administration Guide.)
Exit mkdev fs.
If the kernel does not link at the end of installation, try to boot from the kernel called /stand/unix.safe (which does not contain the third-party drivers), into single-user mode.
If the driver for the root hard disk controller is
one of the third-party drivers missing,
the unix.safe kernel will not boot.
If this happens, boot the system using
a boot-time loadable driver (BTLD) for this
SCO OpenServer system.
Then, remove the old driver from the link kit, and
install the BTLD using
installpkg(ADM).
Upgrading SCO OpenServer Development System
When you upgrade to SCO OpenServer Release 5.0.6,
we recommend that you upgrade to the corresponding SCO OpenServer Development System release
(5.1.1) as well.
Earlier versions of the SCO Development System are not
supported, and may behave unpredictably.
The Development System is not automatically upgraded when you upgrade the SCO OpenServer system. After you complete the operating system upgrade, use the Software Manager to install the new version of the SCO OpenServer Development System. Supply the license information from the Development System's own Certificate of License and Authenticity, which is included in the SCO OpenServer box.
If you do choose to run an earlier version of the SCO
Development System, you must reactivate it after upgrading to
SCO OpenServer Release 5.0.6.
The instructions for reactivating the Development System
are displayed when you invoke the /bin/cc, /bin/rcc,
or /usr/bin/CC command.
Upgrading from release 5.0
This section covers issues that may arise
when upgrading from SCO OpenServer Release 5.0.0, 5.0.2, 5.0.4, or 5.0.5 to SCO OpenServer Release 5.0.6.
See also:
When a directory directory_name is moved, it is renamed directory_name#. (If a directory called directory_name# already exists, sufficient number signs are appended to the directory's original name to create a unique name, such as directory_name##.) For example, if /tcb/files/audit contained user-created files before an upgrade that you cannot find there after the upgrade, check whether a directory exists called /tcb/files/audit#. If so, you can return your files to the upgraded /tcb/files/audit directory.
Third-party products and system serial numbers
Some third-party applications that are run after a system has been upgraded may find that the serial number of the installation is not the same as the one under which the application was originally installed.
The installation tries to rebrand the
new kernel with the old serial number during an upgrade.
If this does not work, rebrand the kernel with the serial
number of a previous release using the command:
brand -n old_serial_number old_activation_key /etc/conf/pack.d/kernel/os.a
Then, relink the kernel and reboot the system.
Upgrading to the Enterprise configuration from Host or Desktop
If you purchased an upgrade for one of the following
scenarios, the upgrade requires a two-step procedure:
The first step upgrades the system to SCO OpenServer Release 5.0.6 in the same configuration, and the second step upgrades the system to SCO OpenServer Enterprise System.
The first step happens automatically when you choose the Upgrade installation option. Use the license information from the previous (5.0.0, 5.0.2, 5.0.4, or 5.0.5) Certificate of License and Authenticity (COLA) for this step.
To complete the second step, follow the instructions in Chapter 4, ``Installing and managing software components'' to invoke the Software Manager and install the SCO OpenServer Enterprise System. When prompted, supply the license information from the 5.0.6 COLA.
After you install the SCO OpenServer Enterprise System, exit the Software Manager and reboot the system.
When you upgrade an SCO OpenServer Release 5.0.6 Desktop System to an Enterprise System, anonymous ftp will no longer work if it was configured before. This is because the Enterprise System functionality that enables ``virtual domains'' prevents the ftp server from recognizing existing anonymous ftp user information.
To re-enable anonymous ftp in this environment:
ftp:x:20:50:anonymous ftp account:/usr/internet/ip/0.0.0.0/sco_ftp:/bin/shThe ftp account entry must be on one line.
If you upgrade the system within the SCO OpenServer family (for example, from Host to Enterprise), you must also install the appropriate language support product in the usual way, after the upgrade.
Ideally, do not install language products until after an upgrade.
IPX/SPX upgrades overwrite *_tune.h files
An Upgrade installation to an SCO OpenServer Desktop System or Enterprise System
does not automatically upgrade the files
ipx_tune.h, nvt_tune.h, and spx_tune.h.
Instead, during the installation, the files get saved to
/usr/lib/ipxrt/saved_config.
If you have made changes to these files that you want to preserve,
compare them with the newly-installed
versions after the upgrade, and make any necessary changes to
the new files.
Upgrading SCO Merge
SCO Merge is not automatically upgraded when you install
SCO OpenServer Release 5.0.6.
If you have been running SCO Merge under SCO OpenServer Release 5.0.0, 5.0.2,
5.0.4, or 5.0.5 and you select the Upgrade installation type for
Release 5.0.6, SCO Merge will not be disturbed.
If you select a Fresh installation for Release 5.0.6,
use the
Software Manager
to install the latest release of SCO Merge from the SCO Optional Services
CD-ROM.
Supply the license
information
provided in a file on the same CD-ROM.
Additional product documentation unavailable after upgrades
If you perform an Upgrade installation on a system that has additional
products installed (such as SCO Merge, SCO Advanced File and Print Server, or SCO OpenServer Development System),
the documentation for these products is unavailable unless the
additional products are upgraded as well.
(This does not apply to manual pages.)
To retain
the documentation for the older versions, you must remove the
documentation package for each product and re-install it on the
upgraded system from the original media.
Upgrading from release 3.0
There are no specific issues to consider when upgrading from
SCO Open Desktop Release 2.0 to SCO OpenServer Release 5.0.6.
Make sure you read
``Issues with any upgrade''
and the Release Notes before beginning the installation.
The material in
``Upgrading from release 5.0''
may also apply to systems running Release 3.0.
Upgrading from release 2.0
There are no specific issues to consider when upgrading from
SCO Open Desktop Release 2.0 to SCO OpenServer Release 5.0.6.
Make sure you read
``Issues with any upgrade''
and the Release Notes before beginning the installation.
The material in
``Upgrading from release 5.0''
may also apply to systems running release 2.0.