[systemd-devel] binding tmpfiles.d to unit startup

[Lennart Poettering]

On Mon, 03.03.14 15:48, Holger Schurig (holgerschurig at gmail.com) wrote:

> Hmm, that gave me one thougth: if systemd starts as PID 1 and no
> /etc/passwd etc doesn't exist, I can very well understand that, when
> compiled with --enable-privioning, it should create those things. But
> the "c "-line could be happily handled by a shell script. So my
> proposal is to only add things into systemd-provision that absolutely
> must be done by pid 1, because without it /bin/dash or most user-space
> won't run. But then systemd-provision should just execute provision
> shell scripts in /lib/systemd/provision.d (or similar). No need to
> re-create "cp", for example. Also it gives overall a bigger
> flexibility.

The explicit goal here is to have something declarative for recreating
/etc and /var. Something one can easily turn into a file list for rpm or
dpkg. Which means shell scripts are not suitable for this, because they
are imperative...

Lennart

-- 
Lennart Poettering, Red Hat