units: tmpfiles-setup-dev - allow unsafe file creation to happen in /dev at boot This will allow us to mark static device nodes with '!' to indicate that they should only be created at early boot.

readahead: wipe out readahead

units: conditionalize static device node logic on CAP_SYS_MODULES instead of CAP_MKNOD npsawn containers generally have CAP_MKNOD, since this is required to make PrviateDevices= work. Thus, it's not useful anymore to conditionalize the kmod static device node units. Use CAP_SYS_MODULES instead which is not available for nspawn containers. However, the static device node logic is only done for being able to autoload modules with it, and if we can't do that there's no point in doing it.

units: bring systemd-tmpfiles-setup-dev.service closer to systemd-tmpfiles-setup.service Among other things, order both services relative to systemd-sysusers.service in the same direction.

units: properly capitalize the unit description

kmod-static-nodes: remain after exit

systemd-tmpfiles-setup-dev: remain after exit Without this, tmpfiles-setpu-dev would be re-run if any other service, which pulls in basic.target, was started after setup-dev was finished and before basic.target was active.

static-nodes: move creation of static nodes from udevd to tmpfiles As of kmod v14, it is possible to export the static node information from /lib/modules/`uname -r`/modules.devname in tmpfiles.d(5) format. Use this functionality to let systemd-tmpfilesd create the static device nodes at boot, and drop the functionality from systemd-udevd. As an effect of this we can move from systemd-udevd to systemd-tmpfiles-setup-dev: * the conditional CAP_MKNOD (replaced by checking if /sys is mounted rw) * ordering before local-fs-pre.target (see 89d09e1b5c65a2d97840f682e0932c8bb499f166)

man: link systemd-tmpfiles-setup-dev.service

units: rename systemd-static-nodes -> systemd-tmpfiles-setup-dev This is really just a special case of systemd-tmpfiles-setup, moreover it could easily create more than static nodes.