Darren J Moffat wrote:
Jerry Jelinek wrote:
Currently, with user defined properties, the values can be changed
inside the zone. The proposal actually depends on this feature.
It sounds like you might need to talk to the zfs team about some
enhancements here so we can have properties that
Ethan Quach 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 insert the roped off ROOT container dataset
like we do in the global zone:
Jerry Jelinek wrote:
Ethan,
Ethan Quach wrote:
Jerry Jelinek wrote:
Ethan Quach 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 insert the
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:
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 BE's
On Wed, Aug 27, 2008 at 1:20 PM, Patrick Ho [EMAIL PROTECTED] wrote:
Can a non-global zone utilize all the available memory on the system if
resource management is not used and rcap is not used?
A non-global zone could use up most of the free physical memory on the
system. If that happened,
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 place that we look for
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
On Wed, Aug 27, 2008 at 4:31 PM, Ethan Quach [EMAIL PROTECTED] wrote:
Jerry,
If its not for general purpose, then yes, I agree zonepath/ROOT is
more clear. ?(And I also agree about the rpool name)
Regarding a general purpose dataset, IMO we need to always automatically
give this branded
