Source: hurd X-Debbugs-CC: [email protected] On Wed, Sep 3, 2014 at 1:21 PM, Gabriele Giacone <[email protected]> wrote: > sbuild/schroot suffer a bindmount bug we already talked about but not > tracked yet. Briefly, > mount -o bind foo0 foo1 > mount -o bind foo2 foo1/bar > proc/mounts displays: > /dev/hd0s1 foo1 > /dev/hd0s1 foo0/bar > instead of > /dev/hd0s1 foo1 > /dev/hd0s1 foo1/bar
Filing bug in question. CHROOT_FILE_UNPACK_DIR is bindmounted on CHROOT_MOUNT_LOCATION. Hurd also needs bindmounting /dev and /servers on respectively $C_M_L/dev and $C_M_L/servers, but due to this bug, bindmounts-on-bindmounts result mounted on first bindmount source device i.e. CHROOT_FILE_UNPACK_DIR. e.g. I: 10mount: settrans -a /var/lib/schroot/mount/test00 /hurd/firmlink /srv/chroot/schroot-unpack/test00 I: 10mount: settrans -a /srv/schroot/mount/test00/dev /hurd/firmlink /dev I: 10mount: settrans -a /srv/schroot/mount/test00/servers /hurd/firmlink /servers produces /dev/hd0s7 /srv/schroot/mount/test00 /hurd/ext2fs writable,no-inherit-dir-group,sync=5 0 0 /dev/hd0s1 /srv/chroot/schroot-unpack/test00/dev ext2fs writable,no-inherit-dir-group,store-type=typed 0 0 /dev/hd0s1 /srv/chroot/schroot-unpack/test00/servers ext2fs writable,no-inherit-dir-group,store-type=typed 0 0 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/cabcawc0tffj3p8n16zzrswtgegixkkrfmlberaaj5fnq-xn...@mail.gmail.com
