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 /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 zon
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
>
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 on
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:
> 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
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 consi
Can a non-global zone utilize all the available memory on the system if
resource management is not used and rcap is not used?
Thanks,
Patrick
___
zones-discuss mailing list
zones-discuss@opensolaris.org
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 con
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 but would be sha
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/
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 ins
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 "roped off" ROOT container dataset
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 zo
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
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 cannot be changed
> on d
15 matches
Mail list logo
