On Fri, Jul 04, 2014 at 03:37:20AM -0700, Russ Allbery wrote: > Gerrit Pape <p...@dbnbgs.smarden.org> writes: > > I looked into latest policy, but did not find anything about systemd > > support. I'm surprised that this is now a release critical bug, and the > > package marked for removal. What's the justification? > > I'm very dubious about this being release-critical.
I think it is. The package will not work as expected without the inittab interface. > > This package hooks into /etc/inittab, does systemd not automatically > > manage services from inittab? > > Correct, systemd doesn't use inittab. > > > Isn't it systemd having release critical bug then? > > I don't think it's likely that systemd will support inittab. The > semantics of inittab are quite a bit inferior to what's available with > very little additional work using the native configuration format, and the > regular inittab jobs are provided by regularly-configured services. Yes, > that is a disruptive change for people who were using inittab to run other > things. Thanks Russ. This also applies to the runit package actually. Having my own init system since more than 10 years, I'm not that much in systemd. I looked at policy, but didn't find any instructions. I hereby ask for help to add systemd support to these packages. Important thing to know is: init scripts don't work out for this. The service management concept of daemontools and runit is, amongst other things, a process tree with guaranteed process state, including envrionment. init scripts don't provide that. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
