System files subject to migration fall into two categories:
In addition to describing tools and precedures, this guide also includes as much orientation material as possible in the form of appendices. These contain information to orient the administrator in the UnixWare 7 environment, with more detailed explanations of differences between the two platforms.
Although both platforms support similar features, certain implementations are different and migration is not possible:
The SCO OpenServer Release 5 version of cpio(1) is available on UnixWare 7, allowing you to restore archives created with the Backup Manager under SCO OpenServer Release 5. This command is intended for you to be able to restore cpio archives from an SCO OpenServer Release 5 system and should not be used to make UnixWare 7 backups.
To restore an SCO OpenServer Release 5 backup on UnixWare 7 using cpio(1):
Where /dev/ctape1 is the path to your tape device.
You can select specific files and directories by adding them to
the end of the command. If, for example, you wanted to restore
the /tmp/hold/time file, you would type:
cpio -iAmudB -I/dev/ctape1 tmp/hold/time
Should you want to restore an entire directory, for example, /tmp/hold you would type:
cpio -iAmudB -I/dev/ctape1 tmp/hold/*
To list the files on a backup:
cpio -iABmudq -I /dev/ctape1 \*
ARCserveIT v6.6.0 for UnixWare 7 release 7.1x is able to retrive data backed up with ARCserve/Open from Cheyenne from a previous SCO OpenServer Release 5 system. ARCserveIT includes several upgrade utilites which allow you to migrate your existing ARCserve/Open databases and Auto Pilot jobs.
To restore your ARCserve/Open backup session with ARCserveIT:
For more information on using ARCserveIT, please see the online ARCserveIT documentation.
The ap (account profile) utility is supported on both platforms Should you need to gather accounts from multiple systems or routinely copy accounts across platforms, you can do it more simply using ap.
On a UnixWare 7 system, ap gathers account information from the /etc/passwd file and the I&A database. On an SCO OpenServer Release 5 system, ap gathers account information from the /etc/passwd file and the Protected Password database. Irrelevant information about the user (including unsuccessful login attempts, unsuccessful password changes, and the location and time of the last login) is not included in the profile.
To create a complete archive of your present users, log in as root
and enter this command:
ap -d -v > profile.acct
To archive a subset of accounts, simply include a list as in this example:
ap -d -v > nathanb mavrac sergeo renard > profile.acct
You can also preserve the group membership information for each account using the -g (with either of the above commands).
Using the profile.acct file saved from your SCO OpenServer Release 5 system, you can later load the accounts on your UnixWare 7 system with the restore option of the .ap(1M) command.
Because long passwords are supported in different ways in SCO OpenServer Release 5 and UnixWare 7, there are two ways that you can create a user account from the profile depending on how you want to handle user accounts that have long passwords.
The first method truncates long passwords to 8 characters. Enter the
following command:
ap -r -f profile.acct usernames
If you do not specify any usernames, all accounts stored in profile.acct are copied to the system.
The new accounts should now be in place and ready for use. The ap command will warn you if any passwords had to be truncated. Instruct these users to only enter the first 8 characters of their password when they first log in. They will also be required to change their password at this time.
The second method allows you to specify a password using
the -p option:
ap -r -f profile.acct -p password usernames
(Again, usernames is optional.)
All user accounts with passwords longer than 8 characters will be
assigned the same password. These users are
prompted to change their password when they first log in. For
example, if the users nathanb and mavrac
both had passwords longer than 8 characters, the following
command would set their login password to ``Global1'':
ap -r -f profile.acct -p Global1
Other accounts present in the file with short passwords are unaffected.
If you want users to have different initial passwords, invoke one command for each user.
For the most part, your hardware devices will be configured automatically when you install UnixWare 7. If an adapter, bus card, data port, or peripheral is not recognized after the installation, use the information in this topic to configure your hardware.
UnixWare 7 provides a set of SCOadmin managers similar to those available on SCO OpenServer Release 5. For differences between UnixWare 7 configuration interfaces and those provided with SCO OpenServer Release 5, see ``Understanding the UnixWare 7 platform''.
The UnixWare Device Configuration Utility (DCU) has been added to SCOadmin. You will use this interface to display and modify device-specific configuration parameters for many devices that are stored in an in-core database. The DCU is particularly useful for detecting and resolving conflicts between configured devices, determining free parameter values when adding ISA (Industry Standard Architecture) hardware that is not auto-detected or auto-configured, and configuring ISA device controllers.
For more information, consult ``Using the Device Configuration Utility (DCU)'' in the UnixWare 7 online documentation.
Use the Audio Configuration Manager to add and configure sound cards. You can play and record audio files with the scosound(X1) utility.
For more information, see ``Configuring audio adapters'' in the UnixWare 7 online documentation.
Use the SCOadmin Printer Setup Manager to add and modify printers.
For more information, see ``Managing the print service'' in the UnixWare 7 online documentation.
Use the Network Configuration Manager to configure LAN network adapter drivers, and LAN and WAN protocols.
For more information, see ``Configuring network hardware'' in the UnixWare 7 online documentation.
Use the Modem Configuration Manager to:
For more information, see ``Configuring modems'' in the UnixWare 7 online documentation.
While ISDN modems are configured with the Modem Configuration Manager, ISDN bus adapters are configured with the Network Configuration Manager.
Use the Serial Manager to configure individual serial ports. If the ports do not appear to be recognized, run the DCU.
For more information, see ``The Serial Manager'' in the UnixWare 7 online documentation.
Use the Device Configuration Utility (DCU) to add support for tape, CD-ROM, and hard disk drives which were not auto-detected during the installation process.
UnixWare 7 disk tools are discussed in ``The UnixWare 7 disk subsystem''. for more information.
Use the PnP Configuration Manager to enable Plug and Play devices that are not recognized by other managers; for example:
For more information, see ``Configuring Plug and Play devices'' in the UnixWare 7 online documentation.
Most tape drives supported on SCO OpenServer Release 5 can be used on UnixWare 7, but some floppy-tape (QIC-80) devices may not be supported.
If your SCO OpenServer Release 5 system includes ARCserve/Open 2.2 from Cheyenne, you may be able to migrate your database to operate with ARCserveIT 6.6. For more information, please see the online ARCServeIT documentation.
For more information, see ``Adding tape drives'' in the UnixWare 7 online documentation.
UnixWare 7 supports a large number of video adapters including those supported under SCO OpenServer Release 5. In addition, UnixWare 7 provides the vesa X server driver. This generic driver can operate any new video card that honors the VESA BIOS interface, and is useful in supplying high resolution support to video cards that do not have a specific accelerated driver. For more information on this feature, including performance implications, see SCOhelp on your installed UnixWare 7 system.
Most video adapters are automatically configured when you install your UnixWare 7 system. However, you should record your video configuration from your previous operating system in case:
The display at the top of the screen lists the name of the adapter, any configured monitor, and the resolution.
Record this information, then (if auto-detection or auto-configuration fails) use it to configure your adapter on UnixWare 7 using the SCOadmin Video Configuration Manager.
If you install your UnixWare 7 system and find that your video adapter is incorrectly configured, or you want to modify configuration, try the following.
To run your system in a safe video mode
Enter /usr/bin/X11/setvideomode -stdvga. This This sets IBM VGA 640x480-16 mode, which is almost always safe for any adapter.
To restore the adapter's default configuration
Enter /usr/bin/X11/setvideomode -default. Do this if initial auto-configuration worked well enough to get the video working, but you manually configured the adapter to a different setting and lost the use of the video adapter.
This -default option restores the settings to initial auto-configuration defaults.
To determine the video adapter in the system
Enter /usr/bin/X11/VideoHelp.
This command lets you know what video adapter is present on your system.
The following topics are discussed here:
Configuration of network interface hardware in UnixWare 7 can be done at install time (for one network adapter only), or it can be performed at a later time by using the Network Configuration Manager as in SCO OpenServer Release 5.
Note the configuration details of the network adapter hardware (IRQ, I/O address range, memory address range, DMA channel) in your system so that you can configure your UnixWare 7 system with these values. For SCO OpenServer Release 5, note the details displayed by the Network Configuration Manager.
In UnixWare 7, TCP/IP is configured over a network interface using the Network Configuration Manager as in SCO OpenServer Release 5. You should note the hostname, domain name, IP address, netmask, broadcast address and frame type of the existing network interfaces so that you can configure these on your UnixWare 7 system. To obtain these values, run the Network Configuration Manager.
You may need to copy over the file /etc/hosts from the SCO OpenServer Release 5 system. This contains information about the hostnames and IP addresses of localhost and other systems. It is recommended that you merge this information with the existing /etc/hosts file to avoid accidentally removing the localhost entry.
You may also need information from the /etc/tcp file on an SCO OpenServer Release 5 system such as the IP address of a statically configured default router. Look for an entry such as:
/etc/route add default gateway
The /etc/tcp file on an SCO OpenServer Release 5 system contains information about which TCP/IP services should be configured in the /etc/inet/config file on your UnixWare 7 system. The /etc/inetd.conf file will also show what services were available through the inetd daemon. Again, you should only consult this file so that you can amend the /etc/inetd.conf file on your UnixWare 7 system. (Note that UnixWare 7 is bundled with TCP Wrappers which allow you to control who can access the services listed in /etc/inetd.conf.)
If you configured the Dynamic Host Configuration Protocol (DHCP) or the Address Allocation Server (AAS) on your SCO OpenServer Release 5.0.4 system, you can migrate their daemon configuration files, /etc/inet/dhcpd.conf and /etc/inet/aasd.conf, to UnixWare 7. Both will work without additional modification.
DHCP and AAS were not available on previous versions of SCO OpenServer Release 5.
This section discusses differences between UnixWare 7 and SCO OpenServer Release 5, and how the upgrade of routing may be accomplished.
UnixWare 7 contains updated gated and routed daemons (named in.gated and in.routed) and an updated route command. Both gated and routed support RIP Version 1 and Version 2, and router discovery. The separate router discovery daemon, irdd, that was available in SCO OpenServer Release 5 does not exist in UnixWare 7.
The release of gated in UnixWare 7 is similar to the version in SCO OpenServer Release 5.
gated in UnixWare 7 supports RIPv1, RIPv2, OSPFv2, EGPv2, BGPv2-v4, and router discovery.
Updated support commands for gated in UnixWare 7 include gdc, ripquery and ospf_monitor.
routed in UnixWare 7 supports RIPv1, RIPv2, and router discovery. routed in SCO OpenServer Release 5 only supported RIPv1. A new support command, rtquery, allows you to query routing daemons in the manner of ripquery. Additionally, it provides additional control over routed, by allowing you to raise or lower the trace level for debugging.
gated conforms to the RFCs shown in the following table:
| SCO OpenServer Release 5 | UnixWare 7 | Description | |
|---|---|---|---|
| RFC 891 | Yes | Yes | DCN local network protocols |
| RFC 904 | Yes | Yes | EGP specification |
| RFC 911 | Yes | Yes | EGP gateway |
| RFC 1058 | Yes | Yes | RIPv1 specification |
| RFC 1163 | RFC 1267 | RFC 1267 | BGP specification |
| RFC 1164 | RFC 1268 | RFC 1268 | BGP application |
| RFC 1253 | Yes | Yes | OSPFv2 MIB |
| RFC 1256 | Yes | Yes | Router discovery |
| RFC 1267 | Yes | Yes | BGP-3 specification |
| RFC 1268 | Yes | Yes | BGP-3 application |
| RFC 1269 | Yes | Yes | BGP-3 managed objects |
| RFC 1389 | Yes | Yes | RIPv2 MIB RFC 1403 |
| Yes | BGP OSPF interaction | ||
| RFC 1583 | Yes | Yes | OSPFv2 specification |
| RFC 1723 | Yes | Yes | RIPv2 specification |
| SCO OpenServer Release 5 | UnixWare 7 | Description | |
|---|---|---|---|
| RFC 1058 | Yes | Yes | RIPv1 specification |
| RFC 1256 | Yes | Router discovery | |
| RFC 1723 | Yes | RIPv2 specification |
UnixWare 7 does not provide a graphical manager for configuring routing. However, the Network Client Manager does include support for the traceroute and ping.
You can use the Network Configuration Manager to configure a default router.
In UnixWare 7 all routing configuration files are located in /etc/inet, rather than in /etc as in SCO OpenServer Release 5.
Configuration files are:
For gated, changes are required to /etc/inet/gated.conf. Some keywords recognised by gated in SCO OpenServer Release 5 have changed and affect the default behavior. In particular, a new aggregate keyword may be required as route aggregation was always enabled in SCO OpenServer Release 5. Additionally, more extensive tracing is provided; see gated.conf(4tcp) for further details).
The gdc checkconf command is useful for checking the integrity of the gated.conf file. It should be run in multi-user mode (that is, with networking running). Otherwise, it will be unable to pick up valid network interfaces to use.
For routed, the /etc/inet/gateways configuration file supports many more command keywords. In particular, the no_rdisc keyword can be used to disable router discovery (enabled by default). See routed(1Mtcp) for details.
The gdc and rtquery commands provide the ability to dump a snapshot of the routing daemon's routing table and interface list to a log file for debugging purposes.
The files /var/adm/syslog and /var/adm/log/osmlog are used to log messages by default.
UnixWare 7 is shipped with a version of BIND that includes a number of bug fixes, security fixes security fixes and new features over versions of BIND that shipped with SCO OpenServer Release 5.
DNS may be configured using the DNS Manager. However, if you migrate configuration files from SCO OpenServer Release 5, the DNS Manager may not be able to understand their structure or naming conventions. In this case, you must edit the files yourself.
The file /etc/named.boot must be relocated as /etc/inet/named.boot. Similarly, any configuration files in the /etc/named.d hierarchy should be relocated below /etc/inet/named.d. You may also need to edit the files to correct any pathnames such as those specified by the directory directive. You do not need to copy over the cache hints file (see root.cache(4tcp)) as one is provided with the system (/etc/inet/named.d/db.cache). If necessary, you can use the DNS Manager to update this file.
Remove any hostresorder line in the resolver configuration file, /etc/resolv.conf. In UnixWare 7, name resolution order and methods are controlled using entries in /etc/netconfig. It is recommended that you do not edit this file directly. Use the Network Client Manager to configure entries in this file.
The recommended upgrade path is to use the DNS Manager to configure a caching-only nameserver.
Next, configure any zones that the system serves as a primary name server. Use the ndc restart command to restart named. Check the contents of /var/adm/syslog and /var/adm/log/osmlog for any named errors. You may notice that hostnames containing an underbar (``_'') character are logged as this is an illegal character for an Internet hostname. You should rename these hosts if possible.
Finally, configure any zones that the system serves as a secondary or stub name server and restart named. Check the logs again and check that the zone data has been written to the correct files.
The interpretation of a decimal point in the SOA serial number has changed. Previous versions of BIND would interpret 1.234 as 1000234 instead of 1234. The recommended serial number format is YYYYMMDDNN where YYYY is the year, MM is the month (01-12), DD is the day (01-31), and NN is the serial number of the change during that day (00-99) This allows you to make 100 changes a day until the year 4294.
The version of NIS in UnixWare 7 is based on that in SCO UnixWare 2.1. shipped. NIS in UnixWare 7 does not support the copy-only servers that could be configured in the SCO OpenServer Release 5 version of NIS.
NIS may be configured using ypinit. Alternatively, you can use the Network Client Manager to configure a NIS client.
In UnixWare 7, NIS files are located in the /var/yp hierarchy rather than in the /etc/yp hierarchy used in SCO OpenServer Release 5.
NIS master and slave servers
should set up /etc/passwd and /etc/group
files using the Account Manager as normal
but the copies of these files that are used to generate
the corresponding NIS maps can be located elsewhere
if the DIR variable is redefined in /var/yp/Makefile.
Run ypinit with the appropriate option
on all systems that need to use NIS:
For SCO OpenServer Release 5 users, there are new APIs, dials(3N) and cs_connect(3N), which are used to dial out to remote systems. The SCO OpenServer Release 5 modem dialers (based on atdialer) have been carried forward to UnixWare 7. This allows for the configuration of over 900 different modems.
UnixWare 7 includes support for ISDN BRI adapters and call service handling. Both of these features are proprietry to SCO.
To configure entries for modems and ISDN adapters in the /etc/uucp/Devices file, use the Hardware menu under the WAN view of the Network Configuration Manager.
To configure call services and filters defined in the files /etc/ics/Callfilter and /etc/ics/Callservices, select Call Services->Incoming in the WAN view of the Network Configuration Manager.
To configure entries for remote systems in the /etc/uucp/Systems file, select Call Services->Outgoing in the WAN view of the Network Configuration Manager.
For SCO OpenServer Release 5, the following files should be moved to /etc/uucp:
The Devices file may need modifying to reflect the device naming scheme used by UnixWare 7. See ``Serial device node naming conventions'' the UnixWare 7 online documentation for details.
The ftp servers in SCO OpenServer Release 5 and UnixWare 7 are based on the Washington University ftp server, wu-ftpd. The UnixWare 7 version is based on version 2.4. It includes additional features and many bug fixes compared to the SCO OpenServer Release 5 version.
The ftp servers in SCO OpenServer Release 5 and UnixWare 7 conform to RFC 959 and RFC 1123.
The ftp server in UnixWare 7 may be configured using the ftp Server Manager.
The following files need to be migrated from SCO OpenServer Release 5:
Any user names added to the SCO OpenServer Release 5 or /etc/ftpusers file should be added to the UnixWare 7 /etc/ftpusers file in order to continue to deny access to those users.
Any shells added to the SCO OpenServer Release 5 /etc/shells file should be added to the UnixWare 7 /etc/shells file in order to continue to allow access to a user who has one of those shells as their login shell. The pathnames of some entries may need changing to match the location of the shell in the filesystem hierarchy of UnixWare 7.
Any conversions added to the SCO OpenServer Release 5 /etc/ftpconv file should be added to the UnixWare 7 /etc/ftpconversions file, changing the pathname of the conversion utility where appropriate.
The syntax of some entries in /etc/ftpaccess has changed:
NFS in UnixWare 7 and SCO OpenServer Release 5 is based on Version 2. Configuration of NFS and the automounter in UnixWare 7 is substantially different from SCO OpenServer Release 5.
NFS in UnixWare 7 does not include the spongy mount or transport over TCP features of NFS in SCO OpenServer Release 5.
automount in SCO OpenServer Release 5 automatically consults the NIS auto.master map unless the -m option is specified on the command line. It does not consult the /etc/auto.master file unless this is also specified using the -f option. automount in UnixWare 7 reads the /etc/auto.master file unless you override the pathname using the -f option. It does not consult the NIS auto.master map unless the following line is included in the /etc/auto.master file on the client:
+auto.master
A filesystem is made available for mounting by NFS clients by
adding
share(1Mnfs)
entries to the /etc/dfs/dfstab file. You can invoke the entries
in this file by executing the following command:
. /etc/dfs/dfstab
You can mount NFS filesystems on NFS clients using the Filesystem Manager.
The following table shows approximate equivalences between NFS configuration files in SCO OpenServer Release 5 and UnixWare 7:
| SCO OpenServer Release 5 | UnixWare 7 | Description |
|---|---|---|
| /etc/default/filesys | /etc/vfstab | Used by client to define filesystem to be mounted |
| /etc/exports | /etc/dfs/dfstab | Used by server to define filesystems that clients can mount |
| /etc/auto.master | /etc/auto.master | Lists initial automount configuration. The information may also be obtained as a map from an NIS server |
|
/etc/auto.direct
/etc/auto.indirect | /etc/auto.home | List direct and indirect automount configuration. The information may also be obtained as map(s) from an NIS server |
| exec | noexec |
| trunc | notrunc |
| tcp | spongy |
The information in the /etc/exports file can be added to /etc/dfs/dfstab as follows:
pathname -options # commentChange each line so that it has the following format:
share -Fnfs -o "options" [-d "comment"] pathnameThe description specified by the -d option is optional. The access option in SCO OpenServer Release 5 is not supported by UnixWare 7. Replace each access option with ro (read-only) or rw (read and write) to define the read permissions for each client explicitly. Note that netgroup entries are supported. For example, consider the following lines in a copy of the /etc/exports file from an SCO OpenServer Release 5 system:
/usr -access=clients #export to netgroup clients /usr/local #export to the world /usr2 -access=hermes:zip:tutorial #export to only these machines /usr/sun -root=hermes:zip #give root access only to these /usr/new -anon=0 #give all machines root access /usr/bin -ro #export read-only to everyone /usr/stuff -access=zip,anon=-3,ro #several options on one lineThis would be converted to:
share -Fnfs -o "rw=clients" /usr share -Fnfs -d "export to the world" /usr/local share -Fnfs -o "rw=hermes:zip:tutorial" /usr2 share -Fnfs -o "root=hermes:zip" /usr/sun share -Fnfs -o "anon=0" /usr/new share -Fnfs -o "ro" /usr/bin share -Fnfs -o "rw=zip,anon=-3,ro" /usr/stuff
SCO OpenServer Release 5 included version 3.2 of NTP and UnixWare 7 includes version 3.5f of NTP. These conform to RFC 1305 and retain compatibility with RFC 1119 and RFC 1059.
NTP clients may be configured using the Network Client Manager.
NTP servers are configured by editing the file /etc/inet/ntp.conf. Configuration of NTP servers does not differ substantially between SCO OpenServer Release 5 and UnixWare 7 except for the following points:
The default NTP configuration file in SCO OpenServer Release 5 is /etc/ntp.conf. The default NTP configuration file in UnixWare 7 is /etc/inet/ntp.conf. In addition, you will need to copy over files containing authentication keys. You should also create any log files such as those used for writing drift measurements and other statistics. The pathnames of these files will be defined in the ntp.conf file.
IPX/SPX in SCO OpenServer Release 5 is based on NWU Version 3.1. IPX/SPX in UnixWare 7 is based on Netware 4.10a.
UnixWare 7 supports NetWare over IP (NWIP) by tunneling IPX/SPX packets over IP. At least one NetWare server must be configured to run as a Domain SAP/RIP Server (DSS). See ``NWIP configuration parameters'' the UnixWare 7 online documentation for details. for more information.
Use the Network Configuration Manager to configure IPX/SPX. Using nwcm or editing the configuration files by hand is not recommended.
From SCO OpenServer Release 5, configuration information in the file /etc/ipx.d/NPSConfig may need to be migrated.
The information in these files should be migrated to /etc/netware/nwconfig on your UnixWare 7 system.
The configuration file /etc/netware/nwconfig contains configuration information for all NetWare components including the IPX/SPX stack. This section refers only to IPX/SPX stack configuration.
The contents of the SCO OpenServer Release 5 configuration file /etc/netware/nwconfig differ significantly from the file /etc/ipx.d/NPSConfig in UnixWare 7.
lan_N_adapter = "/dev/netn"
The version of NetBIOS in UnixWare 7 is based on the in-kernel NetBIOS in SCO OpenServer Release 5 with the following enhancements:
NetBIOS in UnixWare 7 is not configurable using the Network Configuration Manager. It is necessary to edit the file /etc/inet/nb.conf instead. However, as the default behavior of NetBIOS is to run over all available interfaces, this is not usually necessary unless you want to configure name resolution via nominated WINS servers.
The only NetBIOS file that needs to be migrated is /etc/default/netbios to /etc/inet/nb.conf.
There are several differences in the parameters that can be configured in /etc/default/nbconf and /etc/inet/nb.conf. The following parameter has been enhanced for UnixWare 7:
The following parameters are no longer valid in UnixWare 7:
PPP has changed extensively in UnixWare 7. It supports the following new features:
Most of the PPP configuration files in SCO OpenServer Release 5 are replaced by a single file that should not be edited manually. The contents of the file may be changed using the PPP Manager or the ppptalk(1M) command. You can also use the PPP Internet Connection Manager to set up simple outgoing PPP configurations.
Pools of available IP addresses may be configured using the Address Allocation Manager in UnixWare 7. The UUCP Systems and Devices files may be configured from the WAN view of the Network Configuration Manager. Packet filter definitions may be configured using the Packet Filter Manager.
The following table shows the equivalence between SCO OpenServer Release 5 PPP configuration files and data definition statements that are internal to ppptalk in UnixWare 7:
| Feature configured | SCO OpenServer Release 5 file |
UnixWare 7
definitions |
|---|---|---|
| PPP endpoints | /etc/inet/ppphosts |
bundle
link protocol |
| Authentication database | /etc/inet/pppauth | auth |
| Third-party framing drivers | /etc/pppstack | |
| link | ||
| IP address pool | /etc/ppppool | protocol |
| Packet filters | /etc/pppfilter | protocol |
| ppphosts parameter | ppptalk parameter | ppptalk definition |
|---|---|---|
| accm | accm | protocol = lcp |
| attach | bundle_tag | bundle |
| auth | protocol | auth |
| authtmout | authtmout | bundle | global |
| bypassframing | No equivalent | |
| clocal | No equivalent | |
| conf | maxcfg | protocol = ccp | ip | lcp |
| debug | debug | bundle | link | protocol |
| filter |
bringup
keepup passin passout | protocol = ip |
| flow | flow | link |
| forcefarip | peeropt = force | protocol = ip |
| forcenearip | localopt = force | protocol = ip |
| getfarip | peeropt = any | protocol = ip |
| getnearip | localopt = any | protocol = ip |
| idle | maxidle | bundle |
| local | localaddr | protocol = ip |
| mask | netmask | protocol = ip |
| maxslot | vjmaxslot | protocol = ip |
| mru | mru | protocol = lcp |
| nak | maxfail | protocol = ccp | ip | lcp |
| name | peerauthname | bundle | global |
| noaccomp | acfc = no | protocol = lcp |
| noslotcomp | vjslotcomp = no | protocol = ip |
| noipaddr |
localopt = any
peeropt = any | protocol = ip |
| nomgc | magic = no | protocol = lcp |
| noprotcomp | acfc = no | protocol = lcp |
| novj | vjcompress = no | protocol = ip |
| old | No equivalent | |
| providefarip | peeropt = prefer | protocol =ip |
| providenearip | localopt = prefer | protocol =ip |
| proxy | proxyarp | protocol = ip |
| remote | peeraddr | protocol = ip |
| reqtmout | reqtmout | protocol = ccp | ip | lcp |
| retry | No equivalent | |
| rfc1172addr | No equivalent | |
| sh_hook | exec | protocol = ip |
| speed | No equivalent | |
| staticdev | dev | link |
| term | maxterm | protocol = ccp | ip | lcp |
| uucp | remotesys | bundle |
It is not feasible to migrate the PPP configuration files from SCO OpenServer Release 5 to UnixWare 7. You should make backup copies of the files, and refer to these for configuration information when setting up PPP on your UnixWare 7 systems.
SCO OpenServer Release 5 and UnixWare 7 contain different mail transport systems with different methods of configuration. However, the feature sets are similar and most features do migrate easily. This topic discusses those features that feature prominently in the GUI or character based configuration tools.
Mail folder formats are completely backwards-compatible from UnixWare 7 so folders can be imported with ease.
The following major areas are addressed here:
SCO OpenServer Release 5 user inboxes are located in /usr/spool/mail, and in /var/mail in UnixWare 7. There is a symbolic link to /usr/spool/mail from /var/mail, and it is therefore sufficient to copy these files to the new machine. No data conversion of these files is required.
Using the Mail Manager to change the inbox location to the users' home directories, change the ``Users' INBOX Location'' setting (within the ``Folder Configuration'' category) to the appropriate setting.
SCO OpenServer Release 5 supports two mail transport agents: MMDF and sendmail. Preserving these configurations is described separately:
UnixWare 7 sendmail has been modelled after MMDF to make the transition easier: even advanced features such as the domain table and channel support are supplied. Not all of these are covered in this topic, but after you become familiar with the UnixWare 7 sendmail configuration, it should become clear how to port even advanced MMDF configurations to UnixWare 7 sendmail.
The primary screen of the SCO OpenServer Release 5 MMDF Configuration Manager allows you to configure the host name, enable SMTP and UUCP, enable domain hiding, and enable or disable the name service methods.
The UnixWare 7 Mail Manager enables UUCP by selecting the Settings->UUCP Enable/Disable menu option.
The additional options under ``Forwarding'' in the MMDF Configuration Manager are as follows:
The ``Redirection'' option in the MMDF configuration calls up the aliases editor. The same functionality exists in UnixWare 7 and is accessed by opening the ``Alias Files and Maps'' category and selecting the alias file entry. Then select the ``Edit'' facility in the dialog box and the alias editor is started for the system-wide mail alias file.
SCO recommends importing alias files rather than typing in the aliases by hand into the alias editor.
The sendmail configuration is obtained and/or modified by running mkdev cf on SCO OpenServer Release 5. It contains several options, each of which is described here. In addition, SCO OpenServer Release 5 sendmail supports some MMDF features, notably configurable INBOX location which is also described here.
This feature is enabled by using the Settings->UUCP Enable/Disable menu option to enable the UUCP channel. Then edit the ``Forward all mail to'' entry in the UUCP channel to add the UUCP gateway name.
Note that, if the UUCP gateway is on the Internet, you would use the same strategy with a custom SMTP channel (that is, leave the DNS one alone, and create a new one for this option). To do this, create a new channel with channel program as SMTP, table type as UUCP Systems file, and the channel name something like uucpgate. Then edit the ``Forward all mail to'' option to point to the UUCP gateway.
This feature can be be duplicated on UnixWare 7 by configuring the default SMTP channel to have the ``Forward all mail to'' option pointing at the smart host. Also, add a badhost channel (using the Settings->Bad Host Forwarding/Delay option) that also points to the smart host.
This will cause all known (via the SMTP channel) and unknown (via the badhost channel) hosts to be resolved to the smart host.
OpenServer Release 5.0.4 sendmail supports virtual domains under POP. UnixWare 7 supports virtual domains and adds IMAP support as well.
SCO OpenServer Release 5 used virtual users (fake users known only to the POP server), whereas UnixWare 7 uses real users and exports them via a user map into the virtual domains.
Refer to ``The Virtual Domain User Manager'' in SCOhelp for details of how to set up virtual domains and export users to those domains. The virtual domain POP users' inboxes on SCO OpenServer Release 5 are contained in the directory /usr/internet/ip/ip_addr/sco_mail/spool, where ip_addr is the IP address of a virtual domain. The inboxes are named after the virtual user names.
These mailboxes do not need to be reformatted, but do need to be moved into the standard place for inboxes (by default, /var/mail) on UnixWare 7.
In UnixWare 7, virtual users' password information is contained in /var/internet/ip/ip_addr/passwd. This file is in the old style UNIX /etc/passwd format where the encrypted password is contained in the same file as the user ID information. SCO OpenServer Release 5 normally splits out the encrypted password into /etc/shadow, and places an ``x'' in that field in /etc/passwd.
For additional information on the vacation notification features, see ``The Vacation Notification Manager'' in SCOhelp and the vacation(1) and maildelivery(4) manual pages.
The following SCO OpenServer Release 5 files must be migrated:
OpenServer users who have MMDF as their mail transport agent must make the following change in their ~/.maildelivery file:
* - pipe R rcvtripbecomes
* - pipe R vacation
If users have any of the above files on SCO OpenServer Release 5, they can be loaded directly onto a UnixWare 7 system; their functionality is identical.
OpenServer users who have sendmail as their mail transport agent should convert their ~/.forward and ~/.vacation.msg files as described for migrations from SCO UnixWare Release 2.X.
All alias files in SCO OpenServer Release 5 are specified by the ALIAS keyword and table parameter in /usr/mmdf/mmdftailor. For example, the entry
ALIAS table=aliasesspecifies an alias file named aliases. The directory under which the alias files are located is specified in mmdftailor by the MTBLDIR keyword. For example:
MTBLDIR=/usr/lib/mail/aliasfilesIn this case, the full pathname to the alias file would be /usr/lib/mail/aliasfiles/aliases. By default, if you do not have MTBLDIR defined in the mmdftailor file, the directory is defined to be /usr/mmdf/table.
All alias files may be specified for your sendmail configuration on UnixWare 7 systems by using the Mail Manager. In addition, the files must be converted to sendmail alias file format:
name: addr1, addr2, addr3are used in both formats, and will not need modification.
alias:login/fileFor example, ``foobar:dpk/foobar'' would cause user and group IDs to be set to those of the user dpk, and the text of the message to be appended to the file foobar in the dpk default login directory. Similarly, ``foobar:dpk//tmp/foobar'' would do the same for file /tmp/foobar.
On UnixWare 7, redirection of a message to a file is specified differently. If any addresses to the right of the colon in the alias list begin with a slash (/) character, sendmail interprets the address as the name of a file, and appends the mail message to that file. The filename must be a full pathname, and there is no notion of being able to specify a file relative to a user's default login directory. So, using the previous example, if the home directory of user dpk is known to be /home/dpk, then the alias ``foobar:dpk/foobar'' would be converted as follows:
foobar: /home/dpk/foobarThe user and group ID of the file is specified by other sendmail mail delivery agent options. See ``sendmail operations'' in SCOhelp for more information.
news-inject:news|/usr/lib/news/uurecIn UnixWare 7, sendmail format alias files, a program address may take the following forms:
The prg is the full path of the program to be run. Note that if command-line arguments are needed for the program, they must follow prg, and the entire expression must be quoted (the leading quotation mark may either precede or follow the |).
So, converting the previous example to sendmail alias file format would yield:
news-inject:|/usr/lib/news/uurecAgain, the OpenServer specification of the user ID and group ID by the ``news'' prefix is not allowed for UnixWare 7. sendmail uses other methods for this functionality.
mother: < /etc/mmdf/mother_list@udel-relay.arpa
mother: :include: /etc/mmdf/mother@udel-relay.arpa
In both cases, the @HOST is optional.
On UnixWare 7 systems, sendmail does allow a special notation in the right-hand side of an alias to read its list of recipients from an external file. The format is as follows:
aliasname: :include:/pathThe expression ``:include:'' must appear exactly as shown, but optional white space is allowed between the ``:include:'' and ``/path''. The ``/path'' is the full pathname of a file containing a list of recipients. However, you may not specify an @HOST as is possible for SCO OpenServer Release 5. See ``sendmail operations'' in SCOhelp for more information concerning ``:include:'' lists.
The location of the aliases file is defined by the OA option line in the sendmail configuration file /usr/lib/sendmail.cf. The default location is /usr/lib/mail/aliases. However, you should check the sendmail.cf file. This aliases file is compatible with the UnixWare 7 system without modification, and the name and location may be specified by the Mail Manager. However, you must ensure that aliases which use redirection to files or pipes have corresponding directory paths or programs which exist. The aliases database file(s) should then be created using the newaliases(1M) utility.
User-defined ~/.forward files may be brought forward to UnixWare 7 systems (with the modification discussed in ``Preserving vacation notifications'') to use the vacation notification feature.
On SCO OpenServer Release 5 systems using MMDF as mail transport agent, users' ~/.maildelivery files are compatible with UnixWare 7, and may be transferred with little modification. However, the following programs popular with use in ~/.maildelivery on SCO OpenServer Release 5 are not available in UnixWare 7:
On SCO OpenServer Release 5 systems using sendmail as the mail transport agent, users' ~/.forward files are also compatible with UnixWare 7 and may be transferred with little modification. Users must simply ensure that programs, files, and recipients referenced in their ~/.forward files are accessible. See also ``Preserving vacation notifications''.
The SCO OpenServer Release 5 and UnixWare 7 disk subsystems are dissimilar and use slightly different abstractions. While disk divisions identify SCO OpenServer Release 5 filesystem, swap, dump, and boot areas of the UNIX partition, UnixWare 7 uses the term ``slice''. Unlike SCO OpenServer Release 5 divisions, which are limited to eight per partition, UnixWare 7 has a maxiumum of 184 slices.
Just as SCO OpenServer Release 5 uses the divvy command to create and manage divisions recorded in the divvy table, UnixWare 7 controls slices defined in the Volume Table of Contents, or vtoc, managed with the with the disksetup(1M) command. Further, while the filesystem configuration for SCO OpenServer Release 5 is stored in /etc/filesys, UnixWare 7 stores similar information in /etc/vfstab.
These differences are relatively transparent thanks to the implementation of the SCOAdmin Filesystem Manager on UnixWare 7. SCO OpenServer Release 5 administrators will find the interfaces quite similar. However, there are tasks that require use of command line utilities to manage the vtoc and disk slices.
If you plan to install additional hard disks after you install UnixWare 7, they must be configured using diskadd(1M) to create partitions and slices.
To re-partition an existing hard disk (post-installation), use the fdisk(1M) command to define the partitions, followed by disksetup(1M) to define the slices.
For more information, see:
This topic explains the operational differences between the two platforms and points to details provided elsewhere in this document and the UnixWare 7 online documentation.
Some system administration commands are available in their SCO OpenServer Release 5 versions for backwards compatibility, via the OSRCMDS environment variable. See ``UnixWare 7 and SCO OpenServer Release 5 runtime commands''.
Many SCOadmin managers have been ported directly to UnixWare 7, and others have been modified to provide additional features and improved usability.
The SCOadmin desktop has been eliminated; use the SCOadmin launcher under the tree logo on the CDE desktop. The Panorama desktop is still available, but you must run SCOadmin from an xterm.
The principal administrative difference lies in the UnixWare Device Configuration Utility (DCU), now accessible under SCOadmin. See ``Configuration interfaces'' for more information.
The Account Manager now includes user locale settings and remote host equivalency. It also utilizes and manages the UnixWare 7 tfadmin(1M) security database to implement SCO OpenServer Release 5-style authorizations. See ``Authorizations and system privileges'' for more information.
The Task Scheduler allows the setting of scheduled tasks via a graphical manager as well as cron(1M) authorization via the traditional allow and deny files.
This manager includes remote capabilities for default policy distribution across a specified set of machines on a network.
This manager has been revised extensively. It lists printer models by name instead of requiring the users to know the technical details of their print system.
The System Time Manager provides easy access to the date(1) command, allowing modifications only by authorized users and non-NTP clients.
This manager has an improved user interface to provide clear locale information on the main screen and better usability overall. It also sets up locale information for compatibility with both SCO OpenServer Release 5 and SCO UnixWare 2 applications.
The netconfig tool has been renamed netcfg(1M). It includes new functionality and should be accessed using the SCOadmin interface.
The following SCOadmin managers are not provided:
SCO OpenServer Release 5 storage administrative commands are not supported in UnixWare. This includes commands such as badtrk(ADM) and divvy(ADM). Equivalent functionality is provided by UnixWare 7 commands. See ``The UnixWare 7 disk subsystem''.
Third-party SCO OpenServer Release 5 utilities used to configure, monitor, or otherwise manage storage devices must be ported to UnixWare.
ARCserveIT from Computer Associates is provided as part of the base UnixWare product. The SCO OpenServer Release 5 Backup Manager is no longer available. You can restore a tape backup on UnixWare provided the backup application, the tape media and the tape mode used to create the backup are all compatible with UnixWare.
The SCO OpenServer Release 5 version of cpio(1) is available so that you can restore archives made using the Backup Manager under SCO OpenServer Release 5. You should not use the SCO OpenServer Release 5 command to make backups under UnixWare 7. See ``Restoring SCO OpenServer Release 5 backups''.
The UnixWare 7 kernel differs in these respects:
This means that the system is more responsive to variations in workloads and there is more flexibility in tuning.
memfs is backed by the swap device, with memory usage dynamically adjusted to match demand. By comparison, a RAM disk device cannot utilize swap, nor can it vary its memory usage.
Process management is similar to SCO UnixWare 2 and includes the following:
The following pseudo-drivers are not supported:
Instead of using the pseudo-driver /dev/marry, swap space can be added dynamically via the swap(1M) command.
Some devices that were supported in SCO OpenServer Release 5 may not be supported in UnixWare. These may include low-end non-SCSI devices such as floppy-tape. Support for such devices may be available via third parties, but this is not guaranteed. Devices that conform to SCSI or IDE/Atapi, with the exception of IDE Tape, should work in UnixWare. In addition:
In UnixWare 7, the default configuration of the console gives a similar look and feel to that of SCO OpenServer Release 5 console multiscreens.
When the system enters multiuser mode, seven multiscreen text login prompts and one graphical login prompt are presented. The traditional SCO OpenServer Release 5 screen switch sequences can be used to navigate among the multiscreens, with the following exceptions:
If you prefer to have eleven text login prompts as in SCO OpenServer Release 5, instead of the default seven, you can run the following script to enable the extra login prompts:
for i in 09 10 11 12 do pmadm -a -p contty -s $i -S login -fu -v `ttyadm -V` \ -m "`ttyadm -d /dev/vt$i -l console -s /usr/bin/shserv \ -p \"Login (vt$i): \"`" done
Note there must be no trailing spaces after the backslash (``\'') characters at the ends of the third and fourth lines.
For more information on using multiscreens see ``Running programs simultaneously with multiscreen displays'' in the UnixWare 7 online documentation.
SPX and SPX II connections are supported.
The following MUAs are not available:
The UnixWare print service replaces SCO OpenServer Release 5 printing:
Documentation is shipped as HTML and may be read with any world wide web browser. It is organized as topics, rather than as books.
Manual page sections are identified by traditional UNIX numbers instead of the mnemonic letters used in SCO OpenServer Release 5.
Some equivalents are:
| SCO OpenServer Release 5 | UnixWare 7 |
|---|---|
| C | 1 (Unrestricted commands) |
| NC | 1 (Unrestricted network commands) |
| ADM | 1M (Administrative commands) |
| ADMN | 1Mtcp (Networking administrative commands) |
| F | 4 (System files) |
| M | 5 (Miscellaneous) |
Although the base security features of the two platforms are similar in the treatment of account data, passwords, and file permissions, each uses different mechanisms designed to meet (or exceed) C2 level requirements.
The concept of authorizations (privileges that control access to administrative commands and powers) has been carried over to the UnixWare 7 platform, but the underlying mechanism is quite different:
Under UnixWare 7, login restrictions are based entirely on accounts rather than login terminals. Terminals are never locked because of repeated unsuccessful attempts, but the same protection is implemented in the account login process.
The principal differences are as follows:
SCO OpenServer Release 5 and UnixWare 7 use entirely different (but roughly equal) auditing implementations. Consult the UnixWare 7 online documentation for complete information.
The security profiles available under UnixWare 7 replicate SCO OpenServer Release 5 as closely as possible. The ``Security profiles'' table appears in both documentation sets for comparison.
Locale configuration is forced during UnixWare 7 installation -- you must set the locale as you install. More choices have been added to both locale and keyboard definitions in UnixWare 7, which is also backwards-compatible with SCO OpenServer Release 5
You can also set the locale after installation on a system-wide basis using the SCOadmin International Settings Manager or on a per-user basis using the SCOAdmin Account Manager.
On your SCO OpenServer Release 5 system, start the SCOadmin International Settings Manager to view the current locale. The locale is highlighted when you enter the manager; it is listed in the ``Language'' selection box. For example, your locale might be ``en_US''. Record this locale so you have access to it during UnixWare 7 installation.
When you install UnixWare 7 and are prompted for the locale, you will select a locale that appears in spelled-out form; for example, the locale ``en_US'' corresponds to ``English for United States''. You can also select a keyboard that maps to that particular locale.
This appendix describes key command equivalences and differences between UnixWare 7 and SCO OpenServer Release 5, including:
See the manual reference pages for full details of all UnixWare 7 commands.
The options for many commands are different. See the manual pages for information.
The following table shows UnixWare 7 equivalents for SCO OpenServer Release 5 commands that are no longer available.
| SCO OpenServer Release 5 | UnixWare 7 equivalent |
|---|---|
| doscmd(C) | dos(1). These dos utilities are no longer available in UnixWare 7. Similar functionality is available in the mtools package provided in the Skunkware archives. See dos(1) for details. |
| bootos(HW) |
boot(1M)
Use the KERNEL argument to specify the kernel to boot. |
| mkdev(ADM) | The main functionality is in dcu(1M) and resmgr(1M). |
| mkdev hd | diskadd(1M) |
| divvy(ADM) |
disksetup(1M)
Use prtvtoc(1M) and edvtoc(1M) to edit the disk's VTOC. |
| badtrk(ADM) | disksetup(1M) |
| custom(ADM) | pkgadd(1M) (for SCO UnixWare 2.0 and UnixWare 7 packages) |
| enable(ADM) and disable(ADM) |
pmadm(1M)
and
sacadm(1M).
|
| coltbl(ADM) | colltbl(1M) |
| configure(ADM) | The idtools commands. See idconfupdate(1M), CM idinstall 1M , idmkinit(1M) and idtune(1M). |
| cpuonoff(ADM) | psradm(1M) (to activate and deactivate processors) and psrinfo(1M) (to show the current state of processors). |
| cpusar(ADM) | sar(1M) (base command) |
| haltsys(ADM) | halt(1Mbsd) |
| integrity(ADM) | pkgchk(1M) |
| link_unix(ADM) | idbuild(1M) |
| multiscreen(M) | Configure using vtlmgr(1). |
| nwpasswd(NWG) | Use NetWare UNIX Client (NUC) to change passwords. |
| p_fsck (in fsck(ADM)) | CM fsck 1M (-P option) |
| link_unix(ADM) | idbuild(1M) |
|
rc2(ADM):
I01MOUNTSYS P00ANNOUNCE P75cron P70uucp |
rc2(1M):
S01MOUNTSYS K00ANNOUNCE S75cron S70uucp |
| reboot(ADM) | halt(1Mbsd) |
| rlogind(ADMN) | in.rlogind (see rlogind(1Mtcp)) |
| routed(ADMN) | in.routed (see routed(1Mtcp)) |
| rusersd(NADM) | rpc.rusersd (see rusersd(1Mtcp)) |
| rwalld(NADM) | rpc.rwalld (see rwalld(1Mtcp)) |
| rwhod(NADM) | rpc.rwhod (see rwhod(1Mtcp) |
|---|---|
| slist(NWG) | CM nlist 1nuc |
| telnetd(ADMN) | in.telnetd (see telnetd(1Mtcp)) |
| tftpd(ADMN) | in.tftpd (see tftpd(1Mtcp)) |
| timed(ADMN) | in.timed (see timed(1Mtcp)) |
| ulist(NWG) | Use NetWare UNIX Client (NUC) utilities to view all the users on a NetWare server. |
| uuclean(ADM) | uucleanup(1Mbnu) |
| rwalld(NADM) | in.rwalld (see rwalld(1Mtcp)) |
| xntpd(NADM) | in.xntpd (see rwalld(1Mtcp)) |
The following table shows UnixWare 7 equivalents for SCO OpenServer Release 5 system files.
| SCO OpenServer Release 5 file | UnixWare 7 equivalent |
|---|---|
| filesys(F) | /etc/vfstab |
The following commands have the same name but substantially different functionality in SCO OpenServer Release 5 and UnixWare 7. See the manual pages for details of the UnixWare 7 commands.
Commands that differ only in the options available are not listed here.
| SCO OpenServer Release 5 | UnixWare 7 functionality |
|---|---|
| ct(HW) | ct(1bnu) |
| crash(ADM) | crash(1M) (functionality is substantially different) |
|
| |
| boot(HW) (boot program) | boot(1M) (boot program) |
| debug(HW) (boot debugger) | No equivalent. |
| dbx(CP) (command-line oriented user-level program debugger) | debug(1); also see ``A guide to debug for dbx users'' in the UnixWare online documentation. If started in a graphical environment, debug will launch its graphical interface rather than the command-line interface; this can be overridden using debug -ic to start the debugger. |
| dbxtra(CP) dbXtra(CP) (graphical front-ends for dbx) | debug(1); if started in a graphical environment, debug will launch its graphical interface rather than the command-line interface. |
| rc0(ADM), rc2(ADM) | rc0(1M), rc1(1M), rc2(1M), rc3(1M) (See manual pages for details.) |
| rsh(C) | rsh(1tcp) (remote shell) |
| /etc/TZ | /etc/TZ (time zone directory) |
The following SCO OpenServer Release 5 commands are available on UnixWare 7 for backward compatibility purposes. The SCO OpenServer Release 5 commands are located in the /OpenServer/bin directory on UnixWare 7.
To enable use of these OpenServer commands, set the OSRCMDS variable (OSRCMDS=on ; export OSRCMDS) to run applications that use the SCO OpenServer Release 5 versions of these commands.
The following SCO OpenServer Release 5 commands are not available. See ``Equivalent commands and processes'' for equivalents when the same functionality is available via other commands or processes.
You should not have to do anything special to get an existing SCO OpenServer Release 5 application to run on UnixWare 7. The application compatibility features delivered with UnixWare 7 are described in ``Application compatibility''
Source code changes are necessary for many applications originally compiled for use on SCO OpenServer Release 5, so that the source code can be recompiled with the UnixWare and OpenServer Development Kit. See ``Source code compatibility''.
The following list is a brief summary of the known compatibility exceptions for SCO OpenServer Release 5 application binaries and source code in UnixWare 7:
Applications that attempt to access SCO OpenServer Release 5 system data files directly or indirectly may experience problem if these files also exist in UnixWare 7 with a different format (for example, utmp).
Compatibility for SCO OpenServer Release 5 applications on UnixWare 7 is provided by the UnixWare 7 kernel, and the runtime libraries, command executables, and system files provided in standard system directories or in the /OpenServer directories.
Compatibility features for SCO OpenServer Release 5 applications include the following:
Application (or binary) compatibility is designed to be automatic. The UnixWare 7 kernel recognizes SCO OpenServer Release 5 applications installed with custom(1M) (as well as pkgadd(1M) installed packages) and can detect applications compiled for use on SCO OpenServer Release 5. As such, you should use the same instructions that were provided with your SCO OpenServer Release 5 application to install and run your application on UnixWare 7.
Some applications may experience minor problems, due to implementation differences on the two systems. If your SCO OpenServer Release 5 application does not install or run correctly on UnixWare 7, try one or more of the steps listed below.
OSRCMDS=onbefore installing or running the application. Setting the OSRCMDS environment variable in the current process environment causes the shell to invoke the SCO OpenServer Release 5-specific version of some commands that are found in /OpenServer/bin.
in the current process execution environment before installing or running the application. This will force the system to use SCO OpenServer Release 5 versions of some commands and utilities.
The following is a list of general compatibility exceptions:
For shell scripts and commands, see ``UnixWare 7 and SCO OpenServer Release 5 runtime commands'' for lists of the SCO OpenServer Release 5 commands provided with UnixWare 7, and command equivalents that are not provided with UnixWare 7.
For binaries, differences in interfaces that could not be taken care of either in the kernel, native libraries, or ported /OpenServer libraries are listed in the compatibility tables for the appropriate library or system call. See ``Base kernel compatibility'' and ``API compatibility'' in the UnixWare 7 online documentation for details.
The UnixWare and OpenServer Development Kit can be installed on SCO OpenServer Release 5.0.4, and UnixWare 7. It can be used to compile source code that meets the UnixWare 7 APIs.
Source compatibility in the context of UnixWare 7 and SCO OpenServer Release 5 means how much effort it takes to change existing SCO OpenServer Release 5 source code to use the UnixWare 7 APIs and compile with the UnixWare and OpenServer Development Kit.
The resulting executables can be installed and run successfully on UnixWare 7, SCO OpenServer Release 5.0.0, SCO OpenServer Release 5.0.2, SCO OpenServer Release 5.0.4, SCO OpenServer Release 5.0.5, if they do not use any interfaces indicated by a No or -- entry in the compatibility tables for UDK compatibility, or otherwise called out as being specific to either SCO OpenServer Release 5 or UnixWare 7. The Binary Compatibility Module (BCM) for SCO OpenServer Release 5 must also be installed on the target system to run UDK binaries.
An example of an interface that cannot be used in an application intended for SCO OpenServer Release 5 is the libsocket endtosent routine, which is supported only on SCO OpenServer Release 5.
See ``Base kernel compatibility'' and ``API compatibility'' in the UnixWare 7 online documentation for the kernel and API compatibility tables.
© 1999 The Santa Cruz Operation, Inc. All rights reserved.