> Bullshit. It happens all the time. Rio+Plumber is a simple example.
In the standard profile, as set up by /sys/lib/newuser
or demonstrated in /usr/glenda/lib/profile,
plumber is run before rio starts, so rio has
plumber mounted but not vice versa:
% grep plumb /proc/^`{ps|grep rio|awk '{print $2}'}^/ns
/proc/86746/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86768/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86769/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86770/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86771/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86772/ns:mount #s/plumb.rsc.86763 /mnt/plumb
/proc/86773/ns:mount #s/plumb.rsc.86763 /mnt/plumb
% grep rio /proc/^`{ps|grep plumb|awk '{print $2}'}^/ns
%
If you want to actually cause a loop, then you could run
plumber in your riostart (as in rio -i riostart) file. But there
are plenty of ways to shoot yourself in the foot with
ref count loops if you really want to go there. A much
more direct one is to run a file server that mounts
itself into its own name space.
Russ
