This section contains information about UnixWare 7.1.4 Maintenance Pack 1 that became available after this product was made available.
The online documentation distributed with MP1 in the uw7mpdoc package incorrectly states that MP1 contains two versions of the Samba package, one enabled for PAM (Pluggable Authentication Modules) and NSS (Name Service Switch), and one that is enabled for multibyte characters. This is incorrect; there is only one Samba package (samba), and it is both PAM-enabled and multibyte-enabled. No changes were made to this package for NSS.
The openssh package (version 3.8.1p1) available with MP1 installs the binary /usr/sbin/ssh-keysign with incorrect ownership (bin), and this causes Host Based Authentication using SSH to fail. To correct this problem, enter the following command as root:
chown root /usr/sbin/ssh-keysign
This document contains UnixWare 7.1.4 and UnixWare 7.1.3 Update Pack 4 feature descriptions, procedures, limitations and workarounds that became available after these products were shipped to customers.
Most of these notes apply to both products; the notes under "Installing UnixWare 7.1.4" apply only to a new installation of Release 7.1.4 from the Media Kit CD-ROMs. The notes under "Upgrading to UnixWare 7.1.4" apply to a system upgraded using either the UnixWare 7.1.4 media or UnixWare 7.1.3 Update Pack 4.
The numbers shown after some notes indicate the incident tracking number associated with the note.
The NetBIOS protocol is required by the Advanced File and Print Server (AFPS) product. A problem with the NetBIOS protocol causes a system PANIC if you enter init 1 when NetBIOS is running. The workaround is to enter the following command before changing to init state 1:
netbios stop
529565
The ProDVD version of the cdrtools package is provided with UnixWare 7.1.3 Update Pack 4 and on the Updates CD #2 in the UnixWare 7.1.4 media kit. This version of cdrtools supports reading and writing Digital Video Disc (DVD) format media. DVD-R, DVD+R, DVD-RW, and DVD+RW media are supported for writing.
The following manual pages are provided by the cdrtools package:
| cdda2wav(1) | a sampling utility that dumps CD audio data into wav sound files |
| cdda2ogg(1) | extract audio CD audio tracks and encode them |
| cdrecord(1) | record audio or data Compact Discs from a master |
| readcd(1) | read or write data Compact Discs |
| scgcheck(1) | check and validate the ABI of libscg |
| makefiles(4) | users guide for compiling projects on different platforms |
| makerules(4) | system programmers guide for compiling projects on different platforms |
| isoinfo(8) | Utility programs for dumping and verifying iso9660 images |
| mkisofs(8) | create an hybrid ISO9660/JOLIET/HFS filesystem with optional Rock Ridge attributes |
Note that an SCO Update Service license is required to install cdrtools 2.01a27 from the
Update Pack 4 media (no additional license is required to install cdrtools from the UnixWare
7.1.4 CD #2).
529316
Please observe the following notes when installing Mozilla during an upgrade to UnixWare 7.1.4 from a previous release of UnixWare:
Mozilla isn't automatically selected for installation during a uli upgrade if Netscape Communicator is already installed. If Mozilla is desired, it should be selected from the uli package menu. However, note that the CDE taskbar and Panorama desktop are always updated to invoke Mozilla (and not Netscape) for displaying local documentation and web browsing.
If you do not upgrade to Mozilla, follow these instructions to re-enable Netscape for CDE and Panorama desktops:
When Mozilla is installed during an upgrade, Java plug-in support will not be available if the j2jre131 and j2plg131 packages were not previously in- stalled and updated to version 1.3.1.10 during the upgrade. If Java plug- in support is desired, the updated j2jre131 and j2plg131 packges should be installed (in that order) from the media. However, if any of the Java 1.4.2 packages were installed during the upgrade, this may change the default Java for other applications from 1.4.2 back to 1.3.1.
The default Java can be verified by:
# java -version
and changed to version 1.4.2 by:
# rm /usr/java /usr/java2
# ln -s /opt/java2-1.4.2 /usr/java
# ln -s /opt/java2-1.4.2 /usr/java2
or to version 1.3.1 by:
# rm /usr/java /usr/java2
# ln -s /opt/java2-1.3.1 /usr/java
# ln -s /opt/java2-1.3.1 /usr/java2
This release of UnixWare contains both updated Java 1.3.1 packages, as well as new Java 1.4.2 packages. If you installed one or more of the Java packages, you can check which version is the default version of Java by entering this command:
java -version
The command will return with the appropriate release, depending on whether /usr/java is linked to /opt/java2-1.3.1 or /opt/java2-1.4.2. For example, to change the default Java from release 1.3.1 to release 1.4.2, enter the following commands, logged in as root:
# rm /usr/java # ln -s /opt/java2-1.4.2 /usr/java # rm /usr/java2 # ln -s /opt/java2-1.4.2 /usr/java2
If you update the links as in the example above to switch the active Java release, you should also remove and re-install the javaxcomm package, if it is on your system, so that it runs on the default Java version:
# pkgrm -n javaxcomm # pkgadd -q -d pathname javaxcomm
Where pathname is the full path to the javaxcomm package.
If you upgrade a system with an older version of openssh installed, the installation will succeed, but when an OpenSSH utility is launched, you'll get an error or warning. This is due to the fact that the configuration files changed location between older and newer version of OpenSSH. For example, ssh might display the following after upgrade:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. etc....
To fix this problem, enter the following to move your configuration files to the /etc/ssh directory:
mv /etc/ssh_* /etc/sshd_* /etc/ssh/
During a fresh installation of UnixWare, you can choose to configure the installed as a Dynamic Host Configuration Protocol (DHCP) client, instead of specifying an IP address and other network parameters. When the system boots, it will get its IP address and other network parameters (depending on your DHCP setup) from the DHCP server on the subnet. The following files, which are required by some system utilities (such as the CDE desktop), may not be automatically configured during a DHCP install:
For example, attempting to launch most CDE desktop utilities will fail with the following error message:
The request to service this action has failed. A ToolTalk connection could not be established.
If your DHCP server is not configured to provide appropriate entries for these files via DHCP, then you must configure these files manually after the newly installed system boots. You can edit them manually, or use the scoadmin client manager to create them. Consult the resolv.conf(4) and hosts(4) manual pages, and your local network administrator, for more information.
Once you have a UnixWare 7.1.4 system installed, you can set up the system as a Network Install Server and install other systems on the network from the Install Server. The contents of CD #1 through CD #3 can be staged using the installsrv(1M) command as shown in this section. This procedure assumes that the client to be installed can be booted from CD #1 or the Network Installation Diskettes (images of which are included on CD #1 under /info/images) to begin the installation.
Make sure the server package is installed:
pkginfo server
If it is not installed, install it from Base Operating System CD #1, by inserting CD #1 into the primary CD drive and entering:
pkgadd -d cdrom1 server
Make sure there is enough free space in the /var/spool/dist file system to hold the contents of all the CDs you want to offer for network install (2.5GB for CD #1 through CD #3). Also ensure that /tmp is at least 200MB in size (the default /tmp is adequately sized).
Insert the Base Operating System CD #1 into the primary CD-ROM drive. Enter the following command:
installsrv -ue
The -u option to installsrv copies the base operating system (UnixWare.package), the Release 7.1.4 UpdateSet, the Apache server, the Mozilla browser, the English Documentation Set (doc), and the localized documentation set (LocalDoc). The installsrv command displays the set and package names as it copies software from CD #1 to /var/spool/dist:
/var/spool/dist/UnixWare7/C/UnixWare.package
/var/spool/dist/extra.d.cpio
/var/spool/dist/UpdateSet
Transferring <apache> package instance to
</var/spool/dist/UnixWare7/C/apache.package> in datastream format
...
When installsrv is done copying from CD #1, remove CD #1 from the CD drive.
To stage the contents of the Upgrade CD #2 for network install, insert CD #2 into the primary CD drive and enter:
installsrv -2
When installsrv is done copying from CD #2, remove CD #2 from the CD drive.
To stage the contents of the Optional Services CD #3 for network install, insert CD #3 into the primary CD drive and enter:
installsrv -3
When installsrv is done copying from CD #3, remove CD #3 from the CD drive.
Check the Install Server:
installsrv -q
This should print the server's current status, and a list of the packages staged:
UX:installsrv: INFO: TCP networking is enabled UX:installsrv: INFO: Service inetinst is enabled for TCP /var/spool/dist/UnixWare7/C/LocalDoc.package: Locale: C Localized Documentation Services /var/spool/dist/UnixWare7/C/UnixWare.package: Locale: C Core Systems Services /var/spool/dist/UnixWare7/C/apache.package: Locale: C Apache Web Server /var/spool/dist/UnixWare7/C/doc.package: Locale: C Documentation Services ...
See the installation procedure in the Getting Started Guide. This book also shows you how to create network installation diskettes, if needed.
Network installation onto systems of 16MB or less is not supported.
Installations performed over the network will automatically prompt for CD #1, CD #2, and CD #3 packages. Packages from other CDs (such as the UDK CD) can be copied using installsrv -l to /var/spool/dist on the system running the Install Server, and installed over the network using pkginstall(1M) or the scoadmin application installer.
While the Linux Kernel Personality (LKP) can be staged on the network server from CD #2, the Linux RPM CD #4 cannot be staged for network install using installsrv and the UnixWare installation tools. If it is desired to install software from the Linux RPM CD over the network, this must be done using Linux installation tools (such as rpm) from the Linux Kernel Personality (LKP). The UnixWare installation tools cannot install Linux packages.
Network installation is not supported onto systems that use the Token-Ring or FDDI network topologies.
The example procedures in this document load the operating system and package images onto the hard disk of the Install Server system. You can also use the -c mount and -r cdrom[1-9] options to stage the images directly from a CD in any one of the first nine CD drives installed on your system. For example, this command:
installsrv -ue -c mount -d cdrom2
Will link all the software on the CD found in /dev/cdrom/cdrom2 to /var/spool/dist, and the CD will be mounted until the Install Server is disabled (using the -d option).
If there is another UnixWare 7.1.4 Install Server on your network, you can also load images from that server using a command like the following:
installsrv -ue -s servername
The Media-less PXE network install feature allows you to install a system without any installation media, by setting up the system so that it boots itself from a boot image offered by a Unixware Install Server. To do this, you need to:
Set up Dynamic Host Configuration Protocol (DHCP) and Address Allocation (AAS) servers on the same subnet as the Install Server and clients to be installed.
Setup the Install Server on the host UnixWare system.
Setup the client to be installed, and begin the network install.
These tasks are described in the following three sections. Also see the section Network Installation Notes.
A DHCP server must be setup on the same subnet as the Install Server and all clients to be installed. It tells the clients which system holds the bootable Unixware image and other needed files for network boot. The DHCP server usually works with an AAS to access a pool of IP address specifically reserved for dynamic allocation on the subnet.
This section shows you how to set up DHCP and AAS servers on a UnixWare 7.1.4 system. You can configure these servers on the same system running the Install Server, or set them up on any other system on the subnet. The important point being that the DHCP server refers PXE install clients to the UnixWare Install Server and the directories shown in the examples below.
Login as root and launch the SCOadmin Address Allocation Manager from the desktop, or using:
scoadmin address &
Use the Pools > Add menu command to define a range of IP addresses as a named Pool. Type a Pool name into the Address Pool Configuration screen, and then select Add to define the IP addresses in the pool. Select OK when you are done.
From the main AAS screen, select Server > Start Server if the AAS is not running. If the AAS is already running, select Server > Reconfigure. Once you've started or reconfigured the server, select Host > Exit to quit the Address Allocation Manager.
Launch the SCOadmin DHCP Manager from the desktop, or using:
scoadmin dhcp &
Use the Edit > Add menu command to add a subnet configuration. If a configuration already exists for the subnet, make sure it is selected in the display and use Edit > Modify.
Type in appropriate values for Subnet and Mask, and choose the Address Pool that you defined in Step 2, above.
Select Lease and set the following values:
Select OK when you are done.
Select Generic and set the following values:
Select OK when you are done.
Select Generic and set the following values options and values. Do this by selecting the options shown below in the list at left, and moving them using the Add button to the list on the right. When you select an option and then Add, a screen pops up that alows you to set the value of the option. Set the value as indicated below, and click OK. Do this for each option/value in this list:
Select OK when you are done.
Go to the next section.
Do the following on the UnixWare 7.1.4 system hosting the Install Server:
Make sure the server package is installed:
pkginfo server
If it is not installed, install it from Base Operating System CD #1, by inserting CD #1 into the primary CD drive and entering:
pkgadd -d cdrom1 server
Make sure there is enough free space in the /var/spool/dist file system to hold the contents of all the CDs you want to offer for network install (2.5GB for CD #1 through CD #3). Also ensure that /tmp has at least 200MB of free space.
Insert the Base Operating System CD #1 into the primary CD-ROM drive. Enter the following command:
installsrv -bue
The -u option to installsrv copies the base operating system (UnixWare.package), the Release 7.1.4 UpdateSet, the Apache server, the Mozilla browser, the English Documentation Set (doc), and the localized documentation set (LocalDoc). The installsrv command displays the set and package names as it copies software from CD #1 to /var/spool/dist:
/var/spool/dist/UnixWare7/C/UnixWare.package
/var/spool/dist/extra.d.cpio
/var/spool/dist/UpdateSet
Transferring <apache> package instance to
</var/spool/dist/UnixWare7/C/apache.package> in datastream format
...
When installsrv is done copying from CD #1, remove CD #1 from the CD drive.
To stage the contents of the Upgrade CD #2 for network install, insert CD #2 into the primary CD drive and enter:
installsrv -2
When installsrv is done copying from CD #2, remove CD #2 from the CD drive.
To stage the contents of the Optional Services CD #3 for network install, insert CD #3 into the primary CD drive and enter:
installsrv -3
When installsrv is done copying from CD #3, remove CD #3 from the CD drive.
Check the Install Server:
installsrv -q
This should print the server's current status, and a list of the packages staged:
UX:installsrv: INFO: TCP networking is enabled
UX:installsrv: INFO: Service inetinst is enabled for TCP
UX:installsrv: INFO: Network boot is enabled
/var/spool/dist/UnixWare7/C/LocalDoc.package:
Locale: C Localized Documentation Services
/var/spool/dist/UnixWare7/C/UnixWare.package:
Locale: C Core Systems Services
/var/spool/dist/UnixWare7/C/apache.package:
Locale: C Apache Web Server
/var/spool/dist/UnixWare7/C/doc.package:
Locale: C Documentation Services
...
/var/spool/dist/UpdateSet:
UnixWare 7.1.4 Update Set
/var/spool/dist/extra.d.cpio:
CD-ROM /.extra.d/* files
/var/spool/dist/boot.cd.image:
Network boot support
Note the INFO messages and the entry for /var/spool/dist/boot.cd.image, which indicate that the Install Server is enabled for media-less installations over TCP.
Go to the next section.
In order to install a system over the network, the Network Interface Card (NIC) on the system to be installed must support the PXE 2.1 standard. Check the documentation for your networking card.
If your network card does not support PXE 2.1, you must update the card's BIOS to include PXE 2.1 support (or use another card). Most network card vendors offer BIOS upgrades on their web sites. Updates for older Intel Pro/100 cards, for example, are available from http://www.intel.com. Use the Search box on the manufacturer's web site to find your network card and the manufacturer's available updates. Instructions for applying the updates are provided by the manufacturer.
The system to be installed must also be on the same subnet as the DHCP server and Install Server defined in the previous two sections.
Reboot the system to be installed, and enter the system BIOS. Enable booting from the network in the system's BIOS, save your changes, and reboot.
As the system comes up and displays the PXE agent information on the console, you must press the key required by the BIOS to begin the PXE boot process. When you press this key, the boot request is sent to the DHCP server, which should respond with the location of the boot server and the name of the boot file (as set above). The network install process will then start as the system to be installed contacts the UnixWare Install Server and downloads the network bootable image.
Continue the installation beginning with Step 2 of the installation procedure in the Getting Started Guide.
During installation, the system attempts to automatically configure your mouse. If a USB Mouse is detected or manually selected, the system may hang. This is caused by an IRQ conflict between the USB EHCI device and another device. To fix this problem, restart the installation and when prompted to enter the Device Configuration Utility (DCU), select Yes. At the DCU main menu, select Hardware Device Configuration. Look through the table of devices for USB entries that are sharing an IRQ with another device. Below is a partial example of a DCU screen:
Hardware Device Configuration
Device Name IRQ IOStart IOEnd MemStart MemEnd DMA
= ==================== === ======= ===== ======== ======== ===
.
.
.
Y UNKNOWN irq
Y USB EHCI device irq
.
.
.
The irq values shown in the screen will be the same for the conflicting entries. Change the Y next to the UNKNOWN device to an N to remove the device from the current configuration. Press F10 to exit tdevice to an N to remove the device from the current configuration.he Hardware Device Configuration screen. From the DCU mainmenu, select Apply Changes & Exit DCU, and continue the installation. The USB mouse should now be enabled properly. 529243
If your system console, mouse, and keyboard are connected to a multiscreen switch, then the
system may become unresponsive when the system attempts to detect your mouse (just after CD #1 is loaded).
If this occurs, the workaround is to reboot the system, restart the installation, and press any key
when the UnixWare logo appears.
When the [boot] prompt is displayed, enter the following:
[boot] IVAR_MOUSE=manual [boot] boot
This will bypass mouse autodetection and allow you to manually configure your mouse during installation. 529265
If a server's serial controller is statically set to "edge-triggered", then the
install will fail when the installation program attempts to access the hard disk.
To work around this, press any key when the UnixWare logo is displayed at the beginning of the
installation process, and enter the following at the [boot] prompt:
[boot] ASYC_EDGE=Y [boot] boot
After booting the system for the first time, the system BIOS should be changed
so that the serial controller is programmed for "level-sensitive".
529113
When installing Unixware 7.1.4 on a system with multiple processors, you may see the following message:
p6update: ERROR: Cannot bind to processor 1
There are two conditions under which this error message may be seen:
If you are doing a fresh installtion of UnixWare 7.1.4, have interrupted the boot sequence
to set the PSM=MPS boot parameter, and the system has
multiple processors, you will see the message as the system first
comes up. This operation is normally only performed when doing
ISL on an IBM xSeries Server with a root drive attached to an
HBA that is installed in an attached RXE-100 PCI Expansion Enclosure
(also known as a Lookout Box). In this case the message can be safely ignored and will
not appear again after the first reboot.
There has been a CPU licensing problem and there are multiple processors present in the system. In this case, the licensing problem must be corrected for the remaining CPUs can be brought online. Launch the License Manager (scoadmin license) and ensure that your system is properly licensed for the number of processors you have installed. Re-installing any additional CPU licenses may be necessary. Contact your software supplier if you have problems with additional CPU licenses.
528882
A new Small Business Edition and updates to the licensed defaults for other UnixWare License Editions are described in Chapter 2 of the Getting Started Guide. These changes apply to all UnixWare 7.1.4 systems, whether newly installed or upgraded from a previous release. Also note the following changes to UnixWare licensing:
The number of concurrent users, number of processors, and amount of memory supported with the 60-day evaluation license have been updated to:
| Number of concurrent users | 10 (previously 5) |
|---|---|
| Number of processors | 4 (previously 1) |
| Amount of memory | 4 GB (previously 1) |
The UnixWare Development Kit (UDK) is not enabled by a 60-day evaluation license. A separate UDK license must be purchased to install the UDK.
For a list of available UnixWare 7.1.4 Product Licenses, License Packs, and Upgrade Licenses see the Model Numbers Master List.
The Linux RPM CD #4 has been removed from the UnixWare 7.1.4 Media Kit. The Linux Kernel Personality (LKP) should not be selected from UnixWare 7.1.4 Updates CD #2 during either a fresh or upgrade installation of UnixWare 7.1.4.
If LKP is selected, the base LKP packages will be installed from CD #2, but the installation of RPMs from the Linux RPM CD #4 must be deferred (by pressing F8 at the prompt to insert the Linux RPM CD).
The scoadmin Address Allocation Manager may fail with a tcl error when executed from the graphical desktop. The workaround is to execute scoadmin in character mode, either from a terminal window or the graphical desktop:
# CHARM=TRUE scoadmin address
Or, by running scoadmin address on the text console.
The IPsec (Secure IP) manual pages for racoon(8) and setkey/ipseckey(8) are installed in the wrong location, and are not found by the man(1) command or in DocView. To fix this problem, enter the following three commands as root:
cp /usr/share/doc/unixware/en/NET_ipsec/*.8.html /usr/man/html.8 cp /usr/man/html.8/setkey.8.html /usr/man/html.8/ipseckey.8.html makewhatis /usr/man/html.8
By default, /etc/nsswitch.conf is not configured, and the Network Information Service (NIS) works normally. When the Name Service Switch feature and /etc/nsswitch.conf are configured, however, NIS will work only in compatibility mode. The /etc/nsswitch.conf file should contain entries like these for NIS:
#passwd: nis files #group: nis files passwd: compat group: compat #passwd: nis #group: nis
529319
On systems with fast processors where Network Information Service (NIS) files are maintained and updated using scripts, the ypbuild command may not properly detect recent changes. The problem occurs if you start ypinit, immediately make changes to NIS information (e.g., add a user), and run ypbuild all within a second, as is possible within a script. In this case, ypbuild thinks it has no updates to process.
The workaround is to execute a
sleep 1
command after running ypinit and before making any changes that affect information maintained by NIS.
529319
The Networking topic in the online documentation at http://localhost:8458 may not contain an entry for the Lightweight Directory Access Protocol (LDAP) documentation due to a misconfiguration. To fix this problem, enter the following commands, as root:
cd /usr/share/doc/unixware/en/NET_ldap cp openldapindex.html CONTENTS.html doctool --add HelpTopics/NEThome/NETgroup/NET_ldap.desktop
Reload DocView in your browser and the LDAP documentation should now appear under Networking.
The udkdoc package on the UDK CD may not be configured properly into DocView (http://localhost:8458). The UDK documentation titles may not appear under Software Development, and UDK documentation may not be found when accessed via the Search mechanism. To fix this problem, run the following command, as root, after installing the udkdoc package:
doctool --add UWDeveloper/.directory
Reload DocView in your browser and the UDK documentation should now appear under Software Development.
To install and use the UDK on UnixWare 7.1.3 Update Pack 4, you must also download and insstall the following packages from ftp://ftp.sco.com/pub/unixware7/713/uw713up/:
Once you download the packages, install them using the following commands:
pkgadd -qd download-directory-path/syshead.image pkgadd -qd download-directory-path/uccs.image
If you do not install the above packages with the UDK, undefined symbol errors will occur during compilation of programs that use any of the new or changed interfaces in Update Pack 4.
An upgrade to UnixWare 7.1.4 may fail if you use the License Manager to enter your upgrade license
before beginning the upgrade.
If your upgrade fails, enter the License Manager (scoadmin license) and check to see if an
upgrade license for UnixWare 7.1.4 is already installed.
If it is, select the upgrade license from the list and use the License -> Remove command to remove it.
Then, start the upgrade again.
When prompted, enter your license information and the installation should continue normally.
529204
If you use a CD-ROM image file of Upgrade CD #2 to upgrade your system to Unixware 7.1.4 and invoke the Upgrade Wizard using:
uli -f mount-point
After all software from CD #2 is installed, the Upgrade Wizard may display the following message:
Incorrect Media Detected
This occurs because the Upgrade Wizard is looking for an image of CD #3, which is not present. When you encounter this message, you can either:
Defer the installation of CD#3.
Open another shell (either on a console VT or in another window, if you are using a desktop), without exiting the Upgrade Wizard. Use the umount command to unmount the CD#2 image at mount-point, and then use the mount command to mount the CD#3 image at the same mount-point. For example, in the directory where the CD#3 image resides, enter:
mount `marry -a CD#3-image-name` mount-point
You can then continue with the installation of CD#3 using the existing Upgrade Wizard session.
529173
When upgrading a UnixWare 7.1.1 system, make sure that the Linux Kernel Personality (LKP) is not selected for installation to avoid seeing the error described below. (Upgrades from other previous releases are not affected by this problem.) After the upgrade is complete, you can install LKP manually from CD #2 using the following command:
lkpinstall
If LKP is selected during upgrades from UnixWare 7.1.1, the following message may be seen:
Installation of Linux Initial Setup on system as package instance <lxsetup> failed.
The file /var/sadm/install/logs/lxsetup.log may contain this error:
UX:pkginstall: ERROR: postinstall script did not complete successfully
The workaround is to reboot the system and install LKP manually as instructed above.
529197
when upgrading a system with the Linux Kernel Personality (LKP) already installed, it is possible to encounter one or more error messages like the following:
UX:ln: ERROR: Cannot create /linux/pathname: File exists
Such messages can be safely ignored.
Running the Upgrade Wizard (uli) on the text console in CHARM (character Motif) mode with X windows running will result in the static display elements (title, line borders, etc.) disappearing after the xserver package is updated. The dynamic elements (e.g., the package name and number) will continue to display. This is a cosmetic problem and does not otherwise affect the upgrade. To avoid the problem, uli can either be run from the graphical desktop, or can be run on the text console by temporarily stopping the X server before starting uli:
# scologin stop # uli
The X server will start again when the system is rebooted after the upgrade.
The Upgrade Wizard (uli) doesn't always prompt for the Linux RPMs CD #4 when the Linux Kernel Personality (LKP) is selected. Also see LKP CD Removed from Media Kit. 529369
© Copyright 2004 The SCO Group, Inc. All rights reserved.