Using the FAQ's example, you must create the /usr/local file system in the global zone's /usr.

My own convention of individual zones' personal /usr/local is to use the method described in the FAQ (thanks Jeff), and put the 'special' directory in the zone's zonepath.


zonecfg:twilight> add fs
zonecfg:twilight:fs> set dir=/usr/local
zonecfg:twilight:fs> set special=<zonepath>/usr-local
zonecfg:twilight:fs> set type=lofs
zonecfg:twilight:fs> end

In those cases where I have to share a /usr/local between several zones, I put it elsewhere, and make sure *at most one* has write privileges, to prevent zones from stomping over each other's changes. (this is not good if the applications like to use /usr/local/etc or similar for run-time configuration setups.)

zonecfg:twilight> add fs
zonecfg:twilight:fs> set dir=/usr/local
zonecfg:twilight:fs> set special=<someotherpath>/usr-local
zonecfg:twilight:fs> set type=lofs
zonecfg:twilight:fs> add options ro
zonecfg:twilight:fs> end

Steffen


Jeff Victor wrote On 05/03/07 13:22,:
DJR wrote:

I installed my zones, in a sparse zone format.

question is, is there a way to NOT use /usr/local from the global zone and use a local copy or start with a clean /usr/local on the zone besides in a
whole root format where it copies the global over to the zone. I do not
want to rebuild the zone if possible, is there any way around this.


Yes, this is addressed in the FAQ: http://opensolaris.org/os/community/zones/faq/#cfg_io_usrlocal


--------------------------------------------------------------------------
Jeff VICTOR              Sun Microsystems            jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ:    http://www.opensolaris.org/os/community/zones/faq
--------------------------------------------------------------------------
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to