On Jul 18, 2007, at 11:16 AM, Jeffrey Altman wrote:
Except that the new volume should be "special" in that no changes are
permitted. In other words, the "wida" permissions are neutered on
this
volume. Since the new volume type doesn't exist, modifying the
ACLs is
something that has the same effect that you can do today.
Exactly. I'd not thought of the acls issues, but yes, they should be
invariant if possible.
I suppose this brings up some other issues as well. For example,
would we want a -readonly flag for 'vos copy' so one could make an
invariant copy of an existing volume? I can see some use for that.
And I suppose we'd want 'vos convertROtoRW' to work as well.
Since '.readonly' has such a strong association with replicant
volumes, perhaps we should refer to this new type as an invariant
volume. The different terminology will prevent a lot of confusion.
Steve
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
