[wiki] [sites] Adding the systemd chronicles. || Christoph Lohmann

From: <git_AT_suckless.org>
Date: Fri, 31 Jul 2015 11:32:20 +0200

commit f9e6db73725348dfab29071ac5a052493271905e
Author: Christoph Lohmann <20h_AT_r-36.net>
Date: Fri Jul 31 11:31:59 2015 +0200

    Adding the systemd chronicles.

diff --git a/suckless.org/sucks.md b/suckless.org/sucks.md
deleted file mode 100644
index 359cd06..0000000
--- a/suckless.org/sucks.md
+++ /dev/null
_AT_@ -1,103 +0,0 @@
-Stuff that sucks
-================
-See the [philosophy](http://suckless.org/philosophy) page about what
-applies to this page.
-
-Libraries
----------
-These libraries are broken/considered harmful and should not be used if it's
-possible to avoid them. If you use them, consider looking for alternatives.
-
-* [glib][1] - implements C++ STL on top of C (because C++ sucks so much, let's
- reinvent it!), adding lots of useless data types for
- ["portability" and "readability" reasons][2].
- even worse, it is not possible to write robust applications using glib,
- since it [aborts in out-of-memory situations][8].
- glib usage is required to write gtk+ and gnome applications, but is also used
- when common functionality is needed (e.g. hashlists, base64 decoder, etc).
- it is not suited at all for static linking due to its huge size.
-
- Alternatives: [libmowgli][9], [libulz][10]
-
-* [GMP][3] - GNU's bignum/arbitrary precision library. Quite bloated, slow and
- [calls abort() on failed malloc][4]
-
- Alternatives: [libtommath][5], [TomsFastMath][6], [MPI][7]
-
-
-[1]: http://library.gnome.org/devel/glib/
-[2]: http://library.gnome.org/devel/glib/unstable/glib-Basic-Types.html (glib Basic Types)
-[3]: http://gmplib.org/ (The GNU Multiple Precision Arithmetic Library)
-[4]: http://gmplib.org:8000/gmp/file/14cd74efb9de/memory.c#l44 "GMP calls abort() on failed malloc()"
-[5]: http://libtom.org/?page=features&newsitems=5&whatfile=ltm
-[6]: http://libtom.org/?page=features&newsitems=5&whatfile=tfm
-[7]: http://spinning-yarns.org/michael/mpi/
-[8]: https://bugzilla.gnome.org/show_bug.cgi?id=674446
-[9]: https://github.com/atheme/libmowgli-2
-[10]: https://github.com/rofl0r/libulz
-
-Build Systems
--------------
-
-* [cmake][11] (written in C++) - so huge and bloated, compilation takes longer
- than compiling GCC (!).
- It's not even possible to create freestanding Makefiles, since the generated
- Makefiles call back into the cmake binary itself.
-
-* [waf][12] and [scons][13] (both written in Python) - waf code is dropped
- into the compilee's build tree, so it does not benefit from updated versions
- and bugfixes.
-
-As these build systems are often used to compile C programs, one has to set up a
-C++ compiler or Python interpreter respectively just in order to be able to build
-some C code.
-
-Alternatives: [mk][14], [gnu make][15]
-
-[11]: http://www.cmake.org/
-[12]: https://code.google.com/p/waf/
-[13]: http://www.scons.org/
-[14]: http://doc.cat-v.org/plan_9/4th_edition/papers/mk
-[15]: https://www.gnu.org/software/make/
-
-Programs
---------
-There are many broken X programs. Go bug the developers of these broken
-programs to fix them. Here are some of the main causes of this brokenness:
-
-* The program **assumes a specific window management model**, e.g.
- assumes you are using a WIMP-window manager like those
- found in KDE or Gnome. This assumption breaks the
- [ICCCM conventions][icccm].
-* The application uses a **fixed size** - this limitation does not fit
- into the world of tiling window managers very well, and can also be
- seen as breaking the ICCCM conventions, because a fixed sized window
- assumes a specific window management model as well (though the ICCCM
- does not forbid fixed-size windows). In any case, the ICCCM requests
- that clients accept any size the window manager proposes to them.
-* The program is based on strange **non-standard window manager
- hints** that only work properly with a window manager supporting these
- extensions - this simply breaks the ICCCM as well. E.g. trash icon
- programs.
-* The program does not conform to ICCCM due to some **missing or
- improperly set hints**.
-
-The following programs are broken (see [rocking stuff](/rocks) for saner alternatives):
-
-* [Firefox](http://www.mozilla.org/products/firefox) (doesn't set the TRANSIENT\_FOR
- hint correctly on its download dialog)
-* mplayer with GUI (assumes special window management model. It works without the GUI)
-* xine (assumes fixed size, doesn't set TRANSIENT\_FOR hint properly)
-
-If you still need some program which expects a floating WM, use it in
-floating mode.
-
-See also
---------
-
-The [list of harmful software](http://harmful.cat-v.org/software/) at [cat-v.org](http://cat-v.org).
-
-[aterm-ml-post]: http://lists.suckless.org/dev/1102/7141.html
-[st]: http://st.suckless.org/
-[uuterm]: http://etalabs.net/uuterm.html
-[icccm]: http://tronche.com/gui/x/icccm/
diff --git a/suckless.org/sucks/index.md b/suckless.org/sucks/index.md
new file mode 100644
index 0000000..359cd06
--- /dev/null
+++ b/suckless.org/sucks/index.md
_AT_@ -0,0 +1,103 @@
+Stuff that sucks
+================
+See the [philosophy](http://suckless.org/philosophy) page about what
+applies to this page.
+
+Libraries
+---------
+These libraries are broken/considered harmful and should not be used if it's
+possible to avoid them. If you use them, consider looking for alternatives.
+
+* [glib][1] - implements C++ STL on top of C (because C++ sucks so much, let's
+ reinvent it!), adding lots of useless data types for
+ ["portability" and "readability" reasons][2].
+ even worse, it is not possible to write robust applications using glib,
+ since it [aborts in out-of-memory situations][8].
+ glib usage is required to write gtk+ and gnome applications, but is also used
+ when common functionality is needed (e.g. hashlists, base64 decoder, etc).
+ it is not suited at all for static linking due to its huge size.
+
+ Alternatives: [libmowgli][9], [libulz][10]
+
+* [GMP][3] - GNU's bignum/arbitrary precision library. Quite bloated, slow and
+ [calls abort() on failed malloc][4]
+
+ Alternatives: [libtommath][5], [TomsFastMath][6], [MPI][7]
+
+
+[1]: http://library.gnome.org/devel/glib/
+[2]: http://library.gnome.org/devel/glib/unstable/glib-Basic-Types.html (glib Basic Types)
+[3]: http://gmplib.org/ (The GNU Multiple Precision Arithmetic Library)
+[4]: http://gmplib.org:8000/gmp/file/14cd74efb9de/memory.c#l44 "GMP calls abort() on failed malloc()"
+[5]: http://libtom.org/?page=features&newsitems=5&whatfile=ltm
+[6]: http://libtom.org/?page=features&newsitems=5&whatfile=tfm
+[7]: http://spinning-yarns.org/michael/mpi/
+[8]: https://bugzilla.gnome.org/show_bug.cgi?id=674446
+[9]: https://github.com/atheme/libmowgli-2
+[10]: https://github.com/rofl0r/libulz
+
+Build Systems
+-------------
+
+* [cmake][11] (written in C++) - so huge and bloated, compilation takes longer
+ than compiling GCC (!).
+ It's not even possible to create freestanding Makefiles, since the generated
+ Makefiles call back into the cmake binary itself.
+
+* [waf][12] and [scons][13] (both written in Python) - waf code is dropped
+ into the compilee's build tree, so it does not benefit from updated versions
+ and bugfixes.
+
+As these build systems are often used to compile C programs, one has to set up a
+C++ compiler or Python interpreter respectively just in order to be able to build
+some C code.
+
+Alternatives: [mk][14], [gnu make][15]
+
+[11]: http://www.cmake.org/
+[12]: https://code.google.com/p/waf/
+[13]: http://www.scons.org/
+[14]: http://doc.cat-v.org/plan_9/4th_edition/papers/mk
+[15]: https://www.gnu.org/software/make/
+
+Programs
+--------
+There are many broken X programs. Go bug the developers of these broken
+programs to fix them. Here are some of the main causes of this brokenness:
+
+* The program **assumes a specific window management model**, e.g.
+ assumes you are using a WIMP-window manager like those
+ found in KDE or Gnome. This assumption breaks the
+ [ICCCM conventions][icccm].
+* The application uses a **fixed size** - this limitation does not fit
+ into the world of tiling window managers very well, and can also be
+ seen as breaking the ICCCM conventions, because a fixed sized window
+ assumes a specific window management model as well (though the ICCCM
+ does not forbid fixed-size windows). In any case, the ICCCM requests
+ that clients accept any size the window manager proposes to them.
+* The program is based on strange **non-standard window manager
+ hints** that only work properly with a window manager supporting these
+ extensions - this simply breaks the ICCCM as well. E.g. trash icon
+ programs.
+* The program does not conform to ICCCM due to some **missing or
+ improperly set hints**.
+
+The following programs are broken (see [rocking stuff](/rocks) for saner alternatives):
+
+* [Firefox](http://www.mozilla.org/products/firefox) (doesn't set the TRANSIENT\_FOR
+ hint correctly on its download dialog)
+* mplayer with GUI (assumes special window management model. It works without the GUI)
+* xine (assumes fixed size, doesn't set TRANSIENT\_FOR hint properly)
+
+If you still need some program which expects a floating WM, use it in
+floating mode.
+
+See also
+--------
+
+The [list of harmful software](http://harmful.cat-v.org/software/) at [cat-v.org](http://cat-v.org).
+
+[aterm-ml-post]: http://lists.suckless.org/dev/1102/7141.html
+[st]: http://st.suckless.org/
+[uuterm]: http://etalabs.net/uuterm.html
+[icccm]: http://tronche.com/gui/x/icccm/
diff --git a/suckless.org/sucks/systemd.md b/suckless.org/sucks/systemd.md
new file mode 100644
index 0000000..41b6b20
--- /dev/null
+++ b/suckless.org/sucks/systemd.md
_AT_@ -0,0 +1,226 @@
+Systemd is the best example of Suck.
+====================================
+There is a menace which is spreading like a disease throughout the Linux
+world, it is called [systemd](https://github.com/systemd/systemd).
+
+Short Historical Summary
+------------------------
+Systemd is a replacement for the standard init command, which normally runs
+as process id 1 on initialisation of a UNIX bootup. There has been a movement,
+especially around the [Red Hat](http://www.redhat.com)-related developers to
+copy [Microsoft Windows](http://www.microsoft.com/) and all of its features.
+Now this interpretation of how a userspace should look like is implemented and
+was introduced with big criticism and change in the Open Source world into
+many distributions. The [debacle in Debian](https://wiki.debian.org/Debate/initsystem/systemd)
+is the best example in how to not introduce such a changing technology into a
+distribution.
+
+What PID 1 Should Do
+------------------------
+On bootup does the kernel execute some given binary in its known namespace. To
+see what are the only tasks the application running as pid 1 has to do, see
+[sinit](http://git.suckless.org/sinit/). Just wait for child process to reap
+and run some other init scripts.
+
+The Systemd Chronicles
+----------------------
+Now follows a list of unsorted links to the Systemd changelog with comments.
+The list is exceeding the life-time of a philosopher to discuss all
+implications on the sanity of a system design. That's why the comments are
+kept short.
+
+Part 1
+------
+(If you are adding more parts, link to the right revision and not just the
+plain file.)
+[NEWS revision 3f80af378331748e1373d4c189a8e20cddb735c9](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c)
+
+* [logind should wait](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n2089)
+ * Systemd was introduced to decrease the boot up time. Now that they
+ do not understand all implications and dependencies, let us add some
+ artifical time we found out might work for the developers
+ laptops. More on this small world hypothesis of the systemd
+ devleopers below.
+* [scree brightness](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1852)
+ * Screen brightness is something that should crash your boot up when
+ it is not working.
+* [hostnamed](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1763)
+ * There really should be a process running which exposes the content
+ of a file. Complex is without cost.
+* [seqnum removed](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1742)
+ * The sequential ordering of requests was one reason why udevd was
+ introduced. Now remove it, because the developer laptops do not have
+ a problem anymore.
+* [floppy group removed](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1703)
+ * Because we know what is right to know about groups. This is just one
+ example of the mass of group name dependencies systemd is adding.
+ See sinit for how to not need such dependencies.
+* [sysv removed](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1651)
+ * We have won. Now remove all remains of the our defeated enemy as
+ fast as we can. As said in the beginning of the systemd crusade
+ against the UNIX infidels: »You can patch it out.« It is no more
+ there.
+* [abnormal processes](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1627)
+ * Now systemd is getting deep into philosophy. What is »abnormal«?
+ Well, let us just define it. There is no technical merit to accept
+ this.
+* [systemd-resolved](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1578)
+ * Every configuration file needs its own process and service.
+ * Symlinks are a good way to solve all world problems.
+* [new is better](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1571)
+ * The systemd development process is flawed by always assuming »new is
+ best«.
+ * Network configuration should be in my init process.
+* [remote pid 1](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1500)
+ * »Everything will end up having a remote API.« I wonder when systemd
+ will understand MIME and e-mail.
+* [init does man](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1465)
+ * My init process is to big, it needs its own file hierarchy and an
+ abstraction layer to find paths.
+* [factory reset](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1401)
+ * Welcome to the Windows OEM world: Factory reset for Linux! Of course
+ it is in your init process.
+* [system runs runs](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1397)
+ * Exactly. The predisposition of being able to call such a complex
+ command does not imply the running system. Let's check it.
+* [clean up directories](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1306)
+ * There is another monster, in system which does tmp file handling.
+ There are just some cases before it was introduced to have to clean up
+ a directory in the file tree. Now there are hundreds. And easily
+ another case can be added! Of course your init process does that.
+* [firstboot](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1259)
+ * »Interactive queries« pulls in many dependencies. Let us have it in
+ every installation out there on by default. Of course in pid 1.
+* [journald](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1234)
+ * This is a bit longer. Because the systemd developers were not able
+ to contribute to any syslog daemon they had to write their own with
+ some binary format so the principle of being able to read your log
+ files after a critical crash was violated. To be nice invaders the old
+ systems were allowed to order the system log through the specified
+ mechanism. Now that they implemented our specifics, turn off the
+ neutral syslog delivery. You will see this pattern of »now that we
+ conquered your culture, obey« more often in systemd.
+* [systemd-terminal](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1224)
+ * Why does the kernel have tty handling? So in serious situations you
+ will be able to debug it over the last standing PIN on your
+ motherboard. Let us remove this. Run it in pid 1.
+* [networkd is your oppressor](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1216)
+ * Premature optimisation of IP configurations always leads to misery.
+* [We do not understand broadcast](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1211)
+ * As systemd is growing in its complexity and all stuff it is touching
+ of course somewhen the addition of hacks with new implications is
+ increasing.
+* [Timezone hack](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1193)
+ * Systemd is too complex for such a simple transaction with the
+ kernel. Do not inform the kernel and add another assumption which is
+ only documented in the changelog.
+* [the web is a session](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1168)
+ * For the future generations: In 2015 nearly everyone was trying to
+ connect all you do to the web. In the UNIX model it is just a client
+ which should be simple and integrate into the system. Systemd is
+ doing it the other way around and does integrate itself into the
+ web.
+ * The discussion about why my pid 1 is handling sessions is discussed
+ in other points.
+* [pid 1 does DNS](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1128)
+ * This change adds another open door to your pid 1, adds caches, new
+ APIs and of course it will never fail and break systemd on your
+ initial boot.
+ * They are planning (2015-07) to add multicast DNS to your pid 1.
+ Multicast DNS implies an enforced timout to know if someone answered.
+ Systemd was about speed, you know. Look at avahi in how to ruin this
+ concept for Linux. It has the same developer flaws as systemd: Too
+ many forced dependencies, you need to implement its API and when it is
+ taking over you are doomed.
+* [policykit](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1113)
+ * There is a bus inside your pid 1 and if it crashes you are flawed.
+ Exactly, there are a thousand more cases of errors that could occur
+ and make your system unbootable. Instead of using a separation of
+ functions, add everything to a big bus.
+ * Of course when you are using a misdesign like dbus you need to add
+ interactions over the bus to add features you forgot in the initial
+ design. Now let us have our pid 1 have to query for the permission
+ to boot.
+ * »Interactive authentication« will produce you a graphical input form
+ on your serial line.
+* [Calendar](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1044)
+ * As you see, your pid 1 should handle your calendars and cron jobs
+ too.
+* [utmp should go](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n994)
+ * We have taken over your culture, now die! Another flaw in the
+ systemd small world theory: When something is getting optional it
+ will be removed.
+* [password agent](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n964)
+ * »Interactive authentication«
+* [udev timeout](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n944)
+ * Instead of patching the kernel to add a simple solution, add a hack.
+ Only the systemd developers tell you when it is allowed to wait or
+ sleep in userspace. The rest obey our orders!
+* [systemd-pm](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n924)
+ * Power management is required on boot up.
+* [user systemd units](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n898)
+ * What can go wrong when you are adding more paths that are read,
+ parsed and executed?
+* [hack the reload](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n888)
+ * First systemd was adding »better features« like socket activation to
+ make developers use their mechanism for daemons. They hit the
+ proprietary wall of disgust with this changelog entry. Systemd is
+ too big and you will lose your face if you change the misdesign. Now
+ add another hack because we can do it. Big empires fall too and
+ sadly have too many casualties when they are falling. :(
+* [X11 in systemd](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n783)
+ * Of course graphics were missing in pid 1.
+* [complexity is purity](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n738)
+ * You will of course need PPPoE when you do parallel bootup. Every
+ 1000 lines of code add one critical bug you never find.
+* [gateway hostname](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n700)
+ * We rule the world so we are above IETF and IANA. Now add our own
+ hostnames that of course won't add another assumption.
+* [no editor in systemd](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n689)
+ * This one is a setback. Why is there no default editor in systemd in
+ case of factory reset?
+* [7x ctrl + alt + del](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n610)
+ * In systemd you press seven times Ctrl+Alt+Del to trigger reboot.
+* [privacy policy](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n594)
+ * For the next generations: In 2015 privacy was a big issue because of
+ the mentioned hard-wiring between the web and software. Now as seen
+ does every commit which adds some preparation in systemd add an
+ interpretation on what will be seen as a major feature. If you
+ handle privacy you will have some features depending on that user
+ decision and of course the factory reset default value.
+ * Why didn't they use XML for /etc/os-release?
+* [fds cache](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n502)
+ * We have talked about misdesign, too-big-to-fail and world
+ domination. This is the next example of a hack that is prone to
+ fail.
+* [mount -rf](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n380)
+ * This is umount for dummies. Just done one thing – right.
+* [libudev will be orphaned](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n291)
+ * With the advent of udevd was there a compatibility to its complexity
+ called libudev. X11 uses it to query the changing devices. And of
+ course make it a non-independent API in systemd. Why? You can guess
+ why: Defeating the infidels.
+* [fsck indirections](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n281)
+ * When there was syslog fsck did output errors to your display as
+ easy as possible. Now add a hack to have this possible again.
+* [systemd-importd](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n236)
+ * This is pure evil. Your pid 1 is now able to import complete system
+ images over the network and show them to you as your running system.
+ There is nothing that can go wrong.
+* [CGI for systemd](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n166)
+ * The web thing has been discussed before.
+* [kdbus](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n57)
+ * As of 2015-07-31 kdbus is not in the mainline Linux kernel. Systemd
+ made kdbus non-optional in its release. This is the best example how
+ systemd is forcing you into decisions. Of course if your a mindless
+ bureaucrat it helps you to keep your job.
+* [readahead removed](http://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n950)
+ * The first thing swallowed in on Fedora was readahead. Now that (of
+ course!) everyone is using an SSD (at least the developers of
+ systemd do that) it can be removed. Why was it there? Could it be
+ popped out into userspace to have the user decide about that it
+ should be still done? There's no time for that, we are implementing
+ new features.
+
+-- Führerbunker, 2015-07-31
+
Received on Fri Jul 31 2015 - 11:32:20 CEST