On Wed, 21.01.15 11:08, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hey Jóhann, > > "Jóhann B. Guðmundsson" [2015-01-21 9:59 +0000]: > > Seems like a corner case as administrator should fix himself by not backing > > up files in the /etc/init.d directory so arguably this broken behaviour is > > expect. > > With SysV init this isn't "broken" at all. As long as you don't > actually enable the backup files in rcN.d/, this is perfectly valid. > The effect is that systems with such backup files work fine under SysV > init and even under systemd up to 218, but will fail to boot under > systemd 219 onwards (i. e. with current master). I call this a > regression. > > > That said at one point or another we need to drop legacy sysv > > initscript support and have downstream the generator themselves if > > they intend on supporting legacy sysv initscripts. > > If upstream wants to drop it at some point that's their prerogative of > course. I'd advise against it though, as LSB compliant systems need to > support SysV init scripts, it's still the lowest common denoniator, > and tons of third-party software still ship with init.d scripts. I. e. > it's not enough to port the distro packages.
Just to clarify: I have zero intention to drop LSB script support any time soon. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel