On Fri, 2019-11-15 at 16:05 +0100, Ansgar wrote: > 9.11 states: > > +--- > > Alternative init implementations must support running SysV init > > scripts as described at System run levels and init.d scripts for > > compatibility. > +--- > > Does this include override mechanisms for important metadata such as > dependency information? (/etc/insserv/override, > /usr/share/insserv/override)
Oh, and the obvious part: Does this include dependency information from LSB headers? Does this include the requirement that sysvinit scripts can depend on "native" services by the alternative init and vica versa? (upstart didn't support this which was one of the reasons it never saw many native units AFAIU as one would have to start with converting *all* leaf scripts, breaking local services.) Do alternative init systems have to support enabling/disabling sysvinit compat services via symlinks in /etc/rcn.d? If not, are there any requirements what has to happen when switching init systems (i.e. which services are enabled/disabled after switching)? > Does this include understanding insserv system facilities? > > (The init.d script section in Policy referred to is too old to know > about any of these features.) There are also more follow-up questions like: Is switching to alternative init systems supported in a running system? Or might one have to fiddle with a rescue system? Are init scripts w/o dependency information still supported as that is what Policy documents? (I guess "no", but some people want to enforce more strictly which features not documented in Policy are allowed to be used or enforce more strictly (possibly very outdated) Policy requirements on init scripts or when these must be included.) Ansgar
