Re: [systemd-devel] [PATCH] core: mount new devpts instance for PrivateDevices=yes (was: PrivateDevices=yes and /dev/ptmx)

Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git ___

[systemd-devel] [PATCH] core: mount new devpts instance for PrivateDevices=yes (was: PrivateDevices=yes and /dev/ptmx)

On 09.03.2016 16:31, Yuriy M. Kaminskiy wrote: When systemd makes mount namespace for PrivateDevices=yes, it bind-mount outer /dev/pts [1], and makes symlink pts/ptmx -> $tmpdir/dev/ptmx (src/core/namespace.c [mount_dev]). However outer /dev/pts is mounted *without* option ptmxmode (src/core/mou

[systemd-devel] DeviceAllow and hotplugged devices/modules

If 1) service has [Service] DevicePolicy=closed DeviceAllow=char-foobar rw # or "char-*", or "/dev/foobar*" 2) foobar module is not loaded and foobar major is not known to kernel yet at the moment service started, 3) some time after service was started, foobar module is loaded (e.g. t

[systemd-devel] Container IP resolution by name inside another container

Hello, on a host running Fedora 23, with systemd 222, I set up two containers (Fedora 23 too) in /var/lib/machines with "dnf --installroot ..." ; the host and both containers have systemd-networkd and systemd-resolved enabled and started. Containers are started with "machinectl start name".