[I reopened the bug, but I didn't realize I had to explicitly cc to have
my reasoning be accessible, sorry]
Even if the mounts are equivalent at the kernel level, there certainly
is information lost compared to the mtab in squeeze: namely where within
the filesystem the bind mount originates.
Example:
david@feline:~/ > mount | grep '/home '
/dev/mapper/vghs-home on /home type ext4 (rw)
david@feline:~/ > sudo mount -o bind /home/david/tmp /mnt
david@feline:~/ > cat /proc/mounts | grep 'vghs-home'
/dev/mapper/vghs-home /home ext4
rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/mapper/vghs-home /mnt ext4
rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
The 2nd entry is for the bind mount. In squeeze the mtab contained:
/home/david/tmp on /mnt type none (rw,bind)
So how do I figure out that /mnt refers to '/tmp' inside the device
/dev/mapper/vghs-home in wheezy?
Thanks,
~David
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
