[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Tentative summary of the amendments

On 24 October 2014 17:27, Josh Triplett <josh@joshtriplett.org> wrote:
>> In any case, this is uncharted territory, because (to my knowledge)
>> until systemd started integrating system level services into init
>> system itself, applications never depended on particular APIs of init
>> systems.
> Sure they did.  Applications depended on daemons which depended
> specifically on sysvinit functionality: /etc/init.d, /etc/rc?.d, LSB
> init script metadata, dependencies on specific scripts and their
> functionality.  It wasn't much, but it was something.

Did a deamon parse /etc/init.d/... files on startup to figure
something out? I don't think so. Those files in /etc are configuration
for sysvinit and not an API.

Sysvinit calls services, services do *not* call sysvinit. The
communication is only one way.

AFAIK the only API that sysvinit actually has is tellinit. And even
that is kind of optional. That makes it very easy to implement new
init systems. Even in-house custom init systems for specific reasons.

Best regards,
    Aigars Mahinovs        mailto:aigarius@debian.org
 | .''`.    Debian GNU/Linux (http://www.debian.org)            |
 | : :' :   Latvian Open Source Assoc. (http://www.laka.lv)     |
 | `. `'    Linux Administration and Free Software Consulting   |
 |   `-                                 (http://www.aiteki.com) |

Reply to: