> On that whole subject...
>
> Do we need a Unix domain socket equivalent to openat()?
I don't think so. The name is just a file system indexing trick, it's not
really the socket proper. It's little more than "ascii string with
permissions attached" - indeed we also support an abstract name space
which for a lot of uses is actually more convenient.
AF_UNIX between roots raises some interesting semantic questions when you
begin passing file descriptors down them as well.