On Thu, Jan 17, 2008 at 09:36:11AM +0100, Miklos Szeredi wrote:
quoted text
> > I'd suggest doing a new file that would *not* try to imitate /etc/mtab.
> > Another thing is, how much of propagation information do we want to
> > be exposed and what do we intend to do with it?
> 
> I think the scheme devised by Ram is basically right.  It shows the
> relationships (slave, peer) and the ID of a master/peer mount.

 Yes. It also shows the full relationship between source and
 destination for bind mounts. Now the /proc/mounts is useless:

  # mount --bind /mnt/test /mnt/test2

  # cat /proc/mounts | grep test
  /dev/root /mnt/test2 ext3 rw,noatime,data=ordered 0 0


quoted text
> > What do we want to *do* with the information about propagation?
> 
> Just feedback about the state of the thing.  It's very annoying, that
> after setting up propagation, it's impossible to check the result.

 Exactly.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html