systemd-197/NEWS has this:
systemd will no longer detect and recognize specific distributions.
All distribution-specific #ifdeffery has been removed, systemd is now
fully generic and distribution-agnostic. Effectively, not too much is
lost as a lot of the code is still accessible via explicit configure
switches. However, support for some distribution specific legacy
configuration file formats has been dropped. We recommend
distributions to simply adopt the configuration files everybody else
uses now and convert the old configuration from packaging scripts.
Most distributions already did that. If that's not possible or
desirable, distributions are welcome to forward port the specific
pieces of code locally from the git history.
One of the consequences of this seems to be that systemd will no longer
automatically populate and gratuitously enable service files from
/etc/init.d/<scripts>, though these scripts will still be called if they are
referenced explicitly, with "sudo systemctl start <script>". While
systemd-196 works pretty much "right out of the box", systemd-197 is a bit
more challenging.
Providing a set of default systemd service files for debian would be a
solution. These would not conflict with the init scripts, which are simply
ignored by systemd when they are not needed, and would probably help achieve
the faster boot-times promised by systemd.
James
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
