what's going on here? the bind of an empty directory onto /net seems to disrupt the mount table somehow. i can't think of an existing feature of the namespace implementation that would explain this behaviour. is something ignoring the device number, maybe?
does anyone else get the same behaviour? % bind /net /net.alt % mkdir /tmp/empty % bind /tmp/empty /net % cd /net.alt/tcp Can't cd /net.alt/tcp: '/net.alt/tcp' file does not exist cpu% ls -l /net.alt/tcp ls: /net.alt/tcp: '/net.alt/tcp' file does not exist % cd /net.alt % cd tcp % ls -l --rw-rw-rw- I 0 network bootes 0 Jun 28 12:36 clone --r--r--r-- I 0 network bootes 0 Jun 28 12:36 stats % [sorry if this post appears a few times in different forms; i'm trying to get past what i assume is a garbage detector, so i'm assuming that more text to transcript might make it think it's a legit post, but you never know; i'll just keep adding random text until its likes it. or maybe it's something else entirely; we'll see. sorry for this garbage]
