On Tue, 28 Mar 2006, Thomas Hood wrote: > Now that I understand it, the patch as provided by R. Ramkumar looks OK to me. > (When domount's first argument is "bind", the function does a bind mount.) > > HMH: Can you explain your idea further? What do you envision domount() doing > when its first argument is "none"?
It just does what it is doing right now. All it needs to do is accept "none" as valid, even if it is not listed in /proc/filesystems (it will never be listed there). All of the bind/namespace manipulation functions of mount can be invoked either by using mount --<function>, or by using mount -t <whatever, it will be ignored> -o <function>. Set up a bind mount, and then run mount. Look at how it is reported. It will have the artificial type of "none". Mount accepts that syntax to create the mount as well: mount -t none /initial /target -o bind (or, for that matter, -o move, -o rbind, -o after, -o before, -o over..., and I suppose if we ever update our mount, -o make-shared). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]