New versions of samba detect if the other end is also linux, and use protocol extensions (or something) to become a unix file-sharing system: symlinks, owner IDs and permissions all appear on the other end as they should.
Which is nice, but the three machines here at home didn't have a unified UID map, and many of the symlinks are local-only. Thus, they end up being either broken, or, worse still, pointing to a local copy without warning. I was going to switch to nfs sometime, and deal with all that; but not this week!
I don't think I have it all symmetric yet, either, so the usernames and permissions are sometimes transmitted in one direction but not the other. Thus, machine A creates a directory on machine B, whereupon it doesn't have permissions to actually put anything in there; so recursive copies fail.
Comments
Anonymous: Did you use cifs instead smbfs? It works only with cifs. You need also mount.cifs which is not shiped by default on current linux distributions.
JB: Nope, just upgraded to 2.6 from Debian testing.
Ben Morse: In order to fix the samba/symlink problem inbetween 2 linux machines, do this: in /etc/samba/smb.conf under the [global] section add this:
unix extensions = no
I did this on both linux machines. It fixed the problem right away. More info: http://uranus.it.swin.edu.au/~jn/linux/smbfs/
JB: Thanks - that would've been the right work-around... Since then I've migrated everything to take advantage of the new features, but at that moment I would've preferred to just turn it off for a bit.
⇦ Ainulindalë and the Transactional Interpretation of Quantum Mechanics | ⇨ fixlevels |
