On 22/06/15 18:02, Erwan David wrote:
What is the use of this libsystemd0 you get even when systemd was never installed ?
Utility functions for programs designed to be run in a systemd-based environment, or to run in many environments but also take advantage of capabilities offered by a systemd-based environment. The nature of shared library linking in Unix means that binary executables in the latter category need libsystemd0 to be present even if they are being run in a non-systemd-based environment.
*If* this bothers you, you should run a source-based distribution instead of a binary distribution, so that you have stronger control over what software runs on your systems.
Where are migration tutorials, docs for people who did not develop systemd ?
Migration tutorials really are best written by people who both (a) are good at writing tutorials (it's a *quite* distinct skill from writing reference documentation) and (b) have migrated non-trivial systems from $OTHER_INIT_SYSTEM to systemd.
Quite a few people who did not develop systemd have found the man pages adequate. What, specifically, do you find inadequate?
I still have a setting working without systemd that I do not know hoxw to make with it. I still do not know what a mount unit is.
A mount unit is a unit that describes a mount point in the system, specifying which filesystem should be mounted, which options should be used, etc. Usually, they are automatically generated (with predictable names) from the contents of /etc/fstab.
I saw that systemd can start daemons when a certain disk is mounted, I still look how to do it, etc...
You can require a certain service to be running before a certain filesystem is mounted by writing an explicit mount unit for that filesystem which lists the required service as a Requires: dependency.
You can require a certain filesystem to be mounted before a certain service can be started by listing that filesystem's mount unit name in the dependencies of the service.