Hi Eric,
Eric Schrock wrote:
...
Second, it forced the CLI to distinguish between a container and a
filesystem. At first this was accomplished with a trailing slash on the
name, and later introducing the 'ctr' type. Both were confusing to
users for different reasons.
Speaking of
On Thu, Aug 10, 2006 at 10:23:20AM -0700, Eric Schrock wrote:
A new option will be added, 'canmount', which specifies whether the
given filesystem can be mounted with 'zfs mount'. This is a boolean
property, and is not inherited.
Cool, looks good. Do you plan to implement this using the
Yet another reason it was removed. This proposal specifically does not
use the word 'container', nor will the documentation refer to it as
such. I was merely providing background (possibly too much) for why
this option was originally implemented and then removed.
- Eric
On Thu, Aug 10, 2006 at
Right now I'm using the generic property mechanism, but have a special
case in dsl_prop_get_all() to ignore searching parents for this
particular property. I'm not thrilled about it, but I only see two
other options:
1. Do not use the generic infrastructure. This requires much more
invasive
On Thu, Aug 10, 2006 at 10:44:46AM -0700, Eric Schrock wrote:
Right now I'm using the generic property mechanism, but have a special
case in dsl_prop_get_all() to ignore searching parents for this
particular property. I'm not thrilled about it, but I only see two
other options:
1. Do not
Eric Schrock wrote:
Also, I am working on 6367103, which would allow for this option (and
any others) to be set at create time, so you don't have the weird
situation where the filesystem is temporarily mounted.
I'm assuming since you don't use that syntax in your examples that
there will be a
On Fri, Aug 11, 2006 at 01:50:05AM +0100, Darren J Moffat wrote:
I'm assuming since you don't use that syntax in your examples that
there will be a separate proposal/ARC case for the set at create time.
Yes. I have a prototype almost done and will send out a similar
proposal, probably
