Package: mount Version: 2.12p-8 Severity: normal >From my /etc/fstab: /dev/mapper/Root-Root / ext3 defaults,errors=remount-ro 0 1 / /space/chroot/i686-shared none bind 0 0
>From /etc/init.d/umountroot: mount -n -o remount,ro / /space is not on the root filesystem, so by the time we reach umountroot, it has already been unmounted. Even if it hadn't, /space/chroot/i686-shared would have been unmounted. I get the error "mountpoint /space/chroot/i686-shared does not exist", and the rootfs is left read-write instead of read-only. I don't understand why mount prefers to use the device column of /etc/mtab in this situation over the directory column. There will essentially never be anything bind mounted over a device node, so if the specified command line option matches both a directory and a "device", the user almost certainly meant the directory. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-rc1 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mount depends on: ii libblkid1 1.38-2 block device id library ii libc6 2.3.5-7 GNU C Library: Shared libraries an ii libuuid1 1.38-2 universally unique id library mount recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
