This behaviour only exists on vfat, not on msdos, smbfs, hpfs, ext2,
proc, nfs, or ncpfs (though that last actually does support "cd ..." from
DOS clients, but not Linux clients, as a legitimate feature; "cd ..."
changes to the parent's parent, "cd ...." changes to the parent's parent's
parent, and so on 'til you run out of parents). The machine is 5 miles away
and hasn't got a CD in its drive at the moment, so I can't test iso9660.
Both bash and tcsh behave pretty much the same way (pwd can't figure
out the current directory at all in tcsh, but the $PWD environment variable
contains the "/win95/mps/civ2/..." directory), so I assume this is a
filesystem bug.
The machine is a 2.0.35 box with a non-FAT32 VFAT partition created
by Win95 OSR2 (I think... I'm not certain about the Win95 release number).
I'm not equipped at the moment to check if the behaviour's the same in other
kernel versions - 2.1 kernels, or the ones before FAT32 was added to 2.0,
for example.
--- John Campbell jcampbel@lynn.ci-n.comQotD: Live fast, die young, leave a heavily modified corpse.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html