Never mind. I will not do this rename. It's not worth the trouble.
r...@vps1:~# zoneadm -z note move /zones/note
Moving across file systems; copying zonepath /zones/bugs...sh[1]: cd:
/zones/bugs: [No such file or directory]
zoneadm: zone 'note': 'copy' failed with exit code 1.
The copy failed.
I am trying to rename a zonename (and zonepath) to a new zone. But I get this
error:
# zfs rename zones/bugs zones/note
cannot rename 'zones/bugs': child dataset with inherited mountpoint is used in
a non-global zone
#
I tried this with the zone in detached mode. Any tips?
Thanks
--
This
It seems to be -U, looking at the source at least:
http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zoneadm/zoneadm.c#attach_func
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Once a the global zone is upgraded (and rebooted with the new BE), what is the
best way to update the zones?
It seems like all I would need to do is:
pkg -R zone path/root image-update
reboot zone
This seems like a hack, how would post package processing happen if this is
not done from the
Ah, thanks. I knew that was available on Solaris but not in OpenSolaris. The
man page had no reference to the -u option (I take it you meant -u and not -U).
I will try that out later.
--
This message posted from opensolaris.org
___
zones-discuss
I've been playing around with how zones are integrated in a system running a
/support (default publisher) version of OpenSolaris 2009.06. It seems when a
new zone is installed, the SSL keys are also copied over to the zone (at least
that's what the zone install messages seem to show - sorry
over at
#nexenta (http://www.nexenta.org/chat) and look for rootard/anilg
Cheers,
Anil
___
zones-discuss mailing list
zones-discuss@opensolaris.org
On Fri, Nov 28, 2008 at 9:48 AM, Boyd Adamson [EMAIL PROTECTED] wrote:
Anil Gulecha [EMAIL PROTECTED] writes:
Hi,
I'm trying to create a zone from a base zone using the zoneadm clone
feature (This is on b103). However, zoneadm seems to be using copy
instead of cloning via zfs snapshot. Why