4 Mar
2008
4 Mar
'08
2:38 a.m.
Cameron Kaiser <spectre at floodgap.com> writes:
Oh really?
% touch \/path
% ls -l \/path
-rw-r--r-- 1 luser luser 0 Mar 3 17:55 /path
% pwd
/home/luser
% ls -l /path
ls: /path: No such file or directory
If your machine *really* does that, not only do you have very
different filesystem behaviour from every other Unix system I've seen,
but also a very unusual shell, since it's not expanding \/ to /. Try
"echo ls -l \/path" and "echo ls -l /path" -- do they give different
output for you?
Are you sure that something else didn't delete /path between the last
two commands? If I do that on a MacOS X machine, the last command
(correctly) gives me the same output as the previous "ls".
The one oddity related to slashes in filenames in the POSIX spec is
that absolute paths starting with two slashes "may be interpreted in
an implementation-defined manner"; some systems use(d) this for
distributed filesystems.
--
Adam Sampson <ats at offog.org> <http://offog.org/>