This is a poor design decision on the part of the Linux systems 
implementers, as it breaks backward compatibility.  There is no reason 
that an "auto-translator" from CIFS to what has been used in 
unix/BSD/linux for a very long time should not have been implemented. 
Although this practice is not uncommon in the profiteer sector as 
planned obsolescence for cash flow and other fiscal measures dominate, 
and for which the customers have very little control (the typical EULA 
is similar to the Godfather's offer you cannot refuse), it should be 
different in the open systems source code sector.  Has anyone written a 
script that converts "old" into CIFS?

Yasha Karant

On 8/17/21 6:14 AM, Mark Stodola wrote:
> On 8/17/21 7:38 AM, Ekkard Gerlach wrote:
>> Hi,
>>
>> options gid=users,file_mode=0777,dir_mode=0777 are ignored in SL 6.10:
>>
>> root@arthur:/home/pc41# /bin/mount -t cifs  //10.0.0.41/public 
>> /home/pc41/usb-stick -o 
>> username=xxx,password=xxx,gid=users,file_mode=0777,dir_mode=0777
>> root@arthur:/home/pc41# ls usb-stick/ -l
>> insgesamt 0
>> drwxr-xr-x 3 root users 0 17. Aug 13:39 DCIM
>>
>> You see: "root users" and users can't write, mode 777 is ignored. With 
>> old Suse-server worked for 5 years.
>>
>> tia
>>
>> Ekkard
> 
> gid, file_mode, dir_mode are all "fallback" values if they are not 
> provided by the CIFS server.  So if your server has the CIFS unix 
> extensions, those permissions are honored and the *_mode options are not 
> applied.
> 
> If you haven't, I would read the man page mount.cifs(8) and the section 
> "File and directory ownership and permissions."
> 
> I hope that helps.
> 
> -Mark