Setting Package Parameters for Zones
The SUNW_PKG_ALLZONES, SUNW_PKG_HOLLOW,
and SUNW_PKG_THISZONE package parameters define the characteristics
of packages on a system with zones installed. These parameters must be set
so that packages can be administered on a system with non-global zones installed.
The following table lists the four valid combinations for setting package
parameters. If you choose setting combinations that are not listed in the
following table, those settings are invalid and the package will fail to install.
Ensure that you have set all three package parameters. You can leave
all three package parameters blank. The package tools interpret a missing
zone package parameter as if the setting were false, but
not setting the parameters is strongly discouraged. By setting all three
package parameters, you specify the exact behavior the package tools should
exhibit when installing or removing the package.
Table 24–1 Valid Package Parameter
Settings
SUNW_PKG_ALLZONES Setting
|
SUNW_PKG_HOLLOW Setting
|
SUNW_PKG_THISZONE Setting
|
Package Description
|
false
|
false
|
false
|
This is the default setting for packages that do not specify values
for all the zone package parameters.
A package with these settings can be installed in either the global
zone or a non-global zone.
-
If the pkgadd command is run in the global
zone, the package is installed in the global zone and in all non-global zones.
-
If the pkgadd command is run in a non-global
zone, the package is installed in the non-global zone only.
In both cases, the entire contents of the package is visible in all
zones where the package is installed.
|
false
|
false
|
true
|
A package with these settings can be installed in either the global
zone or a non-global zone. If new non-global zones are created after the
installation, the package is not propagated to these new non-global zones.
-
If the pkgadd command is run in the global
zone, the package is installed in the global zone only.
-
If the pkgadd command is run in a non-global
zone, the package is installed in the non-global zone only.
In both cases, the entire contents of the package is visible in the
zone where the package is installed.
|
true
|
false
|
false
|
A package with these settings can be installed in the global zone only.
When the pkgadd command is run, the package is installed
in the global zone and in all non-global zones. The entire contents of the
package is visible in all zones.
Note –
Any attempt to install the package in a non-global zone fails.
|
true
|
true
|
false
|
A package with these settings can only be installed in the global zone,
by the global administrator. When the pkgadd command is
run, the contents of the package is fully installed in the global zone. If
a package has the package parameters set to these values, the package content
itself is not delivered on any non-global zone. Only the package installation
information necessary to make the package appear to be installed is installed
on all non-global zones. This enables the installation of other packages to
be installed that depend on this package.
For package dependency checking purposes, the package appears to be
installed in all zones.
-
In the global zone, the entire contents of the package is
visible.
-
In whole root non-global zones, the entire contents of the
package is not visible.
-
When a non-global zone inherits a file system from the global
zone, a package installed in this file system is visible in a non-global
zone. All other files delivered by the package are not visible within the
non-global zone.
For example, a native sparse root non-global zone shares
certain directories with the global zone. These directories are read-only.
Sparse root non-global zones share the /platform file
system among others. Another example is packages that deliver files relevant
only to booting hardware.
Note –
Any attempt to install the package in a non-global zone fails.
|