After upgrading a server with diskless clients of more than one SPARC kernel architecture, such as a sun4u server with diskless sun4c, sun4d, and sun4m clients, the SUNWkvm packages for clients whose kernel architectures differ from that of the server cannot be patched.
Workaround: Add all of the SUNWkvm packages before applying any patches that affect them:
# pkgadd -d SUNWkvm.*
The upgrade program can exaggerate by as much as 30 percent the amount of space required for upgrades to systems with the Solaris software. Therefore, it prevents many systems from being upgraded without deselecting packages or finding more space.
Workaround: You can manually reallocate disk space among file systems or use the Software Customization menu to remove software packages that are not needed.
The Solstice AutoClients display the following message when rebooting:
fsck -F cachefs: Cache directory /.cache/rootcache does not exist.mount -F cachefs: cache fsck mount failedfsck -F cachefs: Cache directory /.cache/rootcache does not exist.mount -F cachefs: cache fsck mount failed
This directive indicates to the kernel that the root file system is of type cachefs. To determine whether or not a specific Solstice AutoClient can be affected by this problem before you attempt an upgrade, examine the directory /export/root/client-name/var/sadm/pkg on the server (this is the Solstice AutoClient's /var/sadm/pkg directory). If this directory contains a subdirectory called TADcar, the Solstice AutoClients may be affected.
Workaround: Edit the /etc/system file for the Solstice AutoClients after the upgrade by appending the following line:
The Solstice AutoClients' /etc/system file is stored on the server as /etc/root/client-name/etc/system.
Patches located in the Patches directory on the Solaris 7 5/99 CD are not automatically applied to clients whenever a server is upgraded.
Workaround: Apply the patches located in the Patches directory to clients after the upgrade has been completed.