On Mon, May 01, 2006 at 02:08:24PM +0200, thomas parquier wrote: > Ok, I've just changed the classic mount to a bind-mount, for the home > partition. > But there's still the error a mentioned. Regarding the twice > auto-mounted remote shares, I believe that if you're right about twice > mounted filesystem, it should not be good to do so with autofs too. > But I don't how to deal with all that. The problem with bind-mounted > folders is that it seems not to be correctly sync'ed : I mean remote > shares auto-mounted in the original folder are not visible in the > bind-mounted one.
It isn't supposed to. bind mounts make a clone if exactly what is there right now at the time of the mount. Anything added later is new stuff and does not and should not be bind mounted. A common workaround is to do this: point automount to /mychrootpath/home/... ln -s /home -> /mychrootpath/home So your automounter points at the chroot path from the main system, and can of course access everything. The chroot knows nothing other than when it asks for something, somehow it magically gets mounted. The main system being able to see the chroot stuff can use a symlink to it just fine and cause the automounter to work. What this doesn't solve is trying to have two chroots work with an automounter. For that I can't think of any solution. It would be nice to have a bind mount that actively passes on new mounts under the original one, but at this time I don't think we have any such thing. Even rbind just recursively bind mounts every mount in a tree, that are present when the rbind mount is performed but does nothing for new mounts later on. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
