Filter
Top Products
40
Limitations and known bugs No
Recommended actions
Remarks
I Installation and removal of a package or patch may fail in a system with non-global
zones, under the following conditions.
z non-global zone is configured using zonecfg(1M), but not installed by
zoneadm(1M).
z non-global zone is just booted by zoneadm(1M) after installation, without any
non-global zone settings such as host name and root password.
z non-global zone is being installed or removed by zoneadm(1M).
44
Make sure the initial setup like hostname and password configuration of all non-global
zones has been done and all the non-global zones are in “running” state before
installation or removal of package and patch
The following message may be displayed during an upgrade installation from Solaris 9.
network/nfs/server:default failed repeatedly (see 'svcs -x' for details)
45
Ignore the message. It has no impact on the system.
5.2 Specification and incompatibility for Solaris
This chapter explains specification and incompatibility for Solaris.
Table 5.2 Specification and incompatibility for Solaris
Specification and incompatibility
No
Recommended actions
Remarks
Solaris 10 provides Solaris Service Manager (SMF) to enhance the UNIX startup script
(so called RC script) and system daemons during boot up. Due to this new feature, there
is some unexpected and incompatible behavior compared to Solaris 9 or older versions.
1
Refer to SMF documentation as follows and smf(5) manual page.
Solaris 10 System Administrator Collection
>> System Administration Guide: Basic Administration
http://docs.sun.com/app/docs/doc/817-1985/
/usr/bin/ln has been changed in Solaris 10.
z Solaris 9 or older versions.
/usr/bin/ln will overwrite file if target file already exists.
z Solaris 10.
/usr/bin/ln will fail if target file already exists.
2
The same behavior occurs with Solaris 9 or older versions if the -f option is used with
the ln command.
If the DHCP sever has multiple network interfaces, it may not be able to deliver an IP
address to a DHCP client because of DHCP server settings.
3
pntadm(1M) -s option needs to be specified with "uname -n" or the IP address of the
primary network interface. If a non-primary IP address is specified with pntadm -s,
DHCP server will not be able to deliver an IP address to the DHCP client.