Hi Josselin, reading through the systemd position statement [1], I ran into a statement that is either incomplete or incorrect:
The upstart position statement [2] states: <-- snip --> systemd is hasty. ... While we are committed to having sane upgrade paths and not depend on such kernel features prematurely. <-- snip --> The answer in the systemd position statement says: <-- snip --> ... Compatibility at upgrade time should not be a concern either, since the real outside interfaces (D-Bus, unit files, Debian configuration files) have always been stable (forward compatible) and will remain so. There will, most probably, be locked-in upgrades with udev from time to time, but it does not have any impact on the ability to upgrade systems. <-- snip --> Can you give a pointer to what guarantees systemd upstream makes regarding supporting older kernels? One example: Assume kdbus gets merged into the upstream kernel after the kernel that ships with jessie. Would it be guaranteed that the systemd in jessie+1 will still be able to work with the jessie kernel, or is there even the slightest risk that systemd upstream might at some point make kdbus a mandatory requirement? And with systemd absorbing functionality like module loading I could even imagine nightmare scenarios where additionally the jessie+1 kernel would only work with a jessie+1 systemd. Please clarify whether there is just a pointer to a statement from systemd upstream missing, or whether the statement "Compatibility at upgrade time should not be a concern either" is incorrect. Thanks in advance Adrian [1] https://wiki.debian.org/Debate/initsystem/systemd [2] https://wiki.debian.org/Debate/initsystem/upstart -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org