Bug#859003: systemd-container: strange permissions on /dev/pts/ptmx

Russell Coker russell at coker.com.au
Wed Mar 29 15:18:25 BST 2017

On Thu, 30 Mar 2017 01:00:33 AM Felipe Sateler wrote:
> From the kernel documentation:
> > As an option instead of placing a /dev/ptmx device node at /dev/ptmx
> > it is possible to place a symlink to /dev/pts/ptmx at /dev/ptmx or
> > to bind mount /dev/ptx/ptmx to /dev/ptmx.  If you opt for using
> > the devpts filesystem in this manner devpts should be mounted with
> > the ptmxmode=0666, or chmod 0666 /dev/pts/ptmx should be called.
> And indeed nspawn sets up /dev/ptmx as a symlink, while debian host
> does not do that. In the host, /dev/ptmx has 0666 permissions.
> [1] https://www.kernel.org/doc/Documentation/filesystems/devpts.txt

Fair point.

So why does systemd-nspawn do things differently than the host in this regard?

My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

More information about the Pkg-systemd-maintainers mailing list