lianep at eng.sun.com wrote: > 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. >
Correct. > 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.) > The split is actually an artifact of the ancient diskless architecture. One of the problems of zones is that because it allows for arbitrary inheritance of directories, rather than on the traditional package boundaries, it makes for many subtle problems in packaging. And people wonder why upgrade with zones is hard... Dave
