Re: [zones-discuss] renaming zonepath
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. More information can be found in /var/log/zoneAAA2XaapU Cleaning up zonepath /zones/note...The ZFS file system for this zone has been destroyed. I believe the zones are not mounted when the zone is not running so the cp fails. Luckily it did not delete the data *phew*. Thanks! -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] renaming zonepath
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 message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
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
[zones-discuss] preferred way to image-update zones
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 zone itself? Should I instead *from the zone* take a clone, update parentbe zfs option, set it to active. Then, imate-update the snapshot/clone? This seems like a hack too! -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
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 mailing list zones-discuss@opensolaris.org
[zones-discuss] zones issues with SSL publisher (to get Sun support or not)
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 didn't get a chance to actual verify what keys are copied over etc...). This is a bad thing, if we are providing the zone to a user/customer who does not have root access to the global zone. They would have access to the keys, free to distribute and use. What is a solution to this? If I set the default publisher of the global zone to be /release right before installing zone, then the zone and the global zone bits are different. But this does prevent the keys from being copied. Once installed, I could set it back to /support. All of that sounds a bit of a hack and would rather not do that in the hopes of keeping the zones and the global zone in sync with the same bits. But then how can I get Sun support (patches) and also prevent this problem? If there is no good solution at this point, I guess I will just have to stick with /release for now. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Devzones
Hi, A quick google revealed that devzones never came up on this list, so I thought I'd do an introductions. Devzone is built on Zones, and allows one to define a base_zone and then easily make copies of it as and when required via simple commands. Users do not need to have superuser priviledges, and their interface is a very simple set of commands (devzone_create, devzone_enter and devzone_free) I published an article on OSnews going into more detail.. http://osnews.com/story/20653/Devzones_Simple_Use-and-throw_Developer_Environments Devzones has been built and used on Nexenta, but is written in a opensolaris-distro-agnostic manner. More information on the sourceforge page http;//devzone.sf.net Its primarily been developed by rootard with a few contributions by myself.. the project isn't big enough to warrant it's own chatroom/mailing list yet, so if you have any questions, pop over at #nexenta (http://www.nexenta.org/chat) and look for rootard/anilg Cheers, Anil ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zones clone vs copy issue
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 would it do that? My experience has been that the zfs clone thing is only done if the direct parent of the zonepath (in your case, /zones) is a zfs filesystem Thanks.. this was fixed yesterday.. by recreating zones from a new pool. #cat /var/log/zoneAAAsIaaVn /usr/bin/cpio: invalid option -- P Try `cpio --help' or `cpio --usage' for more information. That error looks like it's coming from gnu cpio. I don't think that should be in /usr/bin/. Have you overwritten the OS-supplied one? This too, this is on Nexenta.. forgot to add SUN_PERSONALITY=1. That fixed it. Regards Anil ___ zones-discuss mailing list zones-discuss@opensolaris.org
