Software Installation Per Mount - Sun Microsystems SOLARIS 10 Manual

Version 3.1-en
Solaris 10 Container Guide - 3.1 5. Cookbooks
Alternatively, set the boot arguments permanently in a zone configuration:
global# zonecfg -z keetonga
zonecfg:keetonga> info bootargs
bootargs:
zonecfg:keetonga> set bootargs="-m verbose"
zonecfg:keetonga> info bootargs
bootargs: -m verbose
zonecfg:keetonga> commit
zonecfg:keetonga> exit
global# zoneadm -z keetonga halt
bash-3.00# zlogin -C keetonga
[Connected to zone 'keetonga' console]
[NOTICE: Zone booting up]
SunOS Release 5.10 Version Generic_137138-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc.
Use is subject to license terms.
[ system/filesystem/root:default starting (root file system mount) ]
[ network/loopback:default starting (loopback network interface) ]
[ network/pfil:default starting (packet filter) ]
[ system/installupdates:default starting (system update installer) ]
[ system/boot-archive:default starting (check boot archive content) ]
[ milestone/name-services:default starting (name services milestone) ]
... deleted outputs ...
[ network/inetd:default starting (inetd) ]
[ system/system-log:default starting (system log) ]
[ system/console-login:default starting (Console login) ]
keetonga console login:

5.3.3. Software installation per mount

[ug] In order to allow an application to run in the zone, additionally installed software is required,
except in trivial cases (Apache, Perl, etc.) This software is very often not in Sun pkg format.
One method of distributing this software is to maintain a shared software repository in the global zone
and to make it completely or partially visible in the zones:
Globally, there is the directory / s o f t w a re
Software is installed in the directory / s o ftw a re /p r od uc t /v er s io n/ e.g.:
/s oft w a r e / o r a c l e / 9 i _ 0 5 /
/s oft w a r e / o r a c l e / 9 i _ 0 6 /
/s oft w a r e / o r a c l e / 1 0 g _ 0 1 /
/s oft w a r e / s i e b e l / 3 . 1 4 /
/s oft w a r e / t o m c a t / 3 . 7 /
With zo ne c f g : a d d f s, the required directories in the respective zones are made visible
as read-only (with lofs).
This ensures that even software usage can be tracked in order to monitor licensing fees if necessary.
It is easier to install the entire directory / s o f tw ar e in each zone. Different ways will then need to
be used to monitor software usage (audit and d t ra ce ).
Effective: 30/11/2009
All rights reserved.
96