> > AF_UNIX between roots raises some interesting semantic questions when > > you begin passing file descriptors down them as well. > > Why is that? A file descriptor carries all that information with it... Things like fchdir(). It's not a machine breaking problem but for containers as opposed to chroot we need to be clear what the expected isolation sematics are. Agreed on open() for sockets.. the lack of open is a Berklix derived pecularity of the interface. It would equally be useful to be able to open "/dev/socket/ipv4/1.2.3.4/1135" and the like for scripts and stuff That needs VFS changes however so you can pass the remainder of a path to a device node. It also lets you do a lot of other sane stuff like open /dev/ttyS0/9600/8n1 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
