And that's already bad enough. Most of the "files" in proc should
be fifos! And using proc as an excuse to introduce another set of
magic dirs? No, thanks.
> Correct me if I'm wrong, but what we learn from the proc example
> is that tarring your whole source tree starting at / is not something
> you want to do.
IMHO it would be better to fix proc instead of adding more magic. At
the moment you have to exclude /proc. You want to add /dev. And next?
Exclude all $HOME/dev (in case process name spaces get added)? Or make
fifos magic too and add all of them to the exclude list? But there's
no central place for fifos. So lets add more magic :-(
> What *won't* happen is, you won't get side effects from opening
> your serial ports (you'd have to open them without O_DIRECTORY
> to get that) so that seems like a little step forward.
As already said: depending on O_DIRECTORY breaks POSIX compliance
and that alone should kill this idea...
Over and out, ET.
-
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/