Lennart Poettering has published a further consequence of blog posts about Systemd. This issue deals with the configuration. Systemd leads not introduce new concepts and wants to remain compatible with various Linux distributions, however, strives for a unification.
One of the goals of Systemd, boot the system without executing shell scripts is, according to Poettering largely achieved. Because of the simple and well-defined formats of the known configuration files according to him it was quite easy to replace the numerous shell scripts by C code. However, there are files that differ in the path or in the format between the distributions. Systemd can deal with all this, but that’s a lot of case distinctions in the code required.
To improve this situation, Systemd defines its own configuration files. These are read by preference, and only if they are not present, will fall back on distribution-specific configuration files. Systemd leads however, no new concepts, but based on the existing files. Goal of Systemd is that using the distributions that Systemd to take these files and then the configuration is unified by little.
Objections to the names and contents of the configuration files are largely too late, since this topic was discussed already in various ways according to Poettering with representatives of all interested distributions. The newly defined files are the result of the discussions and were accepted by all.
In the course of the contribution is Poettering configuration files from the. / etc / hostname contains the host name as is expected of the system. / etc / vconsole.conf configures the keyboard and the console font, / etc / locale.conf the language.