//192.168.1.2/folder /home/nemo/123 cifs ro,noauto,user=username,uid=100000,gid=100000,vers=2.02 0 0
Password for username@//192.168.1.2/folder: ***
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
@remote Oh, I’m sure it does (for others at least), thanks for the link. I hadn’t enabled that repository while searching for the package. Whilst being over six years old, it should still work.
Regarding your original question: what happens if you play with the mount arguments a bit, by omitting them one by one, to identify the one your mount.cifs binary doesn’t like?
I just installed NielDK’s cifs-utils package on my J1 and can confirm the EINVAL (error 22) for vers=2.02 only. If I omit this, I get an EACCESS (error 13).
I have a suspicion that this would have worked on an OS earlier than 3.3 … but I have no such device here to test.
I’ve just started going through the code, so I’m not certain, but it doesn’t seem to have many dependencies at all. Just a linux kernel and the kernel module But I would definitely host it on chum.
Right you are. Distros often overcomplicate things. Like I do … thanks for the tip.
I have a number of old samba servers in the house (one is just on the router). fstab: \\192.168.178.20/share /home/mwa/smb/share cifs rw,uid=1000,gid=1000,username=mwa,password=blah,_netdev,vers=1.0 0 0
Those servers also have sftp but are so old that the key material on sfos doesn’t like it … thanks for the tip!