|
|
This document is provided both on the installation CDs and in the online documentation set; some of the links in this document do not work when this document is viewed from the CD. To see the online doc, which is installed by default, point any browser at http://localhost:8458. This document is available under New Features and Notes.
| Processor |
|
Minimum:
1 Intel Pentium or later microprocessor or 100%
compatible (e.g., AMD Athlon and Duron processors),
Recommended: A 100MHz processor is recommended for minimum performance. Faster processors (available beyond 2GHz) will improve system performance and responsiveness. If Merge (from the Optional Services CD) is installed, a 200MHz or faster CPU is recommended. Maximum: no known maximum |
| Memory |
|
Minimum:
32 MB or more of RAM.
Recommended: 128MB for optimal CDE, Optional Services, and Java performance. Performance is further enhanced as more RAM is added. Maximum: Up to 16GB RAM for General Purpose Memory and up to 64GB as Dedicated Memory (limited for use as either SHM or DSHM) |
| Disk Space |
|
Minimum:
At least 1GB.
Recommended: At least 2.8GB for the Installation and Updates CDs (CD #1 and #2) with LKP selected. To install all runtime CD packages, at least 4.6GB of disk space, as follows:
|
| Host Bus Adapters |
|
Minimum:
1
Recommended: Depends on system's disk configuration. Maximum: 32 HBAs default, up to 1024 HBAs if the driver supports it. |
| Network Cards |
|
Minimum:
0 if no networking, 1 if networking
Recommended: 1 Maximum: No system limit; depends on the number of cards supported by the driver. |
To begin a fresh install using a bootable CD-ROM: insert CD #1 into the bootable CD-ROM drive and power up (or reboot) the system.
To begin a fresh install on a non-bootable CD-ROM: you first need to create installation diskettes. See the instructions found under /info/images on CD #1. Insert Installation Diskette #1 into the primary floppy drive and power up (or reboot) the system.
To begin an upgrade install from Release 7.1.1 or 8.0.0 only: insert CD #2 into the primary CD-ROM drive and enter the following commands as root:
pkgadd -d cdrom1 uli scoadmin upgrade wizard
Follow the prompts to install the desired packages. Once the Upgrade Wizard is finished, reboot the system:
cd / shutdown -y -i6 -g0
You may now upgrade other software, such as LKP (see below) and Skunkware, that is not automatically updated by the upgrade process.
Disconnect USB Hard Drives Before Installation: If a USB hard drive is attached to the system as a secondary drive, installation to the primary SCSI/IDE hard drive may fail. As a precaution, we recommend disconnecting USB hard drives before installing UnixWare 7.
Installation Fails on HP Systems with Dual IDE Ports: Installation on a Hewlett-Packard system with dual IDE ports on the motherboard (such as a Viking 2 system) fails with messages like the following:
UX: idmkunix: ERROR: Conflicting use of interrupt vector: already used... UX: idmkunix: ERROR: Interrupt vector conflict between devices 'ide' and... UX: idmkunix: ERROR: Errors encountered. Configuration terminated
The problem is that the installation is attempting to configure the second IDE port and is detecting an IRQ conflict. This will happen regardless of whether any devices are connected to the second port. The workaround is to disable the second IDE port either in the system BIOS before beginning installation, or in the Device Configuration Utility (DCU) as the installation begins.
Install Fails on non-conforming DMA IDE Drives: If you attempt to install the system using a non-conforming ATAPI IDE drive, the drive may not work as expected in DMA mode. This may cause the installation to fail at the point where you choose the CD-ROM installation method, and the install program attempts to access the CD-ROM drive. If this occurs, disable ATAPI DMA when the system logo is displayed during the installation, as shown in the section Disabling DMA for IDE Devices. After installation, you can selectively disable DMA for such devices on subsequent reboots.
Larger Default vxfs Block and Log Sizes: To enhance filesystem performance, the default vxfs filesystem block size has been increased from 1024 to 2048 bytes, and the default log size has increased from 1024 to 16384 Kbytes. These values can be changed during installation by using the F6 (Advanced options) key within the Filesystems and Raw Disk Slices screen.
osmp (Multiprocessing Drivers) package now part of base OS:
In order to ensure that the most current Multiprocessing (MP) drivers are installed in the running
system, drivers formerly in the osmp package are now installed with the base
package.
The osmp package remains on CD #1, and must be installed in order to
configure osmp.
To change the configuration of osmp after installation, re-add the package as in this example:
pkgadd -d cdrom1 osmp.
kdb (Kernel Debugger) now part of base OS:
In order to ensure that the most current version of the kernel debugger (kdb) and its drivers
are installed in the running system, the kdb command and associated files have been moved
to the base package.
The kdb package remains on CD #1, and must be installed in order to configure kdb.
To change the configuration of kdb after installation, re-add the package as in this example:
pkgadd -d cdrom1 kdb.
Domain Names with Numeric Characters Permitted During Installation: Previous releases did not allow the installer to specify a domain name starting with a digit, although this could be changed to a domain name starting with a digit after the system was installed and rebooted. The installation behavior violated RFC1123. This has been fixed in Release 7.1.3, so that you can also specify a domain name starting with a numeric character at installation time.
Upgrade: Screen Goes Blank for a Moment: When using the scoadmin upgrade command, after entering the upgrade license, the screen may blank for about 30 seconds before the installation of the UpdateSet from CD #2. This is normal and not an indication of any problem. The screen may also blank (or change color) during the installation of additional packages from CD #2. This is not an indication of a problem; please wait for the upgrade screen to reappear.
LKP on a Filesystem Other Than root: By default, /linux (where the OpenLinux Server CD RPMs are installed) is created as a directory in the root filesystem. If you instead want to install the OpenLinux RPMs in a separate /linux filesystem:
# mv /home2 /linux # cd /etc # cp vfstab vfstab.orig # sed -e "s/home2/linux/g" < vfstab > vfstab.new # mv vfstab.new vfstab
# lkpinstall -r
LKP Installation and Upgrade Uses OpenLinux 3.1.1 CDs: Release 7.1.3 is designed to use a modified version of the OpenLinux 3.1.1 Server Installation CD, which is distributed as with UnixWare 7 as the Linux RPM CD (CD #4). This modified CD contains the RPMs from the OpenLinux 3.1.1 Server CD, and is the only OpenLinux distribution recommended for installation with UnixWare 7 LKP.
The file /etc/default/lkpinstall is checked during a fresh installation (and during an upgrade using the scoadmin upgrade wizard) to decide whether the CD-ROM in the drive is usable for installations. The file contains at most two lines, as in the following example:
COL_UNSUPPORTED='2.3 2.4 3.0 3.1' COL_SUPPORTED='3.1.1'
The installation or upgrade will fail if the version of the OpenLinux RPM found on the CD in the drive does not match a version found in COL_SUPPORTED.
When running the lkpinstall command from the comand line, the version of the "OpenLinux" RPM found on the CD is checked against the above lists in a less restrictive manner. If it's found in COL_SUPPORTED, installation proceeds. If it's found in COL_UNSUPPORTED, the CD is rejected. If it's in neither list, the user is prompted to confirm that they really want to install RPMs from the current CD before proceeding.
If it's ever necessary to work around this check, either edit or remove the file /etc/default/lkpinstall before starting; during a fresh install, defer installing LKP, edit or remove the file, and then install using lkpinstall.
During a fresh install of UnixWare 7, insert the modified OpenLinux 3.1.1 Server CD when prompted for CD #4. Similarly, if you use the lkpinstall command, insert the modified 3.1.1 Server CD when prompted to insert the OpenLinux CD.
An unmodified OpenLinux 3.1.1 Server CD can also be used during installation since it contains the identical RPM set as CD #4, but this will cause the RPM names to appear in German regardless of the language setting (a problem fixed on the modified distribution provided with UnixWare 7).
Neither the OpenLinux 3.1.1 Workstation CD nor any CDs based on OpenLinux 3.1.0 (including the OpenLinux 3.1.0 CD distributed with UnixWare 7 Release 8.0.0) should be used during installation of Release 7.1.3. Similarly, the MSLA (Modify System for Linux Applications) script from the Release 8.0.0 Skunkware distribution should not be run on Release 7.1.3; the functions performed by this script have been incorporated into the base system, and running it on Release 7.1.3 may produce undesirable results.
The OpenLinux 3.1.1 Localized Documentation and Software CD - a.k.a. the Internationalization or I18N CD - should not be installed under LKP.
Please also note the usage limitations under LKP: Using OpenLinux 3.1.1 with LKP.
Upgrading LKP: Selecting a Profile During an upgrade using the Upgrade Wizard (the uli package on CD #2), or using the lkpinstall command from the command line, the OpenLinux 3.1 RPM set on your system is updated with the OpenLinux 3.1.1 RPM set contained on CD #4. Note that it is important to select the same installation profile for the upgrade that you used when you installed LKP originally.
The installation program will examine the system and indicate the profile (All Packages, Web Server, File Print Server, Network Server, Minimum Server) that most closely matches the installed system with a > (left angle bracket character) to the left of the RPM profile.
If you are in doubt, choose All Packages. Picking a profile with only a subset of your installed RPMs may mean that some RPMs do not get updated with the most current version.
Please observe the following notes:
Autodetection of PCI IDE Drives Turned Off During Upgrade: In order to avoid performance problems during an Upgrade from Release 8.0.0 to the Release 7.1.3 Beta, autodetection of PCI IDE drives is disabled during the upgrade. If you experience slow system response time during IDE disk operations, you can download an updated IDE driver and installation instructions from ftp://ftp.sco.com/pub/openunix8/drivers/storage/.
No DHCP During Installation: Note that network setup during installation does not offer the option of using DHCP (Dynamic Host Configuration Protocol) to configure the network. To use DHCP you must defer network setup until after installation is complete. Once the system is running, you must:
Perform the last two steps using the Network Configuration Manager, by logging in as root and entering scoadmin network (or, by launching SCOadmin from the desktop).
CD-ROM Installation Order: During a fresh installation, the UnixWare 7 CD-ROMs are installed in the following order:
This is a slight change to the previous release, where if you selected the Linux Kernel Personality (LKP) for installation you would be prompted for CD #4 before CD #3.
Upgrading to ReliantHA 1.1.3: ReliantHA 1.1.3 will not automatically upgrade previous versions of ReliantHA, because there is no opportunity to check or hand modify any of the Reliant configurable files prior to a reboot after the installation of CD#3. The upgrade to ReliantHA 1.1.3 must be performed manually. To do this:
Upgrade the operating system to Release 7.1.3.
After the machine is rebooted, insert CD #3 into the primary CD-ROM drive and enter, as root:
pkgadd -d cdrom1 ReliantHA
This will update the version of Reliant currently installed on the system (1.1.0, 1.1.1, or 1.1.2) to 1.1.3.
Check all ReliantHA configuration files to insure they are correct before rebooting.
Reboot the system:
shutdown -i6 -g0 -y
3Com 3c556B Laptop NIC Not Supported -- Autodetection Incorrect: This release does not include a driver for the 3Com Corperation 3c556B Laptop Hurricane (rev32) NIC adapter. However, if you install on a laptop that has a 3c556B, the system will incorrectly autodetect the NIC as a Gigabit adapter (bcme driver). This is because of confusion between the vendor and device ID numbers for the two boards. Since the 3c556B is not supported, and the bcme driver is not the correct driver, do not select this driver. You must install a supported NIC for this laptop. See the Compatible Hardware Web Page at http://www.sco.com/chwp for NICs supported by Release 7.1.3, as well as the new drivers listed in the section Network Interface Cards (NICs) in this document.
Upgrade: Removal of BASEdoc May Fail: During an upgrade, the basedoc package attempts to remove the previous release's BASEdoc package. This attempt will fail if any package installed on the system has a dependency on BASEdoc (only one package, RelHAdoc, is known to have this dependency). The basedoc package is still installed, but BASEdoc is not removed. This leaves two sets of system documentation (one in SCOhelp and one in DocView), on the system. To work around this problem and remove BASEdoc, record the name of the package or packages that depend on BASEdoc when the error message appears during installation, or execute this command:
grep BASEdoc /var/sadm/pkg/*/install/depend
The above command returns all the depend files in all the packges that have an entry for BASEdoc. Rename each depend file that you find depend.bak, and then reinstall basedoc from CD #2 (pkgadd -d cdrom1 basedoc). Then, after basedoc is installed, move all the depend.bak files to their original name (depend).
ENABLE_4GB_MEM on Systems with <4GB Memory:
Some systems with less than 4GB of memory have been observed to continuosly recycle when rebooted
if the file /stand/boot contains the line ENABLE_4GB_MEM=Y (or if this directive
is specified to the boot loader).
We recommend that this boot directive either not be used on systems with less than 4GB of memory,
or that it be set to ENABLE_4GB_MEM=N on such systems.
Upgrade: Use the Upgrade Wizard: Upgrades of earlier releases to Release 7.1.3 should be performed with the Upgrade Wizard (see Installation). Do not use the pkgadd command to manually install the UpdateSet from CD #2 for the first time. Doing so will lead to dependency problems, and some packages will fail to install. To recover from this failure, install and run the Upgrade Wizard by placing CD #2 in the CD drive and entering the following commands (as root):
# pkgadd -d cdrom1 uli # scoadmin uli
Upgrade: LKP Space May Be Miscalculated: If you are upgrading Release 8.0.0/LKP to Release 7.1.3/LKP, the Upgrade Wizard (scoadmin upgrade) may not properly calculate the space needed for the upgrade, and may tell you there is not enough space to install LKP. If this occurs, press F10 and then F8 to abort the installation. Then execute these commands:
chsysinfo ou8 scoadmin upgrade chsysinfo default
When using the Upgrade Wizard, be sure to select all the packages you currently have on your system, so that they are all upgraded to the current release. If you miss any, you can manually install them later from the CDs using pkgadd.
In general, note that LKP is intended for running applications, not administering your system. Most system administration tasks must be performed from the UnixWare side of the system, using a UNIX shell, commands, and graphical administration tools.
If you want OpenSSH running on your UnixWare 7 LKP system, it should be installed, configured, and run on the Unix side (from CD #1 or CD #2), and not run on the LKP side (although CD #4 contains copies of the Linux version of this package, it is not running by default). See the New Features section for descriptions of the UnixWare 7 openssh package. Although you can run the sshd daemon on either side, running it on the Unix side is recommended, since this provides login directly to a Unix shell (which is probably what is expected on an UnixWare 7 system). If sshd is running on the LKP side, login will take you directly to a Linux shell. Regardless of whether you run sshd on the Unix or Linux side, you must ensure that it is running on only one side, or resource conflicts and unexpected behavior will result.
The NIS-SERVER-2.0-22 and NIS-CLIENT-2.0-22 RPMs from the OpenLinux 3.1.1 CD #4 will install under LKP, and may run, but do not work. NIS (Network Information Service) software must be run and administered on the Unix side of the system. See Administering NIS.
Netscape may hang when processing java scripts. All Netscape users under LKP should:
On fast machines (such as a Pentium 4 over 1GHz), The KDE PS/PDF Viewer may not work correctly due to synchronization problems between the KDE wrapper and the underline application (Ghostscript). The workaround is to use Ghostscript (or another PS/PDF viewer) directly without going through the desktop. This is a problem on native OpenLinux 3.1.1 as well.
Using ps with the f (forest) option and a process set
that includes process 0 (e.g., ps axf, ps -A f, etc.)
will produce no output.
Instead, use
ps f --deselect --pid 0, which has the same effect as ps -A f.
The kdesktop process running under kdeinit is known to dump core when exiting KDE. To fix, re-start KDE.
When used without the -c option, fuser does not report all file usage on LKP file systems. To see what processes are using a file, enter the fuser command with all the possible mount points that could be used to get to that file. For example, to find out all processes from either the LKP or the UNIX side using files under /mnt:
fuser -c /mnt fuser -c /linux/unixware/mnt
The Linux dosemu DOS emulator application does not run under LKP.
The Linux netstat, route, and traceroute commands do not run under LKP. Use the netstat(1Mtcp) route(1Mtcp) and traceroute(1Mtcp) commands from an UNIX shell instead, or use the full path from a Linux shell (as in /unixware/usr/sbin/traceroute).
The Linux at command does not work under LKP; at jobs do not run. To work around this problem, use the Linux crontab command or use at from an UNIX shell.
The output of tty(1) and ttyname(3C) is incorrect when stdin of the current process is not the same as the original login shell. This can happen when executing a Linux command from a Unix shell, or when you open a Unix shell from a window in KDE. For example; log in to the Unix side of a Release 7.1.3 system running LKP and do the following:
$ tty /dev/pty001 $ /linux/bin/cat anyfile ... $ tty /dev/_tcp/1
Once the Linux command is executed, the output of tty upon return is no longer correct.
Once any Linux process has been executed, /linux/dev cannot be unmounted until the invoking login session ends.
The bash RPM attempts to provide appropriate links for login shells listed in /etc/passwd that do not reside under /linux. It detects if a Linux ksh binary (as provided by the pdksh RPM) is installed. If one is present, then it will link all the ksh variants (/linux/u95/bin/ksh, /linux/OpenServer/bin/ksh, and so on) to the Linux ksh. If it is not present, then the script will create Linux side links to bash as the closest match available.
If you are printing to a parallel port from LKP, your print jobs may never appear on the printer; yet, no error messages are displayed. This is due to parallel port device nodes for LKP being defined with the same major device number as /dev/null; the print jobs are effectively being sent to /dev/null. If your system is affected by this issue, then the following ls command will display output as shown:
$ ls -l /linux/lxinst/dev/lp* crw-r--r-- 1 root sys 39, 0 Aug 1 09:55 /linux/lxinst/dev/lp crw-r--r-- 1 root sys 39, 0 Aug 1 10:28 /linux/lxinst/dev/lp0 crw-r--r-- 1 root sys 39, 1 Aug 1 09:56 /linux/lxinst/dev/lp1 crw-r--r-- 1 root sys 39, 2 Aug 1 09:56 /linux/lxinst/dev/lp2
The solution for this problem is documented in the Support Knowledge Base on the Web. Go to the Support Knowledge Base and click on Advanced Search. In the next screen, click on the Search by Incident # button and enter the following keywords into the text box: 115222. Click on Search, and the article will be displayed. Follow the instructions provided in the article to enable printing to parallel ports from LKP.
If you print from OpenLinux 3.1.1 using CUPS 1.1.10 or higher to Release 7.1.3, you may receive the following error message (in an e-mail):
Subject: printer job
Your printer job (KDE Print Test)
could not be printed.
Reason for failure:
UX:lpd: ERROR: The following options can't be handled:
-h (or -o nobanner)
UX:lpd: TO FIX: The printer(s) that otherwise qualify
for printing your request can't handle
one or more of these options. Try
another printer, or change the options.
This message means that the remote UnixWare lpd daemon is not permitting use of
the -o nobanner option, which is the UnixWare lpd equivalent of the Linux
-h option.
To permit use of -h from CUPS on OpenLinux, enter the following command as root in an
UNIX shell:
lpadmin -p printername -o nobanner
where printername is the name of the printer as defined under UnixWare.
If you switch to a Linux shell while in the CDE dtterm X terminal emulator, you may get the following error when launching an X application from the Linux shell:
Xlib: connection to "unix:0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: unix:0.0
To fix this problem, set the DISPLAY variable as shown:
DISPLAY=nodename:0
Where nodename is the value returned by the uname -n command. An alternative solution is to execute xhost + in the Linux shell, but this is less secure than setting DISPLAY because it allows any process to write to the terminal.
The implementation of the Linux /proc/devices file under LKP (/linux/proc/devices) is limited and does not provide all the functionality provided on a Linux system. In particular, block devices are not mapped in the file. Applications that depend on this file may not run correctly.
All graphical interfaces running under LKP (including KDE2) use the Unix X server by default. Although XFree86 is also provided on the OpenLinux 3.1.1 CD #4, it is not configured by default after installation. Instructions for configuring the system to use the XFree86 server instead of the Unix X server can be found in the LKP documentation in the section Configuring an X server.
During installation of StarOffice, you may see the following message:
No resource: Error message not available
Such messages can be safely ignored.
The HanCommWord5 application (Korean word processor), does not work under LKP.
The Oracle Performance Manager application (for use with Oracle databases), does not work under LKP.
See also the new lxcore utility.
Release 7.1.3 is shipped with the OpenLinux Release 3.1.1 Server CD-ROM (as CD #4). The RPMs contained on this CD are loaded under LKP, and can be updated as new versions are released on the SCO FTP Site. To install updates, you can use either of two methods:
Download the updated RPM images and use the rpm command under LKP to install them. See the README files on the SCO FTP site that accompany updated RPMs for the command line you should use to install them.
Use the System Updater from KDE (or kcupdate from the command line). To enable the System Updater, you must first:
OpenLinux-MR311-server-20011213-1800
After creating the above file, you can start the System Updater from LKP, either through the KDE desktop (click on the System Updater icon) or an LKP shell (enter kcupdate). The System Updater will lead you through the process of applying available updates.
Linux Shell Users Cannot Log Into or Run CDE: Logins that have a Linux-side shell (any shell under /linux) cannot run the Common Desktop Environment (CDE) on the Unix side, and cannot log in to a CDE Desktop. To work around these problems, you must either change the login's shell in /etc/passwd to one located on the Unix side (/bin/ksh, /bin/sh, etc.), or run another desktop. If you log in through the dtlogin screen, choose the Panorama or Failsafe Desktop sessions from the pull-down menus at the bottom of the screen.
Installing and Running Applications from Prior Releases: Most Release 8.0.0 and Release 7.1.1 applications will continue to install and run properly on Release 7.1.3. Some legacy applications, such as VisionFS, will not install or run correctly because the application was written to expect Release 7.1.1 return values from the uname(1) command.
If you are upgrading, or if you want to run an application written for a prior release on Release 7.1.3, and the application you want to use either will not install or will not run, try executing the following shell commands before installing or running the application:
SCOMPAT=5:7.1.1:UnixWare export SCOMPAT
These commands change the values returned by uname to match those returned by UnixWare 7 Release 7.1.1, in the environment of the current process. To install and run a prior release's application successfully on Release 7.1.3 (e.g., App711, started with StartApp711), you might need to execute the following sequence of commands:
SCOMPAT=5:7.1.1:UnixWare export SCOMPAT pkgadd -d cdrom1 App711 StartApp711
You may also want to add these commands to the top of the application's startup scripts so that the application will startup without having to specify SCOMPAT on the command line each time you start the application. The chsysinfo(1M) command can also be used to change the kernel values for system name and version, but these changes are system-wide; use chsysinfo only if you want the entire system to return system name and version values different from the default values.
Emergency Recovery Does Not Work with the udi_dpt Driver and Tape Drives: The udi_dpt Host Bus Adapter (HBA) driver cannot store data to tape drives or restore data from tape drives. The workaround is to choose a non-UDI driver for the tape device using the Device Configuration Utility, dcu(1M).
X Applications Cannot Dynamically Scale Down Some Multibyte-Character Fonts: The UnixWare 7 X server cannot dynamically scale below 16 points any multibyte character set font provided in 16 points or larger. This problem also affects applications run under LKP (the Linux Kernel Personality). To work around the problem, you must use the application's font selection facility to select another multibyte-character set font that is already provided in the required smaller point size. This avoids the need for the X server to dynamically scale the font down to the point size you want. When changing the application's font, also ensure that the application's settings for country, language, and code set are appropriate for your locale.
High Security Profile Prevents non-root DNS Lookups:
If you chose a high security profile during installation, or switched to one using the
relax(1M) command, then the /etc/resolv.conf
file's permission mode is changed to 600, which locks out all users except root
from doing DNS (Domain Name Service) lookups.
Enter the command chmod 644 /etc/resolv.conf as root to enable DNS
lookups for all users.
Slow Printing on Extended Parallel Printing Ports: If your system is equipped with an extended standard parallel port and printing to that port is slow, follow the instructions given below in the section Improved Recognition of Extended Standard Parallel Ports.
NVIDIA and AOPEN Video Driver May Cause Reboot or Hang: There is a known problem with the NVIDIA GeForce2 Ultra adapter and the AOPEN TNT2M64 based PA3000+ agp adapter when using the VESA mode. Due to a suspected problem with the adapter VESA firmware, an attempt to startup the desktop may cause the system to reboot or hang. The workaround is to go to single user mode (shutdown -iS) and run scoadmin video to either configure the IBM VGA driver for low resolution, or use another video card.
USB Keyboards Do Not Work with kdb: USB keyboards do not work with kdb(1M). You must use a serial console or a PS/2 keyboard for kernel debugging.
df Returns Error or Uses Wrong Path if LKP is Installed: If you use a file system mount point as an argument to the df command, on a system with LKP installed, you may get an error or incorrect output. The work around is to specify the device name instead of the mount point.
So, for example, the root file system is by default a vxfs file system; df -os /
should return the number of free extents of each size on the root file system.
Instead, the command fails with the message:
UX:df: WARNING: / mounted as a lxuwfs file system
A related problem is that if you specify / as an argument, df will use /linux/unixware in its output, as in this example:
# df / /linux/unixware (/ ): 10238436 blocks 1365110 files #
To fix these problems, use the full device name in place of the mount point, as in these examples:
# df -os /dev/root
/ (/dev/root ): 10246232 blocks 1366148 files
Free Extents by Size
1: 71 2: 99 4: 72 8: 90
16: 50 32: 30 64: 21 128: 18
256: 8 512: 0 1024: 6 2048: 11
4096: 5 8192: 2 16384: 3 32768: 1
# df /dev/root
/ (/dev/root ): 10238436 blocks 1365110 files
#
Use the df command with no options to get a list of device names and mount points.
Japanese xterm Has Cut and Paste Problems: If you install the jale package (Japanese Language Extensions) from CD #1 or CD #2, xterm is replaced by xterm_ja (a mtulibyte version of xterm). Unfortunately, the paste operation does not work correctly in xterm_ja; garbage is added to text when it is pasted into the terminal window. The workaround is to run the XFree86 X server from LKP instead of the Unix X server. See Configuring an X server in the LKP documentation.
Errors in First Mail to root After Install: After installation, root's mailbox contains mail that instructs the administrator to run the config_search command to generate the SCOhelp documentation search index. This message is incorrect; SCOhelp has been replaced by DocView, and the command to generate the DocView search index is /usr/lib/docview/conf/rundig. Generating the indexes for the first time can consume significant system resources; run this command when the system is not being used heavily.
CD Burning Timeout and Performance Issues: If you have an IDE bus CD-RW drive, and you want to erase CD-RW discs, you must edit the file /etc/conf/pack.d/ide/Space.c and raise the atapi_timeout value to a very high number (e.g. 60000). This will prevent timeout problems on the bus when erasing CDs.
Also on IDE-based systems, it is strongly recommended that you install your CD-RW drive on a different bus than the one on which your root hard disk resides. If you try to blank CD-RW discs on an ATAPI drive that is on the same bus as your root hard disk, your whole system will be unaccessible during the burn (which could take longer than 5 minutes); other system problems can occur as well.
MultiTech Modem Problems After Upgrade: If you are using a MultiTech MultiModem dialer entry in your system modem configuration and are upgrading from a previous release, the Modem Manager will not be able to find the configuration files for your existing modem after you upgrade. Dialers named MultiTech MultiModem have been renamed to MultiTech MultiTech. In an upgrade, the Modem Manager can no longer find the MultiTech MultiModem dialer entries because they are no longer listed in the file /etc/uucp/DBase/MultiTech_Systems. To fix this after the upgrade completes, manully edit the file /etc/uucp/Devices and comment out the old MultiTech MultiModem entry using a '#' character. Then, run scoadmin modem to reconfigure your modem.
Java Errors When Using Netscape 4.6.1: The version of Netscape (4.6.1) delivered on CD #1 and CD #2 for UnixWare may display popup screens when processing web site certificates, and on exit may display these error messages:
==========================================================================
Java reported the following error on startup:
java.lang.SecurityException: system classes were not signed
===========================================================================
===========================================================================
# Error: Issuer certificate is invalid. (-8156)
# jar file: /opt/netscape/java/classes/java40.jar
# path: /opt/netscape/java/classes/java40.jar
===========================================================================
This is due to the versions of certain plug-in modules provided with Netscape 4.6.1. While these windows and errors do not indicate any security concern, you can avoid them by using a more recent web browser, such as the versions of Konqueror or Mozilla that run under the Linux Kernel Personality (LKP).
Viewing Apache Manual Pages:
Apache manual pages are installed with the apache package, but the directory in which they
reside is not added to the default MANPATH environment variable.
As a result, the man command does not display them.
To workaround this, edit the file /etc/default/man, and add :/usr/lib/apache/man to the
MANPATH line in the file; or, specify the directory on the command line,
as in this example:
man -M /usr/lib/apache/man httpd
USB Device Fails To Work on Connect: Some USB devices may fail to enumerate reliably when you connect them. If you connect a USB device and see either of the following the error messages:
Descriptor load failed during enumeration! or Descriptor parse failed during enumeration!
Disconnect and reconnect the device to fix the problem.
PHP 4.2.0 is also available on the Skunkware CD-ROM. To install PHP:
# pkgadd -d cdrom1 php
# /etc/init.d/apache stop
# /etc/init.d/apache start
Buffer overflow attacks have become increasingly common, and represent a major security vulnerability. A buffer overflow occurs when an application uses a fixed-length buffer to hold user input, and does not check that the data read into the buffer does not exceed the size of the allocated buffer. Malicious users can exploit this programming error by overwriting the buffer with data that typically gets executed as a program and grants them a shell on the target system. If the application whose buffer is overwritten in this fashion is a system process running as root, the user can gain unrestricted access to the system. Other possible methods of exploiting buffer overflows also exist. The bock command provides a means of monitoring for such attacks. See the bock(1M) manual page in the online documentation.
Please also see the section CD Burning Timeout and Performance Issues, in this document.
The DocView Documentation Server (docview) is installed by default from CD #1 during a fresh installation and from CD #2 during an upgrade. DocView provides access to all documentation installed on UnixWare 7, through a customized Apache server on port 8458. With it, updated documentation packages are installed that are designed to work in the DocView framework.
To display DocView, simply point any browser at http://localhost:8458. If you get no response, check the status of DocView and start it if necessary, as shown (logged in as root):
# docview status /etc/docview status: httpd (no pid file) not running # docview start /etc/docview start: httpd startedDocView may also not start because the Apache Web Server package was not installed. To check if Apache is installed, enter:
$ pkginfo apache UX:pkginfo: ERROR: information for "apache" was not foundThe above example shows the response given if Apache is not installed. To install Apache, insert the Optional Services CD into the CD-ROM drive, and enter:
$ pkgadd -d cdrom1 apache
DocView uses htdig as its search engine. The search index is not created automatically when you install DocView. To create the search index, run the following command as root:
/usr/lib/docview/conf/rundig
Whenever you add documentation to DocView, run the above command to include the new documentation in the search index.
DocView replaces the SCOHelp documentation server and browser supported on Release 8.0.0 and earlier systems. Upgraded systems will have both SCOhelp (serving port 457) and DocView (serving port 8458) installed; the previous release's BASEman and BASEdoc packages are removed, and a pointer to DocView is added at the top level of SCOhelp. Fresh installations will have DocView only.
The table below shows the base system documentation packages now in DocView format, the CD-ROMs on which they are located, and the name of any set that installs the documentation packages automatically.
| CD-ROMs | Packages | Set |
| CD #1, #2 | docview basedoc baseman | doc |
| CD #2 | lkpdoc | lxcompat |
| OUDK CD | udkdoc | udk |
The remainder of the documentation on CD #2 (such as the openslpd package) and the documentation packages on he Optional Services CD remain in SCOhelp format, and will be installed and displayed under DocView on port 8458. Similarly, legacy SCOHelp-format documentation from prior releases will be viewable under DocView after they are installed, under the same topic name as before. For example, the RelHAdoc package is in SCOhelp format on the Optional Services CD. It is installed under the Filesystems topic in both SCOhelp and DocView.
The scoadmin dns graphical interface can be used to set up basic Domain Name Service (DNS) configuration files and a BIND9 boot file. A new command, h2n(1M), is provided to manage basic and advanced DNS and BIND9 features. See the manual page for details. Note that once you use h2n, you must continue to use it to maintain the configuration files; the scoadmin dns interface cannot process the files generated by h2n.
pkgadd -d cdrom1 rstmp
To disable DMA at boot, interrupt the boot process as it begins by pressing a key when the system logo
is displayed.
Once the [boot] prompt is displayed, enter the following:
ATAPI_DMA_DISABLE=YES
Then, enter boot to continue booting the system.
To disable DMA on every system boot, append ATAPI_DMA_DISABLE=YES to the file
/stand/boot [see boot(4)].
To disable DMA for either a particular model name or a
family of models, use the ide_exceptions[] array in the
/etc/conf/pack.d/ide/space.c file [see the
space.c(4dsp) manual page in the online documentation].
The ide_exceptions[] array contains IDE devices that do not conform to
specification when operating in DMA mode; the driver will disable DMA for any device or
family of devices appearing in this array.
The first argument is the model number and the second is the firmware version.
Model numbers are matched based on the size of the string entered in the array.
This means that the string "ABCD" will match all devices starting with "ABCD".
Use sdiconfig -l to get a list of devices.
Leading spaces in either argument are ignored for matching purposes.
The third and fourth arguments in this array are not currently used, and should be given values as
in the example below:
struct sdi_blist ide_exceptions[] = {
{"HITACHI CDR-8335","0008","", 1}
};
The following Host Bus Adapter (HBA) drivers have been updated as indicated:
| adsl | Corrected various problems that made the system unusable. |
| adst70 | The following problems were corrected:
|
| ciss | Corrected a problem where ciss-based boot controllers were not configured properly during OS installation. This updated driver adds support for the following Compaq HBA model: the Smart Array 5312 64 bit PCI-X Dual Channel Ultra 160. Note that to use 64-bit DMA with this driver, ensure that Smart Array 530x or Smart Array 532 firmware is at firmware level 2.18 or higher; if not data corruption could occur. Smart Array firmware updates can be found on Compaq's Web Site. |
| c8xx | Minor problems with the text displayed on boot were corrected. The fixed block size limit was increased to 128K. |
Note that using Jackson Technology may either increase or decrease system performance depending on the workload applied to the system. By default, Jackson Technology is disabled. To enable it, edit the file /stand/boot and add the following to the file:
ENABLE_JT=Y
You can also enter this string before the OS boots, by pressing the space bar when you see the UnixWare 7 logo during a reboot.
Modifications were made to the MPS (Intel Multi-Processor Spec) PSM (Platform Specific Module) to read the ACPI BIOS tables. The PSM processes the tables as follows:
Use the psrinfo(1M) command to display processor status.
The java2sdk3 package from Release 8.0.0 has been updated and is also on CD2 to allow users to upgrade previous versions of the java2sdk3 package. These packages can be selected during a fresh install or an upgrade from a previous release. They can also be installed manually using pkgadd; the j2sdk131 package depends on the j2jre131 package, which must be installed first. as in this example:
pkgadd -d cdrom1 j2jrel31 j2sdk131
Release notes for the JDK are on the UDK CD under /info/java_dk.
New Script to Auto-start Linux Daemons: There is now a script on the UNIX side in the file /etc/rc2.d/S99linuxrc that starts selected Linux daemons on boot (controlled by /etc/default/linuxrc). See LKP System Management in the online documentation for details,
Default Tunings Modified for Linux Applications: The default UnixWare 7 kernel tunings have been modified for Release 7.1.3 so that it should no longer be required to tune the kernel for many Linux applications (such as StarOffice and Apache) that require increased or specially-tuned kernel resources. For this reason, the MSLA (Modify System for Linux Applications) script that was provided in Release 8.0.0 on the Skunkware CD should not be run on Release 7.1.3, as the tuning performed by that script has been improved and incorporated into the Release 7.1.3 kernel.
/linux/proc merged into /proc: In the previous release, the Linux /proc filesystem was implemented on LKP under /linux/proc, and supported by the lxprocfs kernel module. The lxprocfs functionality has been merged into the procfs module, and the lxprocfs module has been removed. The user-visible functionality of /linux/proc is essentially the same but is provided by procfs mounted with a new mount option (-olinux).
lxcore - transform a Unix core file into a Linux core file: A new utility is provided that transforms a Unix core file into a format that can be understood by the Linux gdb debugging tool running under LKP. The syntax of the new command is:
lxcore unix-core-file linux-core-file
Both file names must be provided. See the lxcore(1M) manual page.
This utility is intended only for core files generated by linux applications or processes that dump core while being run from LKP. In particular, this tool is not intended and cannot be used as a means of debugging core files generated by UnixWare 7 applications using the linux gdb. The linux gdb requires access to the binary file as well as the core file, and does not know how to interpret an UnixWare 7 binary.
Limited support for tape devices added: LKP now supports the Linux tape devices /dev/st0 and /dev/nst0. These are mapped to the standard Unix tape devices /dev/rmt/ctape1 and /dev/rmt/ntape1, respectively. Other tape devices can be added by editing the file /etc/conf/pack.d/lxdevfs/space.c and rebuilding the kernel. Note that the Linux tape devices do not support the complete set of ioctl commands supported on the Unix devices, and in particular only a small set of SCSI passthru commands are available to the Linux devices. For this reason, complex tape management systems should not be expected to work under LKP.
The LS-120 technology standard enables LS-120 floppy drives to store 120 MB of data on a single, 3.5-inch LS-120 diskette; an increase of more than 80 times the current capacity of standard 1.44 MB diskettes. The LS-240 standard doubles that capacity when using LS-240 diskettes; LS-240 drives can also typically read/write LS-120 diskettes, as well as reformat standard 1.44MB-capacity diskettes to hold 32MB of data. Both types of drives can read and write standard 1.44MB capacity diskettes.
If your system is a fresh installation of Release 7.1.3, the Merge documentation is served by DocView on http://localhost:8458 and installed under DOS and Windows. If you upgraded your system to Release 7.1.3, then the Merge documentation is served by both DocView and the previous SCOhelp browser (on port 457) under the same topic. Also see the Merge Release Notes under the /info/merge directory on the CD.
BOARD_IDS parameter in a driver's bcfg(4dsp) file
accepted identifiers in the format 0xSubVendorSubDevice, as in:
BOARD_IDS="0xE110085"
Though never officially supported, this format did work.
With Release 7.1.3, the format above is no longer allowed; BOARD_IDS must be
specified in the format 0xVendorDevice.SubVendorSubdevice, as in:
BOARD_IDS="0x14E41645.0x0E110085"
If both formats are specified, then the driver will work on both Release 7.1.3 and older systems:
BOARD_IDS="0xE110085 0x14E41645.0x0E110085"
The Intel eeE and e1000g drivers are no longer provided or supported. They are replaced by the eeE8 (Intel Pro/100+) and e1008g (Intel Pro/1000) drivers, respectively. On upgrade, the new drivers do not automatically replace the older drivers; the system continues to use the eeE or e1000g drivers if already installed. To use the new driver instead: run netcfg (or scoadmin network), remove the adapter, then add the adapter again, selecting the new driver (both drivers will be listed).
The stbg driver (IBM PCI Ethernet Adapter) has been discontinued; use the pnt driver (AMD PCnet family mdi driver) instead.
The following network interface card (NIC) adapter drivers are new or have been updated for this release:
3Com 3C996/3C1000/3C94X Gigabit Ethernet Broadcom BCM5700 NetXtreme Gigabit Ethernet Broadcom BCM5701 NetXtreme Gigabit Ethernet Broadcom BCM5702 NetXtreme Gigabit Ethernet Broadcom BCM5703 NetXtreme Gigabit Ethernet Compaq NC6770 Gigabit Ethernet Compaq NC7760 Gigabit Ethernet Compaq NC7770 Gigabit Ethernet Compaq NC7771 Gigabit Ethernet Compaq NC7780 Gigabit Ethernet Compaq NC7781 Gigabit Ethernet
Compaq Netelligent 10/100 TX PCI Dual TP (ID CPQAE40) Compaq Netelligent 10BaseT PCI UTP (Board ID CPQAE34)
700262-xxx PRO/1000 Gigabit Server Adapter PWLA8490 717037-xxx PRO/1000 Gigabit Server Adapter PWLA8490 713783-xxx PRO/1000 Gigabit Server Adapter PWLA8490G1 A38888-xxx PRO/1000 F Server Adapter PWLA8490SX 738640-xxx, PRO/1000 F Server Adapter PWLA8490-SX A06512-xxx PRO/1000 Gigabit Adapter PWLA8490SXG1P20 A19845-xxx PRO/1000 T Server Adapter PWLA8490T A33948-xxx PRO/1000 T Server Adapter PWLA8490TG1P20 A51580-014 PRO/1000 XT Server Adapter PWLA8490XT A73668-001 PRO/1000 XT Server Adapter PWLA8490XTL A68178-xxx PRO/1000 XT Lo Profile PCI Server Adapter PWLA8490XTL A50484-xxx PRO/1000 XF Server Adapter PWLA8490XF 739456-xxx IBM Netfinity Gigabit Ethernet SX Adapter 09N3599 721352-xxx IBM Netfinity Gigabit Ethernet SX Adapter 30L7076 A34085-xxx IBM Gigabit Ethernet SX Server Adapter 06P3718 A36407-xxx IBM Gigabit Ethernet Server Adapter 22P4618 A78408-xxx PRO/1000 MT Desktop Adapter PWLA8390MT A81081-xxx PRO/1000 MT Server Adapter PWLA8490MT A65396-xxx PRO/1000 MT Dual Port Server Adapter PWLA8492MT A81983-xxx PRO/1000 MF Server Adapter PWLA8490MF A78709-xxx PRO/1000 MF Dual Port Server Adapter PWLA8492MF
3COM 3C980C EtherLink Server 3COM 3C982-TXM Dual Port Fast EtherLink Server 3COM 3C980C-TXM 10/100 PCI Server Network Interface Card
Intel EtherExpress PRO/100B T4 PILA8475B
The OpenSSH suite includes the ssh program (replacing rlogin and telnet), scp (replacing rcp), and sftp which replaces ftp. Also included is sshd, the server side of the package, and the other basic utilities like ssh-add, ssh-agent, ssh-keygen and sftp-server. OpenSSH supports SSH protocol versions 1.3, 1.5, and 2.0. For more information on the SSH tools, see the documentation on the OpenSSH Web Site http://www.openssh.org/manual.html.
man openssl after installing
the openssld package (on CD #2 only), or go to
http://www.openssl.org.
pkgrm ReliantHA), and then install ReliantHA 1.1.3
from the Optional Services CD.
An upgrade package for releases 1.1.0-1.1.2 will be included in the final product.
If you have already installed the new package over the old, remove the package as shown above and
then reinstall from the CD.
The documentation for this software is installed under Filesystems in the online documentation. The following enhancements are included in version 1.1.3:
Added a configuration utility to simplify the configuration process. The new script is /usr/opt/reliant/bin/rcu. Documentation for it will be available in the final product.
Added a minimal sanity diagnostic tool for ReliantHA configurations. The new script is /usr/opt/reliant/bin/rdu. Documentation for it will be available in the final product.
Added a sample script utility that copies configuration files from one machine to all other nodes in a Reliant cluster. It new script is /usr/opt/reliant/bin/samples/hvcpconf. Documentation for it will be available in the final product.
When serial or other private links fail, a warning is now logged in the switchlog file.
The example line in the hvipalias files has been updated.
The gab driver has been changed to allow the system administrator to run the gabconfig command to make the system panic when a gab_halt occurs, allowing a dump to be taken. The command and its options are:
/sbin/gabconfig -P [0|1]
A '1' enables the panic scenario, and a '0' disables it. It is disabled by default.
Oracle failover scripts capable of handling Oracle9i have been provided as sample scripts in the /usr/opt/reliant/samples directory. They have not yet been fully certified, so use them at your own risk. When certified, they will replace the Oracle scripts with the same names in /usr/opt/reliant, which are currently not Oracle9i-capable.
A bug in the Process_Offline script has been corrected, so that the appropriate script processes get killed, and do not accidentally kill non-ReliantHA processes and shells. It also appropriately kills any children spawned by the ReliantHA process.
The Ip and Mount detector scripts have been improved, and now allow you to set the debug mode for each, as follows:
| Desired Logging Behavior | -d flag in the Ip or Mount entry in /usr/opt/reliant/etc/rkind/names | .Ipdebug_min or .Mtdebug_min file in rkind directory |
|---|---|---|
| log failure messages and state changes only | set | exists |
| log all messages | set | removed |
| log minimum detector messages and don't log bm messages | unset | exists |
| log no messages | unset | removed |
An experimental, improved Nw detector has been added as a sample; it should be used with care on production systems, or it may pose a security risk.
The vulnerability is that rsh is invoked within the binary, and root permission in the .rhosts file on each node must be enabled for the experimental version to work properly. By doing this, you are allowing the root login on the system running the experimental version to log in to any node with root permissions.
To use the experimental Nw:
cp /usr/opt/reliant/bin/samples/Nw /usr/opt/reliant/bin/Nw
On each node, create a /.rhosts file that contains the system name
(uname -s)
The experimental Nw detector, upon detection of a Network failure, will remotely check the ability of other nodes to access the network. If they are unable to access the network either, then the applications will stay on the current node. If the node to which the application is to move is successful in accessing the net, then the switchover will proceed as configured.
When none of the nodes are able to access the public network, execution of hvdisplay will show all applications (as well as the Nw Resource) to be "online". The Nwlog will log messages indicating that the network is inaccessible. The administrator must inspect the log, when the network access is questionable, before executing an hvswitch. To execute hvswitch under this condition will not restore the network and may result in an unecessary switch.
Setting the debug level is the same as for Ip and Mount, except the resource name is Nw and the file is .Nwdebug_min.
The cdrtools application on the Optional Services CD can be used to record CD-R and CD-RW format CDs.
Samba 2.2.4 is included on the Optional Services CD. Samba provides filesharing capabilities using native Microsoft SMB and CIFS protocols for interoperability with Microsoft operating systems. Samba 2.2.4 includes both a Pan-European version as well as a multibyte version suitable for Asian locales. (The important difference between the two versions is the sorting algorithm used for file ordering which determines whether the file sorting is compatible with wide-character or ascii character code environments.)
Samba is configured with the SWAT (Samba Web Administration Tool) utility using a web browser on http://localhost:901. In both versions, localization settings are accessed from the SWAT Home Page by clicking on the Globals tab, and then selecting Advanced View. Set appropriate values for your locale for the client code page, the character encoding system, and the other options (each option has context-sensitive help). Please refer to the man page for smb.conf for futher details. The Samba documentation is installed with the software. To view it:
The SCO Update Service provides a convenient way for you to keep your system current via access to maintenance and security updates, and optionally to early access to new product features which will be included in the next release. When you register your SCO Update Enabling License, obtain a Registration Key, and enter the information into the License Manager, you will then receive updates over the internet (or, optionally, on CD). Please go to http://www.sco.com/products for more information about the SCO Update Service, including SCO Update licensing terms and obtaining a SCO Update license.
SCO Update Service Enabling Licenses are sold either separately or bundled with an Edition License. If bundled with the Edition License, the Enabling License is part of the license information supplied during installation of the system, and will appear in the License Manager after installation. If purchased separately, use the License Manager to enter SCO Update license information.
The SCO Update Service Enabling License must be registered in order to begin receiving product updates via the SCO Update Service.
Registering your system software provides these benefits:
Registering a product is basically a three-part process: first, you use the License Manager to get the information you need to register; second, you visit the Registration Web Site to obtain a Registration Key; then, you use the License Manager again to enter the Registration Key onto your system.
See Using the License Manager for how to use the License Manager and register products.
Any device that conforms to the protocol defined in the USB Specification should work with the UnixWare 7 USB stack. Devices using proprietary protocols will not. If you have, for example, a touch tablet that presents itself as a conforming Human Interface Device, there is an excellent chance that it will work like a mouse even though it has not explicitly been tested. The following hardware has been used with Release 7.1.3:
| Keyboards | Antec Apple Belkin Gateway Imageteam 3800PDF handheld linear Imager Logitech iTouch Microsoft Natural Keyboard Symbol 2014 Barcode reader |
Mice | Acomdata RF wireless/laser pointing presentation mouse Apple Hockey Puck Apple Optical Kensington Mouseworks Logitech Mouseman Wheel Microsoft Intellimouse Microsoft Intellimouse Optical Explorer |
| Hubs | Antec keyboard integrated hub Ariston 4 port Apple keyboard integrated hub Aten 2 port dongle Belkin 7 port Belkin F5U012 docking station (hub only) Gateway keyboard integrated hub Logitech itouch keyboard integrated hub Orange Micro USB 2.0 Xircom 4 port |
HCIs | Numerous motherboard chipsets Dlink D500 UHCI SIIG OHCI Adaptec EHCI Orange Micro EHCI ADS 2-port OHCI |
| CDs | Addonics 1.1 cable Addonics 2.0 cable IBM USB Portable CD-ROM Drive 00N8239 (mechanical media lock) Iomega ZipCD 650 La Cie 8x4x32 Part II Atapi to USB CD-RW enclosure Plextor PlexWriter 24x10x40 CD-RW Drive PX-W2410A1.03 |
Tape Drives | Onstream USB 2.0 Exernal Tape Drive with controller |
| LS120/240 Floppy Drives | Addonics Pocket Superdisk 240 Buslink floppy FDD1 (mechanical media lock) IBM External USB Floppy Disk Drive 05K9282 Imation D353FUE Que Superdisk 240 |
||
For more information on USB, including copies of the USB 2.0 Specification, see the USB Web Site.
cc and CC now permit profiling of threaded programs: The cc and CC compilers now permit profiling of threaded applications. The profiling option -p can now be combined with the -Kthread, -KthreadT, -Kpthread options.
For more information, see the /info directory on the UDK CD; it contains updated release notes for the Java Development Kit, the Open Source Tool Kit, as well as the UnixWare 7 compilers and tools.
See the Guide to Development Kits for a general introduction to developing software on SCO Products. This and other resources are available from the SCO Developer Network Web Page.
The default graphics mode for installation has been increased from 800x600 resolution with 256 colors to 1024x768 resolution with 256 colors.
The following updated drivers are provided in Release 7.1.3:
The mtx driver has been updated to include support for the Matrox G450 Graphics Adapter. The highest resolution supported by the driver is 1600x1200 with 16 million colors, even though the card is capable of supporting higher resolutions. Also note that the DualHead and Dual Display features of this adapter are not supported.
Autodetection support for the ATI RAGE 128 PRO II GL Graphics Adapter has been added to the r128 driver.
pkgadd -d cdrom1 openssl openslp Volution
The Volution Manager Client requires a Volution Manager 1.1 Server running on OpenLinux 3.1.1 or on Release 7.1.3/LKP; in the case of LKP, the server can be installed and run on the same machine as the UnixWare 7 VM Client. Together, they enable you to manage critical services on your UnixWare 7 system from a browser anywhere on your network. Once installed, the Volution Manager Client is started by executing:
/etc/init.d/volutiond start
Note that although a Volution Manager Client is provided for OpenLinux, you should not install and run the Volution manager Client under LKP; only the Unix-side VM Client can manage a Release 7.1.3/LKP system.
All documentation for using Volution Manager 1.1 is installed on the Server system, not on the Client. The Volution Manager Installation Guide and Administration Guide are available on the web at http://www.sco.com/support/docs/volution/. It is recommended that you read Chapter 3 of the Volution Manager Installation Guide, “Installing Volution Manager Clients”, with particular attention to the subsection “Running the Volution Manager Key Tool on UnixWare and UnixWare 7 Clients” before running the VM Client. Also see the product information on the Volution Manager Web Page.
You can manage software on your Release 7.1.3 system with a Volution Manager Server running on the LKP side, and a Volution Manager Client running on the Unix side.
The Volution Manager Server is provided on a separate CD-ROM, and is installed under LKP only. You must choose LKP for installation from CD #2 on fresh install or upgrade (or use the lkpinstall command after installation or upgrade) to install LKP, prior to installing the Volution Manager Server. A Volution Manager Client can be run on the Unix side using the Volution set installed from CD #1 or CD #2 (see Volution Manager Client).
To install the Volution Manager Server from the supplied CD, and then start the Unix Volution Client, follow these steps:
Select the KDE2 and Linux Personality (LKP) session option in the CDE login screen, and log in as root.
Edit the file /unixware/etc/default/linuxrc and remove httpd, ldap, slpd, and tomcat. This lets the needed daemons run under LKP.
Mount the Volution Manager CD on /mnt/cdrom.
Enter the following:
cd /mnt/cdrom/server ./install.sh
This begins the Volution Manager Server installation; follow the prompts shown. After displaying a message indicating that installation is complete, a screen titled Postinstall Diagnostics appears and may hang. This will appear after a message indicating that installation is complete, and does not affect operation of the Volution Manager server. If this screen does hang, switch to another terminal before going to the next step.
Note that after the installation is complete, the Volution Manager Linux client runs under LKP; this misleads Volution Server into treating the system as if it were a Linux system. The Linux client will not be restarted after rebooting, but you do need to remove the computer object in the Volution Manager database that was created for the system before starting the Unix client. This is done in a later step.
Reboot the system:
shutdown -i6 -g0 -y
Remove the computer object from the database before starting the Unix client:
Click on the Delete this object task to remove the computer object.
To access the server from the Unix Volution client:
pkginfo Volution
If no information is found for Volution, install the client as shown in the section Volution Manager Client.
/etc/init.d/volutiond enable /etc/init.d/volutiond start
Release 7.1.3 includes the following software on CD-ROM. The package or set name used to manually install the indicated software or documentation using the pkgadd command is shown in parentheses in the table below, as appropriate.
| Base Operating System Installation CD #1 | |
|---|---|
|
This is the first CD-ROM to insert during a fresh install of UnixWare 7
(see Installation).
This CD is also used to stage the base operating system for a network install.
Individual packages from this CD can also be installed after a fresh install using pkgadd(1M), but it is recommended that all desired packages be selected during the fresh or upgrade installation process. If you add packages after installation, you'll need to reapply the UpdateSet (from the Updates CD #2). A copy of the product release notes (the document you are reading now) is included in the file relnotes.html at the top of the CD #1 directory structure. The /info directory on the CD-ROM contains additional notes, copies of software licenses, and other important information. See /info/readme.htm on the CD. |
| Base Operating System and Updates CD #2 | |
|
This is the second CD inserted during a fresh install, and the CD used
for an upgrade install.
Upgrade installs should be performed using the Upgrade Wizard
(see Installation).
Individual packages from this CD can also be installed after a fresh install
using pkgadd(1M), but it is recommended that all desired packages
be selected during the fresh or upgrade installation process.
If you add packages after installation, you'll need to reapply the
UpdateSet (from the Updates CD).
If you select LKP, then you will be prompted for the OpenLinux CD as well before installing the Optional Services CD. The /info directory on the CD-ROM contains product release notes, copies of software licenses, and other important information. See /info/readme.htm on the CD. |
| Optional Services CD #3 | |
|
After loading all required software from the Updates CD (and possibly
the Linux Distribution CD), a fresh installation will prompt for
installation of desired packages from the Optional Services CD.
Individual packages from this CD can also be installed after a
fresh or upgrade installation is completed,
using pkgadd(1M).
The /info directory on the CD-ROM contains English and other language files that provide product release notes, copies of software licenses, and other important information. See /info/readme.htm on the CD. |
| Linux RPM CD #4 | |
| OpenLinux Server 3.1.1 Distribution for use with LKP | Inserted during the installation of LKP from the Upgrade CD. Contains all RPMs for LKP. The Release Notes for OpenLinux 3.1.1 can be found at http://www.sco.com/support/docs/openlinux |
| UnixWare 7 Development Kit CD | |
|
All packages installed using pkgadd(1M) after UnixWare 7
installation or upgrade.
Installing the udk set leads you through the installation of all
packages on the CD.
gcc supports C, C++, Fortran, and Objective C; no java front end is provided. binutils supports gas, nm, strip, demanglers, ranlib, size, objdump; does not provide ld (to avoid confusion with the UnixWare 7 ld). |
If your system does not support a bootable CD-ROM, the following 3.5-inch diskettes images are provided on CD #1; these allow you to start the installation from a 3.5-inch diskette drive. See the /info/images/readme.txt file on the Base OS Installation CD (CD #1) for how to transfer the images to diskettes. These diskettes are not necessary if you start a fresh installation by booting your system from CD #1.