Mike Meyer wrote:
You can make that happen:
# cd /usr
# mount /dev/<blank> /usr
# vim
vim: not found
# ls /usr/bin
ls: /usr/bin: No such file or directory
# ls bin This will show the contents of /usr/bin before
the mount, because it looks in "./bin", and
"." is on the original /usr, not the new one.
# bin/vim will find bin/vim
# pwd This is both true and not true. The current
/usr/bin directory is /usr/bin, but you won't get there
if you cd to /usr/bin.
Yes indeed this was what happend I was in /usr before I
started sysinstall, did the repartition, quit and tried
to run vim to edit /etc/fstab. This failed but when I did
a straight ls -l ( which was still in /usr ) everything
appeared normal.
So the behaviour is explained by the fact that the shell
still had the handle to the original /usr before the second
mount and as such presented the nfs mounts details.
Thanks guys for spending the time to explain that. All
is clear on this front now just need to determine what is
causing the FS corruption now, for which I need to wait
for some machines to be delivered so I can try doing the
test with just /data hence avoiding any interaction with
/usr.
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
