On 7/20/06, James Dickens <[EMAIL PROTECTED]> wrote:
On 7/20/06, James Carlson <[EMAIL PROTECTED]> wrote:
> James Dickens writes:
> > The interface would be
> >
> >
> > #zoneadm –z zonename lock
> >
> > With the zone locked no changes in the global zone effects the
> > non-global zones.
>
> I'd s
* James Dickens <[EMAIL PROTECTED]> [2006-07-20 10:19]:
> On 7/20/06, James Carlson <[EMAIL PROTECTED]> wrote:
> >What happens when the lock is disabled? If I add another package to
> >the global zone that depends on things that were added while the lock
> >was enabled, does that work? Do I get a
On 7/20/06, James Carlson <[EMAIL PROTECTED]> wrote:
James Dickens writes:
> The interface would be
>
>
> #zoneadm –z zonename lock
>
> With the zone locked no changes in the global zone effects the
> non-global zones.
I'd suggest using a less general term ("pkg-lock", maybe?) and
consider using
James Carlson wrote:
Jeff Victor writes:
should be added to pkgadd, e.g. "pkgadd -Z twilight" would install the pkg in all
zones except zone 'twilight'. (There is probably a better option-letter.)
I think that may still end up walking into some interesting support
issues. In fact, I don't q
Jeff Victor writes:
> should be added to pkgadd, e.g. "pkgadd -Z twilight" would install the pkg in
> all
> zones except zone 'twilight'. (There is probably a better option-letter.)
I think that may still end up walking into some interesting support
issues. In fact, I don't quite see how it's
We might be able to achieve the general goal without creating problems mentioned
by James if the model is slightly different.
Currently Solaris has:
* Install a pkg in all zones (pkgadd)
* Install a pkg in the GZ only (pkgadd -G)
* Install a pkg in a non-GZ only (pkgadd -G)
Note that pkgadd wil
James Dickens writes:
> The interface would be
>
>
> #zoneadm ?z zonename lock
>
> With the zone locked no changes in the global zone effects the
> non-global zones.
I'd suggest using a less general term ("pkg-lock", maybe?) and
consider using zonecfg instead.
So what happens with the default
On 7/20/06, Amol A Chiplunkar <[EMAIL PROTECTED]> wrote:
Interesting !
If you propose to lock all the non global zones and do a pkgadd,
how different is it from pkgadd -G ?
because it effects all packages, -G is not possible if you are using
an installer like in JES or blastwave, or any other
Interesting !
If you propose to lock all the non global zones and do a pkgadd,
how different is it from pkgadd -G ?
For that matter, pkgadd -G is not just for global, but for any
zone. It gives you same kind of result without having to lock zones.
It installs package only in the zone where pkga
Currently if you create a zone, and install another package in the
global zone, it is installed in the non-global zones. I propose a
feature that you can lock each non-global zone then the new packages
would not be installed in the non-global zones. Of course this only
effects packages that are in
10 matches
Mail list logo
