about summary refs log tree commit diff
diff options
context:
space:
mode:
authorVincent Ambo <vincent@kivra.com>2016-01-21T14·02+0100
committerVincent Ambo <vincent@kivra.com>2016-01-21T14·02+0100
commit487e936f3e9d739d300eb31855c9231f8768205b (patch)
treedea5641927af404beac3e6ddb6b25dafe9242541
parent38f1823df20c40f863d3a86aaea972cee811fb2f (diff)
Add slides for criticism & adoption
-rw-r--r--slides.pdfpc10
-rw-r--r--slides.tex28
-rw-r--r--systemdcomponents.pngbin0 -> 233143 bytes
3 files changed, 38 insertions, 0 deletions
diff --git a/slides.pdfpc b/slides.pdfpc
index 971f40eee5..1e20478f77 100644
--- a/slides.pdfpc
+++ b/slides.pdfpc
@@ -67,3 +67,13 @@ systemd-analyze is used for figuring out performance issues, for example by anal
 systemd-cgtop is like top, but not on a process level - it's on a cgroup/slice level, shows combined usage of cgroups
 systemd-cgls lists contents of systemd's cgroups to see which services are in what group
 there also exist a bunch of others that we'll skip for now
+### 13
+### 14
+### 15
+Systemd criticism comes from many directions and usually focuses on a few points
+feature-creep: systemd is absorbing a lot of different services
+### 16
+explain diagram a bit
+### 17
+opaque: as a result, systemd has a lot more internal complexity that people can't easily wrap your mind around. However I argue that unless you're using something like suckless' sinit with your own scripts, you probably have no idea what your init does today anyways
+unstable: this was definitely true even in the first stable release, with the binary log format getting corrupted for example. I haven't personally experienced any trouble with it recently though.
diff --git a/slides.tex b/slides.tex
index 4d5447b6e5..e18c9496cc 100644
--- a/slides.tex
+++ b/slides.tex
@@ -127,6 +127,34 @@
 
 \section{Controversies}
 
+\begin{frame}{Systemd criticism}
+  Systemd has been heavily criticised, usually focusing around a few points:
+  \begin{itemize}
+  \item Feature-creep: Systemd absorbs more and more other services
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Systemd criticism}
+  \includegraphics[keepaspectratio=true,width=\textwidth]{systemdcomponents.png}
+\end{frame}
+
+\begin{frame}{Systemd criticism}
+  Systemd has been heavily criticised, usually focusing around a few points:
+  \begin{itemize}
+  \item Feature-creep: Systemd absorbs more and more other services
+  \item Opaque: systemd's inner workings are harder to understand than old \texttt{init}
+  \item Unstable: development is quick and breakage happens
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Systemd adoption}
+  Systemd was initially adopted by RedHat (and related distributions).
+
+  It spread quickly to others, for example ArchLinux.
+
+  Debian and Ubuntu were the last major players who decided to adopt it, but not without drama.
+\end{frame}
+
 \section{Questions?}
 
 \end{document}
diff --git a/systemdcomponents.png b/systemdcomponents.png
new file mode 100644
index 0000000000..a22c762f7e
--- /dev/null
+++ b/systemdcomponents.png
Binary files differ