Marc Chamberlin wrote:
Does Samba actually complain
when you define '/' as a share? it seems to me it ought to if it is not supported or enabled.
Sort of, it gives you a warning about the security implications of sharing '/' but it appears to allow one to define the share. Trouble is I can't get it to work and actually allow '/' to be shared.
Okay. So samba permits the share, but it's not working, somehow.
Uh yes, I have tried defining path as /slash as well. Up to now that only made sense when I defined the bind mount for /slash, in fstab, which I am trying to avoid.
Aha - I thought you were fairly happy with that solution, except for YaST not quite understanding what's going on.
Below you pointed out another possibility, to use autofs and automount to do the bind mount when it is needed, and to automatically dismount it when no longer needed. I really like the idea, trouble is I am not figuring out how to do it, and Google is not being friendly.
For your fstab: / /slash none bind,x-systemd-automount,x-systemd.idle-timeout=xxx 0 0 (not tested). I don't know how well that automount will interact with Samba though.
But without the bind mount defined in fstab, tools like autofs will no longer mount the "root" / directory though I do not grok why.
On the 'source' system, maybe set up an automount of / to /slash? I.e. only do the bind mount when /slash is needed? Ought to be dead easy with systemd automount.
Hmmm I would love it if you say more, or better yet provide examples.
Sorry. See above - systemd automount works really well for the common, simple cases. -- Per Jessen, Zürich (12.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.