[OpenAFS-devel] Suggestions for features/ideas...

[Neulinger, Nathan]

Yeah, but the user can still get to the data simply by mounting the
readwrite volume.

Granted, that's not likely to occur, but I hate to design around obscurity. 

I can see other applications - marking volumes read-only so as to give you
an extra layer of protection against accidents. 

-- Nathan

> -----Original Message-----
> From: Phil.Moore@morganstanley.com 
> [mailto:Phil.Moore@morganstanley.com]
> Sent: Thursday, May 24, 2001 9:19 AM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] Suggestions for features/ideas...
> 
> 
> >>>>> "Nathan" == Nathan Neulinger <Neulinger> writes:
> 
> Nathan> Ability to flag a volume as read-only - even though it's
> Nathan> actually a read-write volume. I'd like to be able to mount a
> Nathan> volume (likely restore vol) so the user can get to all the
> Nathan> data within it, maintaining the acl's as is, but make it so
> Nathan> that user cannot make any changes to it.
> 
> You can do this today.  Restore the volume from tape, run vos backup,
> and then mount the backup volume.  
> 
> I can't comment on the feasibility of the other two ideas....
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>