Darren J Moffat writes: > lianep at eng.sun.com wrote: > > This doesn't work for the zones model. /usr/lib is (by default) shared > > between all zones, and services need to have a location where they may not > > be. > > I don't see where the problem is with zones so I must be missing > something. Here's my thinking: > > We don't support different versions of the same Solaris WOS package in > different zones. > > Zones can't have a different set of packages installed from the global > zone either.
Where'd you get this information? All the zones docs say you can use pkgadd in a local zone. If I'm confused about this, the docs are too. :) > > The files aren't editable anyway so the admin can't arrange for the > contents of the Solaris manifests to be different between zones. > > Given that the files in /var/svc/manifest are always the same for all > zones, right ? So what am I missing ? That's what you're missing. You could pkgadd, say, sendmail into just one local zone. It delivers a manifest. It needs to put the manifest in a location that's per-zone by default. Zones design, I think, sticks us with a problem of having to split packages. (Or, put another way, the packaging tools do -- split root and usr packages are an artifact of package/install implementation, not necessarily the way things needed to be done.) > > > I've been cooking up a plan in conjunction with the profiles project to > > move the default manifest and profiles location to /etc. It needs a little > > refinement first as some details are tricky, but I'll post it here, probabl > y > > mid-July, for comment. > > Whats the rationale for the move from /var/svc to somewhere under /etc ? > What problem is that solving ? I know it doesn't change my situation > since /var and /etc are both root filesystem package locations. Early boot services, and we can manifest-import *much* earlier and get rid of a lot of grungy scenarios. You're right that it doesn't solve your request. You also said: > My request was ONLY for the Solaris WOS provided manifests not ones from > unbundled products or ones written locally; those would still live in > /var/svc/manifest (or in /etc/ somewhere depending on Liane's proposal). Plenty of WOS provided manifests couldn't do this based on the zones requirement to allow installation in a shared-/usr local zone. Are you sure your service could? liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
