<!-- saved from url=(0055)http://0pointer.de/blog/projects/the-biggest-myths.html -->
<body>
<h1>レナート PID EINS! ﻟﻴﻨﺎﺭﺕ</h1>
<p class="date"> </p>
<h2>Sat, 26 Jan 2013</h2>
<h3><a name="the-biggest-myths">The Biggest Myths</a></h3>
<div class="blosxomStory">
<p>Since we first proposed <a href="http://www.freedesktop.org/wiki/Software/systemd">systemd</a>
for inclusion in the distributions it has been frequently discussed in
many forums, mailing lists and conferences. In these discussions one
can often hear certain myths about systemd, that are repeated over and
over again, but certainly don't gain any truth by constant
repetition. Let's take the time to debunk a few of them:</p>
<ol>
<li><p><b>Myth: systemd is monolithic.</b></p>
<p>If you build systemd with all configuration options enabled you
will build 69 individual binaries. These binaries all serve different
tasks, and are neatly separated for a number of reasons. For example,
we designed systemd with security in mind, hence most daemons run at
minimal privileges (using kernel capabilities, for example) and are
responsible for very specific tasks only, to minimize their security
surface and impact. Also, systemd parallelizes the boot more than any
prior solution. This parallization happens by running more processes
in parallel. Thus it is essential that systemd is nicely split up into
many binaries and thus processes. In fact, many of these
binaries<sup>[1]</sup> are separated out so nicely, that they are very
useful outside of systemd, too.</p>
<p>A package involving 69 individual binaries can hardly be called
<i>monolithic</i>. What is different from prior solutions however,
is that we ship more components in a single tarball, and maintain them
upstream in a single repository with a unified release cycle.</p></li>
<li><p><b>Myth: systemd is about speed.</b></p>
<p>Yes, systemd is fast (<a href="https://plus.google.com/108087225644395745666/posts/LyPQgKdntgA">A
pretty complete...