Alan Cox wrote: > 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. I did say that as being the desired *eventual* goal. > Should /dev/ptmx give you a node in the 'master' pty namespace or a node > in your current containers pty namespace ? Well, since there is no "current containers pty namespace" per se, it will give you a node in the default (initial) pty namespace unless the bind mount is set up. -hpa _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
