[jcifs] setReadOnly, setReadWrite, or setAttributes?
Christopher R. Hertel
crh at ubiqx.mn.org
Thu Oct 30 03:52:47 EST 2003
On Wed, Oct 29, 2003 at 01:30:40AM -0500, Michael B Allen wrote:
> >> > filesystem offers a completely different set of attributes, extended
> >> > attributes, ACE's, etc. The protocol is tuned to provide support for
> >> both
> >> > FAT and NTFS semantics.
> >> Huh? NTFS has these attributes. I don't know how they're implemented but
> >> from the protocol view they're exactly the same.
> >> Extended attributes will need some more thought but I'm not sure if I'm
> >> ready to tackle them this time around :(
> > Hmmm... Then NTFS offers a very large superset. EAs, by the way, are a
> > throwback to OS/2's HPFS. I guess I was just thinking about the fact that
> > the protocol is tuned to the specific OSes it was meant to support...
> Oh, by extended attributes I thought you meant ACEs, ACLs, SIDs and all
> that. So how do you get and set "extended attributes" and what are they
> used for? Otherwise I don't think doing access control lists et al will be
> useful unless we can do RPCs to make use of the SIDs. Ahtough we would be
> able to copy them with copyTo ... mmmm.
Here's a link: http://www.seds.org/~spider/spider/OS2/HPFS/ea.html
Both OS/2 HPFS and Windows NTFS support EAs. They're basically Name/Value
pairs that are maintained by the filesystem in association with (but not
as part of) a file. I *think* that some Unix (Linux and/or *BSD, I think)
filesystems may also support them now. New stuff if true.
There has been some talk of using them to store other forms of metadata
such as ACEs, etc.
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
More information about the jcifs