os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add entry mentioning init and service management projects, from Mark Heily

Browse source
This commit is contained in:
Benjamin Kaduk 2016-01-18 22:00:24 +00:00
parent 09af0f24ab
commit 04efebac66
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=48057
1 changed files with 79 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

79
en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml
View file

@ -3741,4 +3741,83 @@
</task> </task>
</help> </help>
</project> </project>
<project cat='misc'>
<title>System Initialization and Service Management</title>
<contact>
<person>
<name>
<given>Mark</given>
<common>Heily</common>
</name>
<email>mark@heily.com</email>
</person>
<person>
<name>
<given>Jonathan</given>
<common>de Boyne Pollard</common>
</name>
<email>J.deBoynePollard-newsgroups@NTLWorld.COM</email>
</person>
<person>
<name>
<given>Jordan</given>
<common>Hubbard</common>
</name>
<email>jkh@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.daemonspawn.org/2016/01/a-comparison-of-alternatives-to-init8.html">A Comparison of <tt>init(8)</tt> and <tt>rc(8)</tt> Replacements</url>
</links>
<body>
<p>There are three active projects to provide an alternative
to the traditional <tt>init(8)</tt> and <tt>rc(8)</tt> subsystems
that manage the boot process and system services. There are a
number of reasons driving the desire for change, including:</p>
<ul>
<li>Faster boot times, made possible by launching services
in parallel</li>
<li>Greater reliability, by ensuring that services are
automatically restarted if they terminate unexpectedly</li>
<li>Simplified dependency management, using socket
activation and similar techniques</li>
<li>The ability to launch services &quot;on demand&quot;,
and have them self-terminate when idle</li>
<li>Improved security, by removing the need to start common
daemons as the root user</li>
</ul>
<p> Two of the projects, <tt>launchd</tt> and
<tt>relaunchd</tt>, are based on the <tt>launchd(8)</tt> API
introduced by Apple in Mac OS X. The NextBSD project has ported
the original Apple source code by writing a Mach compatibility
layer that allows <tt>launchd</tt> to run on &os;. The
<tt>relaunchd</tt> project started from scratch with the goal of
creating a more modular, lightweight, and portable implementation
of the <tt>launchd</tt> API. The third project, <tt>nosh</tt>, is
a unique creation that borrows concepts from <tt>launchd</tt>,
<tt>systemd</tt>, and several other Unix operating systems.</p>
<p>While the &os; Project has not made a decision to replace
the current <tt>init(8)</tt> and <tt>rc(8)</tt> subsystems, the
existence and active development of alternatives will continue to
drive innovation in this space.</p>
<p>Jordan Hubbard is the contact point for the NextBSD
<tt>launchd</tt>, Jonathan de Boyne Pollard is the contact point
for <tt>nosh</tt>, and Mark Heily is the contact point for
<tt>relaunchd</tt>.</p>
</body>
</project>
</report> </report>