Anon Y Mous wrote:
> Also, another important caveat / missing piece that I noticed is missing
> from all of the OpenSolaris Indiana Sun blogs and documentation I've
> looked at so far: to do resource caps on CPU and RAM memory in OpenSolaris
> I think you need to install the SUNWrcap package first
Also, another important caveat / missing piece that I noticed is missing from
all of the OpenSolaris Indiana Sun blogs and documentation I've looked at so
far: to do resource caps on CPU and RAM memory in OpenSolaris I think you need
to install the SUNWrcap package first like this:
# pkg instal
These links might help to add a little bit more to the explanation (this is my
collection of all time favorite OpenSolaris zones related links here):
http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008
http://blogs.sun.com/jerrysblog/entry/zones_on_opensolaris_2008_11
http
On Sat, Feb 06, 2010 at 10:30:18AM +0100, dick hoogendijk wrote:
> Going from OpenSolaris b131 to b132..
> Am I correct in this procedure:
> [1] pkg image-update (with zones attached)
> [2] after reboot to the new BE detach the zones
> [3] zoneadm attach -u zones
>
> OR, do I have to detach -BEFORE
On Sat, 06 Feb 2010 10:30:18 +0100, dick hoogendijk wrote:
> Going from OpenSolaris b131 to b132..
> Am I correct in this procedure:
> [1] pkg image-update (with zones attached)
> [2] after reboot to the new BE detach the zones
> [3] zoneadm attach -u zones
precisely
> OR, do I have to detach -
Going from OpenSolaris b131 to b132..
Am I correct in this procedure:
[1] pkg image-update (with zones attached)
[2] after reboot to the new BE detach the zones
[3] zoneadm attach -u zones
OR, do I have to detach -BEFORE- the pkg image -update?
___
zone
