[Bug 482978] Re: ls can't cross mounted filesystems with ".." in path
Launchpad Bug Tracker
482978 at bugs.launchpad.net
Sun Oct 21 04:17:26 UTC 2012
[Expired for coreutils (Ubuntu) because there has been no activity for
60 days.]
** Changed in: coreutils (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/482978
Title:
ls can't cross mounted filesystems with ".." in path
Status in “coreutils” package in Ubuntu:
Expired
Bug description:
Binary package hint: coreutils
I suspect the real problem is in something ls uses - hopefully
coreutils developers will be in a better position to determine the
underlying cause.
I'm using crypto/lvm2 and have root mounted on one lvm ext4 partition and /v3c mounted on an ext3 lvm partition.
If I do
$ ls /usr/share/bison/../../../v3c/dev/autobook/parse/build/../v3c/flexx/tests/bison_calc.m4
I get "No such file or directory".
But with
$ ls /v3c/dev/autobook/parse/build/../v3c/flexx/tests/bison_calc.m4
the file gets listed.
/bin/ls isn't the only program to exhibit this behaviour - m4 is doing the same thing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/482978/+subscriptions
More information about the foundations-bugs
mailing list