Two ways a pkg can be installed in the global zone only.
a) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=true
b) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=false
# pkgadd was run with -G
Trolling though the installed pkginfo files will give you (a), but
not (b).
Jeff Cheeney wrote:
Maybe someone on the install or zones discussion lists can help answer
this question.
Giovanni Schmid wrote:
I have read different articles/docs/posts about solaris zones and
liveupgrade issues until now; however, I have some doubts about the right
way to deploy
Giovanni Schmid wrote:
Ethan,
my zonepaths aren't on that zfs.
Have you confidence (or evidence) that in such scenario a simple BE
duplication as provided by
# lucreate -c bootenv1 -m /:c2d0s0:ufs -n bootenv2
will be sufficient ? That is, will Z2 in bootenv2 see
/zfspool/users/home ?
Hey Jerry,
I just thought about something regarding the zones dataset
namespace. Instead of creating the dataset for zone roots at:
rpool/export/zones/z1/rpool/ZBE1
Maybe we should insert the roped off ROOT container dataset
like we do in the global zone:
Mike Gerdts wrote:
On Tue, Aug 26, 2008 at 5:07 PM, Ethan Quach [EMAIL PROTECTED] wrote:
Hey Jerry,
I just thought about something regarding the zones dataset
namespace. Instead of creating the dataset for zone roots at:
rpool/export/zones/z1/rpool/ZBE1
Maybe we should
Jerry Jelinek wrote:
Evan Layton wrote:
This is the same as what is done with /rpool/ROOT and ZFS boot, with
ROOT being the confined area where we place BE's. An admin can still
create things there but this is the only place that we look for BE's.
Datasets outside this are not considered
Jerry Jelinek wrote:
Ethan Quach wrote:
Ethan Quach wrote:
Jerry Jelinek wrote:
Evan Layton wrote:
This is the same as what is done with /rpool/ROOT and ZFS boot, with
ROOT being the confined area where we place BE's. An admin can
still
create things there but this is the only
Comments, mostly on libbe ...
General comment - Since we don't yet support boot environments
within a zone, beadm should fail gracefully when run in a zone, like:
# beadm subcommand
beadm is not supported in a zone.
rather then trying to do something and failing miserably. Most of
Tim,
Thanks for the review. All comments taken as is unless noted below...
thanks,
-ethan
Tim Knitter wrote:
be_mount.c:
53: Why not add this struct to libbe_priv.h where the other structs live?
Because its only used privately in be_mount.c, not anywhere else.
Nit:
294, 2208: The
Joe, Jean, Jerry,
Thanks for providing your comments. We've built an incremental webrev
with just the changes from your comments. This webrev also includes a
couple of dev bugfixes that went in during the code review process -
3776, 3772
Any further comments are welcomed.
Joe,
Thanks. We'll make that correction.
-ethan
Joseph J VLcek wrote:
Ethan Quach wrote:
Joe, Jean, Jerry,
Thanks for providing your comments. We've built an incremental webrev
with just the changes from your comments. This webrev also includes a
couple of dev bugfixes that went
v wrote:
SunOS Release 5.11 Version snv_111b 32-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: zone1
Reading ZFS config: done.
Mounting ZFS filesystems: (6/6)
root_password=fto/dU8MKwQR
Is this encrypted string missing a
v wrote:
I don't think so... It looks like it works:
http://blogs.sun.com/observatory/en_US/entry/zones_and_crossbow1
I would validate with that blogger if that sysidcfg had actually
been validated. If you look a little lower in the blog, the sysidcfg
file failed to get get consumed by
13 matches
Mail list logo
