No collisions. There are other good reasons you dont want to do
forks on files that way (you need to enumerate them but if you
make them directories all hell breaks loose).
Hmm... so how else do you support n-forks cleanly preserving existing
semantics? I'm not sure I like Linus' suggestion, but I can't think
of anything better.
--cw
(On the whole, I think forks are horrible enough that we shouldn't
encourage them further than we do already with .AppleDouble, and
similar solutions... but, opinions vary greatly here)
-
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/