> Date: Thu, 26 Feb 2009 08:36:01 -0500 From: James Carlson
>
> Jordan Brown writes:
> > > I am sponsoring the following for fast track approval. The timer
> > > expires Wednesday 4 March 2009.
>
> You didn't specify a release binding or a stability level for the new
> interfaces.
>
> I'll guess at "patch/micro" and "Committed," and give it a +1
> (including the likely not-so-interesting '/' translation).
So what is supposed to happen if a process tries to access or create a
file with a pathname containing a '/' character? When creating a file,
when is a '/' a directory separator and when is it a character in a
filename?
If I have a file with filename "a/b" and a directory with filename "a"
and a file in that directory with filename "b", which file does an
open() of "a/b" open for me? If there is no directory "a", but there is
a filename "a/b", will open() of "a/b" give me ENOENT because "a" isn't
an existing directory. (Note that according to the standards, the
command:
printf "%s/%s" $(dirname a/b) $(basename a/b)
is supposed to print "a/b", not "./a/b" (i.e., they work on strings, not
on pathnames.)
- Don
