onlyjob

On Tue, 18 Jun 2013 21:05:19 Reda NOUSHI wrote: > @onlyjob, could you also take a look at the kernel source to see if I missed some way to do...

On Debian one can just use official package. Alternatively build dependencies can be installed by the following command: `sudo apt-get build-dep libteam`

Supporting service templates would be really nice. I've just found that on Debian default _postfix_ instance is named "-" but currently systemctl replacement do not support `systemctl start [email protected]`...

> Just because tools like `systemd-resolved` and `systemd-timesyncd` "shouldn't" run in a container doesn't mean there aren't use cases. For instance, I use Docker to unit test Ansible roles that...

I'm not familiar enough with codebase to have an opinion, if the question was addressed to me...

It might be the best to implement [systemd-tmpfiles(8)](https://manpages.debian.org/unstable/systemd/systemd-tmpfiles.8.en.html) binary that can be called as follows: systemd-tmpfiles --remove --create /usr/lib/tmpfiles.d/php7.4-fpm.conf

Fair enough, thanks. Of course there are workarounds but I think _systemctl_ aims for compatibility with systemd .service files and management interface. `tmpfiles.d` appears to be a part of that...

This is already reported in #62 and (temporary) [workaround](https://github.com/gdraheim/docker-systemctl-replacement/issues/62#issuecomment-489865412) is available.

Please do not commit common third party libraries like _zlib_, which is already shipped by all major GNU+Linux distributions. See also https://wiki.debian.org/UpstreamGuide specifically "No inclusion of third party code" section...

Thanks for explanation and for considering. Current versioning is weird and unusual with too many meaningless version numbers. If intention was to just keep `1.99` and append semantic version to...