O> We can't, really, because it will open the global ptmx. This is an > unfortunate side effect of the backwards-compatibility code. > > This is also why I don't like the bind mount; the symlink option has the > nice property that f*ckups are more obvious. It's asking for trouble with existing systems and users that upgrade. /dev/ptmx should remain a proper device file for the non container case. Should /dev/ptmx give you a node in the 'master' pty namespace or a node in your current containers pty namespace ? _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers