Hi Alan -- thanks, I didn't know about the DOS bits, though I'd found the Windows ACLs (which most users don't know about and apps don't use much.) I've learned that it is actually possible to adjust UNIX "chmod" permissions through Windows owner-ACLs.
However, it's important to say that this isn't a good solution for Windows users. Windows makes considerable effort to hide the ACL system from users - the "read-only" DOS attribute is super-easy for a user to adjust, but changing the owner-ACL requires one to enable an obscure setting. So this is a big hole in basic usability--the average user who "owns" a read-only CIFS file will be able to do nothing at all with it. Not delete it or rename it, or make it writable. If I make all files writable on the UNIX side, it appears as if the DOS bits do work as you say, and this would indeed work if people only ever used a Windows client. But there are many cases where UNIX and Windows usage overlap (e.g., uploading files to a live webserver). Also, many Windows applications use the read-only bit as a lightweight form of file locking, so it seems as if making that visible on the UNIX side would be preferable to making it a private "DOS" bit. Similarly (my case!) this makes migration from an existing Samba install hard, since the administrator has to remap all the attributes. So, even if the default isn't changed, I'd like a way to turn on the normal Samba behavior - is there a way to expose this option as a setting? thanks, mike -- This message posted from opensolaris.org _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
