Lines Matching refs:in

3 such that indices of ptys allocated in one instance are independent of indices
4 allocated in other instances of devpts.
14 If CONFIG_DEVPTS_MULTIPLE_INSTANCES=n, there is no change in behavior and
20 'newinstance' option (as in current start-up scripts) the new mount binds
30 the mount is considered to be in the multi-instance mode and a new instance
31 of the devpts fs is created. Any ptys created in this instance are independent
32 of ptys in other instances of devpts. Like in the single-instance mode, the
44 	# We are now in new container
51 /bin/bash in the child process.  A pty created by the sshd is not visible in
85    	- adding ptmxmode mount option to devpts entry in /etc/fstab, or
93    Or, in general, container-startup scripts should use:
104    /dev/pts/ptmx redirection would result in an unusable/unreachable pty.
112     would create a pty, say /dev/pts/7, in the initial kernel mount.
113     But /dev/pts/7 would be invisible in the new mount.
124 7. A mount of devpts without the 'newinstance' option results in binding to
126    does not provide strict isolation in a container environment. i.e by
131    including the mount in the root container, should use the newinstance