This chapter describes problems that relate to the installation of the Solaris 9 9/02 operating environment.
The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 9 9/02 Documentation CD and in the Installation Kiosk on the Solaris 9 9/02 Installation CD.
The Solaris 9 9/02 operating environment requires a memory size of 128 Mbytes or greater.
By default, the Solaris 9 9/02 installation program places swap starting at the first available disk cylinder, which is typically cylinder 0. This placement provides maximum space for the root (/) file system during the default disk layout and enables the growth of the root (/) file system during an upgrade.
If you think you will need to expand swap space in the future, you can place the swap slice so that it starts at another disk cylinder by using one of the following methods.
For the SolarisTM Web Start and SunInstallTM installation programs, you can customize the disk layout in cylinder mode and manually assign the swap slice to the desired location.
For the Solaris Custom JumpStartTM installation program, you can assign the swap slice in the profile file.
If you are creating a mirrored root (/) file system, see "Solaris Volume Manager metattach Command Might Fail".
For more information on the Solaris Custom JumpStart profile file, see the Solaris 9 Installation Guide.
If you use the default Solaris JumpStartTM profile on the Solaris 9 9/02 media to install multiple locales on a system with a small disk, the installation might fail. This problem might occur under the following conditions.
You use the default Solaris JumpStart profile to install any locale other than the C locale on a system with a 2.1 Gbyte disk.
You use the default Solaris JumpStart profile to install two or more locales on a system with a 4 Gbyte disk.
The Solaris 9 9/02 operating environment is now available on DVD. To install or upgrade from DVD, insert the Solaris 9 9/02 DVD into the DVD-ROM drive and boot the system from the ok prompt with the following command.
ok boot cdrom |
If you use the SolarisTM Web Start program on the Solaris 9 9/02 Installation CD to install the Solaris 9 9/02 operating environment, the system might hang on the first reboot after the installation.
Workaround: To avoid this problem, choose one of the following workarounds.
Use the Solaris 9 9/02 Software 1 of 2 CD to install the Solaris 9 9/02 operating environment.
If you use the Solaris 9 9/02 Installation CD to install the Solaris 9 9/02 operating environment, follow these steps.
Insert the Solaris 9 9/02 Installation CD in your CD-ROM drive and begin to install the Solaris 9 9/02 operating environment.
Write down the name of the disk slice when the following message is displayed.
Disk slice disk-slice-name will be used to accommodate a temporary copy of the Solaris installation software. After the files are copied, the system will reboot and the installation will continue. Please Wait... |
Interrupt the installation by pressing Stop-A or by power cycling the system.
The system displays the ok prompt.
Boot the system from the Solaris 9 9/02 Installation CD in standalone mode.
ok boot cdrom -s |
In a terminal window, type the following ls command to determine the physical name of the disk slice you wrote down in step 2.
# ls -l /dev/dsk/disk-slice-name |
This command returns output similar to the following text.
lrwxrwxrwx 1 root root 2 Aug 14 16:56 /dev/dsk/disk-slice-name -> ../../devices/physical-name |
Write down the physical name of the disk slice. Omit the leading text ../../devices from the physical name
Halt the system to return to the ok prompt.
# halt |
Boot the system from the physical device by typing the following command.
ok boot /physical-name |
NetscapeTM version 6.2.3 base and localization packages are now available in the Solaris_9/ExtraValue/CoBundled/Netscape_6 directory of the Solaris 9 9/02 Software DVD and the Solaris 9 9/02 Software 2 of 2 CD. However, the NS62installer script in the Solaris_9/ExtraValue/CoBundled/Netscape_6 directory installs only the base packages on the system.
Workaround: Use the pkgadd(1M) command to install the Netscape version 6.2.3 localization packages on your system. Follow these steps.
Become superuser.
Insert the Solaris 9 9/02 Software DVD or the Solaris 9 9/02 Software 2 of 2 CD.
Change to the directory where the localization packages are located.
# cd /cdrom/Solaris_9/ExtraValue/CoBundled/Netscape_6/Packages |
Use the pkgadd command. Specify the name of the package you want to install.
# pkgadd -d . name-of-localization-package |
The following localization packages are in the Packages directory.
SUNWcns6 - Simplified Chinese localization
SUNWdens6 - German localization
SUNWesns6 - Spanish localization
SUNWfrns6 - French localization
SUNWhns6 - Traditional Chinese localization
SUNWitns6 - Italian localization
SUNWjans6 - Japanese localization
SUNWkons6 - Korean localization
SUNWplns6 - Polish localization
SUNWptns6 - Brazilian Portuguese localization
SUNWruns6 - Russian localization
SUNWsvns6 - Swedish localization
If your system has a Toshiba SD-M1401 DVD-ROM drive with firmware revision 1007, the system cannot boot from the Solaris 9 9/02 DVD.
Workaround: Apply patch 111649-03, or a later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. Patch 111649-03 is included on the Solaris 9 9/02 Supplement CD in the following directory.
DVD_Firmware/Patches |
See the README file in this directory for instructions on how to install the patch. Be sure to read and follow all the cautions and warnings in this README file before you install the patch.
If your system is running the Solaris 2.6 or Solaris 7 operating environment, Volume Management incorrectly mounts the Solaris 9 9/02 DVD. The Solaris 9 9/02 DVD can be mounted, but the data is inaccessible. As a result, you cannot set up an install server, perform a Live Upgrade, or access any data on the media.
Workaround: Choose one of the following workarounds.
Apply the patches that are appropriate for your system.
Table 1-1 DVD patches for the Solaris 2.6 and Solaris 7 Operating Environments
Release |
Patch ID |
---|---|
Solaris 2.6 operating environment |
107618-03 |
Solaris 7 operating environment |
107259-03 |
Do not use Volume Management to mount the Solaris 9 9/02 DVD. Manually mount the Solaris 9 9/02 DVD. Follow these steps.
Become superuser.
Stop Volume Management.
# /etc/init.d/volmgt stop |
Manually mount the DVD.
# mkdir /mnt1 # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /mnt1 |
Verify that the DVD is mounted and the data is accessible.
# cd /mnt1 # ls |
The system returns the following information if the DVD is correctly mounted.
Copyright Solaris_9 |
If you install or upgrade to the Solaris 9 9/02 operating environment on a system with multiple network interfaces, the system recognizes all system interfaces as usable. Interfaces that are not plugged in to the network, or that are not intended for use, appear in the output of the ifconfig -a command. Additionally, interfaces with identical Ethernet addresses might be assigned identical IP addresses. The following error message is displayed.
ifconfig: setifflags: SIOCSLIFFLAGS: qfe3: Cannot assign requested address |
This problem also occurs on systems that have the local-mac-address
PROM variable set to false. The problem occurs
because all interfaces are configured with the same IP address.
Workaround: Choose one of the following workarounds.
To plumb only the configured interface, reboot the system after the initial boot.
To assign a different IP address to each network interface,
set the local-mac-address
PROM variable to true in one of the following ways.
At the ok prompt, type the following command.
ok setenv local-mac-address? true |
In a terminal window, type the following command as superuser.
# eeprom local-mac-address?=true |
When a file system is created during installation, one of the following warning messages might be displayed.
Warning: inode blocks/cyl group (87) >= data blocks (63) in last cylinder group. This implies 1008 sector(s) cannot be allocated. |
Or
Warning: 1 sector(s) in last cylinder unallocated |
The warning occurs when the size of the file system that you created does not equal the space on the disk that is being used. This discrepancy can result in unused space on the disk that is not incorporated into the indicated file system. The unused space is not available for use by other file systems.
Workaround: Ignore the warning message.
If your Solaris 8 system is connected to storage area networks (SANs), check with your support engineer before you upgrade to the Solaris 9 9/02 operating environment. Solaris 8 systems with the SUNWsan package installed might require special procedures to upgrade to the Solaris 9 9/02 operating environment. To find out if the SUNWsan package is installed on your system, type the following command in a terminal window.
# pkginfo SUNWsan |
If the SUNWsan package is installed, the following information is displayed.
system SUNWsan SAN Foundation Kit |
Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you want to upgrade to the Solaris 9 9/02 operating environment, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.
Workaround: Choose one of the following workarounds.
Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.
If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 9 9/02 operating environment, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps.
Become superuser.
Type the following command.
# pkginfo | grep "Solaris Management Console" |
If the description does not start with "Solaris Management Console 2.1", the package names in the output identify a Solaris Management Console 1.0 package.
Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order.
Do not remove any package that has "Solaris Management Console 2.1" in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.
If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package and then remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.
# pkgrm SUNWmcman # pkgrm SUNWmcapp # pkgrm SUNWmcsvr # pkgrm SUNWmcsvu # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmcsws |
In a terminal window, type the following command.
# rm -rf /var/sadm/pkg/SUNWmcapp |
The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps.
Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order.
If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2. Do not use the prodreg command.
# pkgrm SUNWpmgr # pkgrm SUNWrmui # pkgrm SUNWlvmg # pkgrm SUNWlvma # pkgrm SUNWlvmr # pkgrm SUNWdclnt # pkgrm SUNWmga # pkgrm SUNWmgapp # pkgrm SUNWmcdev # pkgrm SUNWmcex # pkgrm SUNWwbmc # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmccom |
Insert the Solaris 9 9/02 Software (SPARC Platform Edition) 1 of 2 CD into your CD-ROM drive. Type the following in a terminal window.
# cd /cdrom/sol_9_902_sparc/s0/Solaris_9/Product # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex \ SUNWmcdev SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma \ SUNWlvmg SUNWpmgr SUNWrmui |
All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.
If you use Solaris Live Upgrade to install a Solaris Flash archive on a boot environment, the /etc/group file is not correct. The archive contains the /etc/group file that was archived and does not reflect the /etc/group file from the currently running boot environment. The /etc/group file on the boot environment must be identical to the file on the currently running system.
Workaround: After you install a Solaris Flash archive on a boot environment, you must copy the /etc/group file from the currently running system to the new boot environment. Follow these steps.
Become superuser.
Mount the boot environment that you want to patch
# lumount boot-envir-name mount-point |
In the previous command, boot-envir-name is the name of the boot environment whose file systems you want to mount. mount-point is the mount point of the file system.
Copy the /etc/group file from the currently running system to the new boot environment.
# cp /etc/group mount-point/etc/group |
Unmount the new boot environment.
# luumount boot-envir-name |
If you use the -s option with the luupgrade command to add patches with a directory and a patch list file, the patches are not added. A message similar to the following message is displayed:
/usr/sbin/luupgrade [52]: 3 patch-list-file: bad number |
In the previous message, patch-list-file is the patch list file you specified for the luupgrade command to use to add patches.
Workaround: To add patches specifying a patch list file, perform the following steps.
Become superuser.
Mount the boot environment that you want to patch.
# lumount boot-envir-name mount-point |
Add the patches to the boot environment.
# /usr/sbin/patchadd -R mount-point -M patch-path patch-list-file-name |
In the previous command, patch-path is the path name of a directory that contains patches to add. The patch-list-file-name is the file that contains the list of patches you want to add.
Unmount the boot environment.
# luumount boot-envir-name |
When you upgrade from the Solaris 8 operating environment to the Solaris 9 or the Solaris 9 9/02 operating environment, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file.
Removing package SUNWjxcft: Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias Removal of <SUNWjxcft> was successful |
Workaround: Ignore the error message.
In the Solaris 9 9/02 operating environment, the Kerberos version 5 global mechanism includes privacy support. Therefore, the Kerberos domestic mechanism is not needed. If you installed the Kerberos domestic mechanism that is located in /usr/lib/gss/do/mech_krb.so.1 on a Solaris 8 system, remove the Kerberos domestic mechanism before you upgrade the system to the Solaris 9 9/02 operating environment.
Workaround: Follow these steps before you upgrade to the Solaris 9 9/02 operating environment.
Type the following command to determine if the Kerberos domestic mechanism is installed on the system.
% pkginfo | fgrep ' SUNWk5' |
If the output of this command includes any SUNWk5 package names, the Kerberos domestic mechanism is installed on the system. Go to step 2.
If the output does not include any SUNWk5 package names, the Kerberos domestic mechanism is not installed on the system. Skip the rest of these steps. Upgrade the system.
Back up the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.
% tar -cf /var/tmp/krb_config_files.tar /etc/nfssec.conf /etc/gss/qop |
Verify that the files are backed up by typing the following command.
% tar -tf /var/tmp/krb_config_files.tar |
Remove each package that is listed in the output of step 1.
% pkgrm package-name package-name package-name |
Upgrade to the Solaris 9 9/02 operating environment.
The upgrade program updates the global Kerberos mechanism code and enables Kerberos privacy support.
In a text editor, change the following lines in the /etc/gss/mech file.
Uncomment the following line.
kerberos_v5 1.2.840.113554.1.2.2 gl/mech_krb5.so gl_kmech_krb5 |
If necessary, add the previous line to the /etc/gss/mech file.
Remove the following line.
kerberos_v5 1.2.840.113554.1.2.2 do/mech_krb5.so do_kmech_krb5 |
Restore the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.
% tar -xf /var/tmp/krb_config_files.tar |
The preremove scripts included in the Asian language packages of the Solaris 9 and Solaris 9 9/02 software do not execute properly during an upgrade with Disk Space Reallocation (DSR). If you attempt to upgrade to a newer release of the Solaris operating environment, the following error message is displayed in the /var/sadm/system/logs/update_log file.
Removing package SUNWkwbcp: /a/var/sadm/pkg/SUNWkwbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWkwbcp failed. pkgrm return code = 1 Removing package SUNWkbcp: /a/var/sadm/pkg/SUNWkbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWkbcp failed. pkgrm return code = 1 Removing package SUNWcwbcp: /a/var/sadm/pkg/SUNWcwbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWcwbcp failed. pkgrm return code = 1 Removing package SUNWcbcp: /a/var/sadm/pkg/SUNWcbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWcbcp failed. pkgrm return code = 1 Removing package SUNWhwbcp: /a/var/sadm/pkg/SUNWhwbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWhwbcp failed. pkgrm return code = 1 Removing package SUNWhbcp: /a/var/sadm/pkg/SUNWhbcp/install/preremove: /a/usr/4lib: does not exist pkgrm: ERROR: preremove script did not complete successfully Removal of SUNWhbcp failed. pkgrm return code = 1 |
Workaround: Ignore the error message.
If you upgrade to the Solaris 9 9/02 operating environment on a system that is running a third-party Secure Shell, such as OpenSSH, from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 9/02 upgrade software overwrites the contents of /etc/init.d/sshd.
Workaround: Choose one of the following workarounds.
If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.
If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.
If the /export directory is near full capacity, and you upgrade to the Solaris 9 9/02 operating environment, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed, or if third-party software is installed in the /export directory. The following message is displayed:
WARNING: Insufficient space for the upgrade. |
Workaround: Before you upgrade, choose one of the following workarounds.
Rename the /export directory temporarily, until the upgrade is completed.
Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.
If /export is a separate file system, then unmount /export before you perform the upgrade.
If your system currently supports diskless clients that were installed with the Solstice AdminSuiteTM 2.3 Diskless Client tool, you must first delete all existing diskless clients that are the same Solaris version and architecture as the server. Then, install or upgrade to the Solaris 9 9/02 operating environment. For specific instructions, see the System Administration Guide: Basic Administration.
If you attempt to install the Solaris 9 9/02 operating environment over existing diskless clients, the following error message might be displayed:
The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot be upgraded. There is an unknown problem with the software configuration installed on this disk. |
In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris operating environment.
If you upgrade from the Solaris 8 (Solaris WBEM Services 2.0), or the Solaris 8 6/00 (WBEM Services 2.1), operating environments to the Solaris 9 9/02 (Solaris WBEM Services 2.5) operating environment, your existing data is lost.
Workaround: Recompile the proprietary Managed Object Format (MOF) files after you perform an upgrade.
If your system is already running 64-bit ready firmware, then the flash PROM update is not required.
If you want to run the 64-bit Solaris operating environment on an UltraSPARC® system, you might need to update its flash PROM firmware. The Solaris 9 9/02 installation programs enable you to add 64-bit support. This 64-bit support is selected by default when you install on Sun UltraSPARC systems. A 64-bit system only boots in the 64-bit mode by default if it has a CPU speed of 200 MHz or greater.
If you choose to run the 32-bit Solaris operating environment on any SunTM or UltraSPARC system, the flash PROM update is not needed.
The following table lists the UltraSPARC (Sun4UTM) systems that are affected and the minimum firmware versions that are needed. System type is the equivalent of the output of the uname -i command. You can determine which firmware version you are running by using the prtconf -V command.
Table 1-2 Minimum Firmware Versions Required to Run 64-Bit Solaris Operating Environment on UltraSPARC Systems
System Type From uname -i |
Minimum Firmware Version From prtconf -V |
---|---|
SUNW,Ultra-1-Engine |
3.10.0 |
SUNW,Ultra-1 |
3.11.1 |
SUNW,Ultra-2 |
3.11.2 |
SUNW,Ultra-4 |
3.7.107 |
SUNW,Ultra-Enterprise |
3.2.16 |
If a system is not listed in the previous table, it does not need a flash PROM update.
For instructions on how to perform the flash PROM update by using the Solaris CD, refer to the Solaris 9 on Sun Hardware Collection. If you do not have this manual, you can obtain it at http://docs.sun.com.
Some localized documentation collections in PDF format have package names that are longer than nine characters. To install these PDF collections on servers that are running the Solaris 7 or 8 operating environment, you must first install two patches.
No patches exist at the time of this release for Solaris 2.6 servers.
Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on the documentation media, Solaris 9 9/02 Documentation CD 1 of 2, 2 of 2, or DVD. This file is located in the following directory:
mount-point/README/locale/install_locale.html |
For example, the English file on the Solaris 9 9/02 Documentation CD 1 of 2 is located in the following directory:
sol_9_doc_1of2/README/C/install_C.html |
If you run the Solaris 9 9/02 Documentation CD uninstaller in Uninstall All mode, the uninstaller removes only those documentation packages that are installed by default.
Workaround: Run the uninstaller in Uninstall Partial mode. Select the specific packages you want to uninstall.
If you use the Solaris 9 9/02 Installation CD with certain locales, the installation program does not prompt you to install packages from the Solaris 9 9/02 Documentation 2 of 2 CD. This problem occurs for the following locales.
ja_JP.PCK
ja_JP.UTF-8
ko.UTF-8
zh.GBK
zh.UTF-8
zh_CN.18030
zh_HK.BIG5HK
zh_HK.UTF-8
zh_TW.BIG5
zh_TW.UTF-8
Workaround: Choose one of the following workarounds.
Select one of the EUC locales (ja, ko, zh or zh_TW) as the default installation locale when you install the Solaris 9 9/02 software.
Run the installer utility directly from the Solaris 9 9/02 Documentation 2 of 2 CD.
If you use the Solaris 9 9/02 Documentation CD installer program with the nodisplay option, the verify panel might not page correctly.
Workaround: Do not specify the nodisplay option with the Solaris 9 9/02 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 9/02 Documentation CD.
When you select a locale for your installation, additional related locales might also be installed. This change in behavior occurs in the Solaris 9 9/02 operating environment because all full locales, with message translations, and the Asian and Japanese partial locales, locale enabler, have been repackaged based on language support for locales. Other partial locales are still packaged and installed based on geographic region, such as Central Europe.
If you upgrade to the Solaris 9 9/02 operating environment on a system running the Solaris 9 Beta Refresh operating environment with Simplified Chinese or Traditional Chinese locale support, the upgrade does not complete successfully. The Simplified Chinese and Traditional Chinese CDE font localization packages (SUNWcdft or SUNWhdft) do not upgrade to the appropriate Solaris 9 9/02 packages. The following error message is displayed.
Removing package SUNWcdft: /a/var/sadm/pkg/SUNWcdft/install/postremove: /a/usr/dt/config/xfonts/zh_CN.EUC: does not exist /a/var/sadm/pkg/SUNWcdft/install/postremove: /a/usr/dt/config/xfonts/zh_CN.GBK: does not exist /a/var/sadm/pkg/SUNWcdft/install/postremove: /a/usr/dt/config/xfonts/zh_CN.UTF-8: does not exist pkgrm: ERROR: postremove script did not complete successfully |
Workaround: Before you upgrade to the Solaris 9 9/02 operating environment, remove the appropriate Solaris 9 Beta Refresh postremove files.
# rm /var/sadm/pkg/SUNWcdft/install/postremove # rm /var/sadm/pkg/SUNWhdft/install/postremove |
If you upgrade to the Solaris 9 9/02 operating environment on a system running the Solaris 8 operating environment with the Solaris 8 Language Supplement CD installed, several invalid Thai, Russian, Polish, and Catalan locale packages remain on the system. These locale packages have an ARCH=sparcall value, and are not removed during the upgrade to the Solaris 9 9/02 operating environment.
Workaround: Before you upgrade to the Solaris 9 9/02 operating environment, use the Solaris Product Registry application to remove the Solaris 8 Languages Supplement CD packages.
If you install one or more of a specific set of European locales, the system might not display any characters outside of the English or European character set in the UTF-8 codeset of the locale. This problem occurs under the following conditions.
You install one or more of the following locales.
Middle East/Israel (ISO8859-8)
Northern Africa/Egypt (ISO8859-6)
Eastern Europe/Russia (ISO8859-5)
Eastern Europe/Turkey (ISO8859-9)
South America/Brazil (ISO8859-1)
Central Europe/Poland (ISO8859-2)
You install no other locales on the system.
Workaround: Choose one of the following workarounds.
During the installation, install both the en_US.UTF-8 North America/U.S.A. locale and the European locale that you want on the system.
After the installation is completed, use the pkgadd command to add the following packages to your system.
SUNW5ttf - Traditional Chinese BIG5 True Type Fonts Package
SUNWcttf - Simplified Chinese (EUC) True Type Fonts
SUNWiiimr - Internet/Intranet Input Method Framework Package (Root)
SUNWiiimu - Internet/Intranet Input Method Framework Package (Usr)
SUNWinleu - Indic Locale Environment User Files
SUNWinlex - Indic Language Environment user files (64-bit)
SUNWinttf - Indic True Type Fonts
SUNWjxcft - Japanese Required TrueType Font
SUNWkttf - Korean True Type Fonts
SUNWtleu - Thai Locale Environment User Files
SUNWtleux - Thai Language Environment user files (64-bit)
These packages are available from the Solaris_9/Product directory on the Solaris 9 9/02 Software 1 of 2 CD or CD image.
For example, if you install the Solaris 9 9/02 operating environment from the Solaris 9 9/02 Software 1 of 2 CD, type the following commands.
# cd /cdrom/cdrom0/Solaris_9/Product # pkgadd -d . SUNW5ttf # pkgadd -d . SUNWcttf |
Repeat the pkgadd command for each package in the previous list.