BTW, chmod 777 should never be used, it is practically always the wrong thing to do. If your intention is to allow ordinary users to write into those directories, make them owned by you, or by the group you belong to, which is why I changed the chmod in the above command.
What I want to do… is allow me to work under windows from that directory via samba.
As I got eclipse running on windows and some files I’m using as a project within eclipse are in that samba share… so do I set their owner to a samba group or something?
No logging in involved, I’ve set the share to ‘guest-ok’… so I’ll have to find out which userid the samba guest account has?
[edit]:
Or should I make a new group to which I add both the samba guest if even possible, and myself from the laptop (laptop running linux) (it’s a NFS share as well… for when I’m working under Linux).
Sure is getting complicated
In that case it’s whatever the guest account maps to. You could also create a Linux group to grant access, say a webdoc group, and then put all the accounts that need access in this group in /etc/group. The directories and files would then need group write permission, so a chown followed by a chmod g+w is needed on them.
However, just setting “guest ok = yes” does not guarantee all of the share’s
users will be the guest account. You might want to look at “man smb.conf”
for the usage of the following parameters, “force user”, “force group”,
ane “guest only”, and see if any of these are appropriate for you.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Made a new group htdocs and added nobody + Bakhuis to it, then set the folder to the group htdocs.
Bakhuis can’t do anything, but ‘nobody’ can.
Think I’ll just mount the SMB share on my linux boxes as well instead of having a double administration for both SMB and NFS shares and having to sort both their permissions… mainly didn’t in the first place because SMB felt a lot slower than NFS.
But they seem equally fast on 11.1.
With NFS there is the added complication that since the filesystem is exported, the permissions are evaluated at the client end. So assuming that the uids and gids match between server and client (another detail), it is the /etc/group on the client side that determines who has group access. In enterprise setups, there are usually site-wide passwd and group exported via NIS or LDAP to keep the uid, gids and names common and the admins sane.
On the other hand SMB permissions are evaluated at the server side. So your plan is fine.
Well as expected… I managed to not succeed in that either, but I created a new thread as it’s straying from this subforums focus. (and Swerdna is probably reading the other one more/able to help me out)