Robert Watson wrote:
First, could you identify the version of FreeBSD you're running?
This is on -CURRENT as of a few days ago.
Second, can you include script output of the shell session in which you mount /proc, /mnt, run mount to confirm they are both mounted, then umount one, run mount to show the wrong one unmounted?
The following demonstrates the problem. I've included a final 'ls' to show that it's not just a reporting problem with 'mount'; the wrong filesystem is really getting unmounted. big# /sbin/mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1g on /home (ufs, local, acls) /dev/ad0s1f on /tmp (ufs, local, soft-updates) /dev/ad0s1h on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) big# /sbin/mount -t procfs proc /proc big# /sbin/mount -t procfs proc /mnt big# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1g on /home (ufs, local, acls) /dev/ad0s1f on /tmp (ufs, local, soft-updates) /dev/ad0s1h on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) procfs on /mnt (procfs, local) big# /sbin/umount /mnt big# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1g on /home (ufs, local, acls) /dev/ad0s1f on /tmp (ufs, local, soft-updates) /dev/ad0s1h on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) procfs on /mnt (procfs, local) big# ls /proc big# ls /mnt 0 1156 18 24 30 378 436 509 531 9 1 1173 19 25 31 38 44 520 532 curproc 10 12 2 26 32 39 441 521 537 11 13 20 27 33 4 444 522 6 1151 14 21 28 34 40 468 523 624 1153 15 22 280 35 41 470 524 625 1154 16 226 29 36 42 478 525 7 1155 17 23 3 37 43 5 529 8 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
