My fault entirely; it is well documented here:
http://docs.sun.com/app/docs/doc/819-2450/zones.intro-1?l=ena=view
kido
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Hi guys,
This is my version of Opensolaris:
Sun Microsystems Inc. SunOS 5.11 snv_111bNovember 2008
I have installed 2 zones on it:
k...@opensolaris:~$ zoneadm list -cv
ID NAME STATUS PATH BRANDIP
0 global running/
On Sat, Jul 3, 2010 at 6:36 AM, Daniel Dinu daniel.d...@gmail.com wrote:
Hi guys,
This is my version of Opensolaris:
Sun Microsystems Inc. SunOS 5.11 snv_111b November 2008
I have installed 2 zones on it:
k...@opensolaris:~$ zoneadm list -cv
ID NAME STATUS
On Sat, 03 Jul 2010 13:36:51 +0200, Daniel Dinu daniel.d...@gmail.com wrote:
zone1 is installed in /vol1/zone1 and zone2 in /vol1/zone2.
zone1 was configured as a sparse root zone (I used create command).
zone2 was configured as a whole root zone (I used create -b command).
Still, the space
Thank you so much for your answer!
So, when I thought that I cannot install a whole root zone, in fact I had 2
already installed...that's funny :)
I have to admit that I checked the files in /etc/zones and I was a little bit
surprised by their (lack of) content regarding inherited dirs, but I
On Sat, Jul 3, 2010 at 7:35 AM, Daniel Dinu daniel.d...@gmail.com wrote:
Thank you so much for your answer!
So, when I thought that I cannot install a whole root zone, in fact I had 2
already installed...that's funny :)
I have to admit that I checked the files in /etc/zones and I was a
Mike, Frank , thank you both for your quick and accurate response!
kido
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
