They are not, the device file and the directory are different objects
that have the same name. In C, "foo" and "struct foo" can appear in
the same scope but they are different objects. This must have seemed
to be a strange idea at first. Here we have "foo" (a device) and
"directory foo" (the device's properties).
When I first saw Linus mention the idea I did a double-take, I thought
it was a strange idea and my first reaction was, it would break all
kinds of things. But when I started examining cases I was unable to
find any real problems. When I asked code examples of breakage none of
the supplied examples survived scrutiny. Then, when I looked through
SUS I didn't find any prohibition.
> The last time this was
> discussed was for handling forks (a la Mac et al) in files, and it
> was shot down.
Do you have the subject line? It might save us some time ;-)
I seem to recall that the fork idea died because it was thought to
require changes to userspace programs such as tar and find. The
magicdev idea doesn't require such changes, none that I've seen so far.
> > SUS doesn't seem to have a lot to say about this. The nearest
> > thing to a ruling I found was "The special filename dot refers to
> > the directory specified by its predecessor". Which is not the same
> > thing as:
> >
> > open("foo", O_RDONLY) == open ("foo/.", O_RDONLY)
>
> It says "foo" and "foo/." are the same _directory_, where "foo" is a
> directory as otherwise "foo/<something>" makes no sense, AFAICS. Is
> there any mention on a _file_ "bar" and going "bar/" or
> "bar/<something>"?
In SUS I didn't find anything, one way or the other. I don't know
about POSIX.
-- Daniel- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/