Chris's Wiki :: blog/unix/InitSystemsBootingSimple Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/InitSystemsBootingSimple?atomcommentsDWiki2022-02-20T20:20:31ZRecent comments in Chris's Wiki :: blog/unix/InitSystemsBootingSimple.By Walex on /blog/unix/InitSystemsBootingSimpletag:CSpace:blog/unix/InitSystemsBootingSimple:15fa3eb82d020e60f231dff20b09e319bf97592eWalex<div class="wikitext"><p>«<em>no one even thought about having the init system involved in restarting daemons after boot or starting new ones.</em>»</p>
<p>'man 5 inittab'
<a href="https://manpages.debian.org/buster/sysvinit-core/inittab.5.en.html">https://manpages.debian.org/buster/sysvinit-core/inittab.5.en.html</a></p>
<p>«<em>We have since discovered that this is a mistake</em>»</p>
<p>But still 'init' does not have to be the process or service manager, and system software does not have to depend on the particular type of process or service manager. It is just how things have happened, and it would be easy to fix.</p>
<p>«<em>init systems evolved over time to also encompass the role of service manager (managing long running services aka daemons)</em>»</p>
<p>Oh please! The difference between process supervisors and service managers is really huge, and current process/daemon supervisors are not service managers, also because some of their authors have simply chosen to crassly ignore defining a service state model, and deliberately confuse process state with service state as a shortcut to fool the gullible.</p>
<p><a href="http://www.sabi.co.uk/blog/21-one.html?210416#210416">http://www.sabi.co.uk/blog/21-one.html?210416#210416</a></p>
</div>2022-02-20T20:20:31ZBy vnm on /blog/unix/InitSystemsBootingSimpletag:CSpace:blog/unix/InitSystemsBootingSimple:b57b74056b70f338870718336c61cbc0d31e6d7avnmhttps://venam.nixers.net/<div class="wikitext"><p>I think init systems evolved over time to also encompass the role of service manager (managing long running services aka daemons). A service manager runs better as PID1 for multiple reasons, and the notion of booting inherently implies that some services should be started too. The first paragraph of the description in the manpage for SYSTEMD(1) does a fairly good job at explaining this idea.</p>
<blockquote><p>systemd is a system and service manager for Linux operating systems. When run as
first process on boot (as PID 1), it acts as init system that brings up and
maintains userspace services. Separate instances are started for logged-in users
to start their services.</p>
</blockquote>
</div>2022-02-20T07:58:15Z