mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add slides for criticism & adoption

Browse source
This commit is contained in:
Vincent Ambo 2016-01-21 15:02:01 +01:00
parent 38f1823df2
commit 487e936f3e
No known key found for this signature in database
GPG key ID: 66F505681DB8F43B
3 changed files with 38 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
slides.pdfpc
View file

@ -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-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 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 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.

28
slides.tex
View file

@ -127,6 +127,34 @@
\section{Controversies} \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?} \section{Questions?}
\end{document} \end{document}

BIN
systemdcomponents.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 228 KiB