I ran into a cosmetic problem using ls when you're in a mount point, mount
something there, and then try to ls it. It works fine if you cd back into
the mount point, however.
on some first vt, with nothing mounted at /mnt...
b64952:~$ cd /mnt
b64952:/mnt$ ls
b64952:/mnt$
then on another vt....
b64952:~# mount /dev/cdrom /mnt
mount: block device /dev/cdrom is write-protected, mounting read-only
b64952:~#
back to the first vt...
b64952:/mnt$ ls
/bin/ls: 00_TRANS.TBL: No such file or directory
[...snip...]
/bin/ls: UPGRADE.TXT: No such file or directory
b64952:/mnt$ cd /mnt
b64952:/mnt$ ls
00_TRANS.TBL COPYING FAQ.TXT LOWMEM.TXT README.TXT
[...snip...]
my version info....
b64952:~$ echo $SHELL
/bin/bash
b64952:~$ bash --version
GNU bash, version 2.03.0(1)-release (i386-slackware-linux-gnu)
Copyright 1998 Free Software Foundation, Inc.
b64952:~$ uname -a
Linux b64952 2.2.13 #5 Sat Feb 19 22:36:46 EST 2000 i586 unknown
b64952:~$ ls --version
ls (GNU fileutils) 4.0
I tried this under tcsh as well, and got identical results.
(under tcsh)
b64952:~> echo $version
tcsh 6.08.00 (Astron) 1998-10-02 (i386-intel-linux) options
8b,nls,dl,al,rh,color
---
Jeff Ames
[EMAIL PROTECTED]
http://vorlon.ces.cwru.edu/~ames/
