On Tue, Jun 04, Carlos E. R. wrote:
2. "Cooperative duos". Picking systemd as my example:
systemd itself cannot offer defaults to start arbitrary programs, because arbitrary programs live at arbitrary paths; it has to rely on another package providing additional information.
Consequently, systemd needs to read *two kinds* of files, namely the *vendor snippet* from /usr/lib/systemd/system/, and the *user preference snippet* from /etc/systemd/system/.
Except the systemd configuration files, such as "/etc/systemd/journald.conf", which have a single copy.
There are always configuation files, which you have to copy as whole. E.g. PAM configuration files, or configuration files using xml or json. But this are the exceptions. And there are libraries, which can do already today what systemd is doing. In go, it took me some minutes to teach an application to read the configuration the systemd way. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org