Sun Microsystems SOLARIS 10 User Manual

Page 44

Advertising
background image

Version 3.1-en

Solaris 10 Container Guide - 3.1 4. Best Practices

Effective: 30/11/2009

4.1.5.3. Software installation by the global zone – usage in the global zone

•

non-pkg software

−

Software A is installed by the global zone e.g. in /software/A

−

/software/A is available to the global zone as a writable directory.

−

Configuration and data of software A can be modified by the global zone since this part
is available and writable exclusively by this zone.

•

pkg software

−

Software P is installed in the global zone with pkgadd -G.

−

In the global zone, an entry is made in the pkg database.

−

The software can be used in the global zone only.

−

The configuration and the data of the software can be modified from the global zone.

4.1.5.4. Installation by the local zone – usage in the local zone

•

non-pkg software

−

/software/A is available to the zone as a writable directory.

−

Software A is installed by the zone e.g. in /opt/software/A.

−

The configuration and the data of software A can be modified by the zone since this part
is available and writable exclusively by this zone.

•

pkg software

−

Software P is installed by the zone with pkgadd -G.

−

The installation and configuration directory of the package must be available and writable
by the zone. If this is not the case, e.g. with /usr/local (if /usr is an inherit-pkg-
dir
for a sparse-root zone), a soft link /usr/local --> ../../opt/local, for example, can be
set up in the global zone. This points with /opt/local into a writable part of the local zone.

−

An entry in the pkg database is made for the zone.

−

The software can only be used in this zone.

−

The configuration and the data of the software can be modified by the zone.

37

Advertising