about summary refs log tree commit diff
path: root/slides.pdfpc
diff options
context:
space:
mode:
authorVincent Ambo <vincent@kivra.com>2016-01-21T14·04+0100
committerVincent Ambo <vincent@kivra.com>2016-01-21T14·04+0100
commit8e06fe4d927d17555acea81b141426464c1b58f4 (patch)
tree1985332adb3a7701f2788cfdb4eb071c3f23867a /slides.pdfpc
parent487e936f3e9d739d300eb31855c9231f8768205b (diff)
Add notes for adoption slide
Diffstat (limited to 'slides.pdfpc')
-rw-r--r--slides.pdfpc6
1 files changed, 6 insertions, 0 deletions
diff --git a/slides.pdfpc b/slides.pdfpc
index 1e20478f77ad..35fa8309e1ae 100644
--- a/slides.pdfpc
+++ b/slides.pdfpc
@@ -77,3 +77,9 @@ 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.
+Another thing is that services start depending on systemd when they shouldn't, a problem for the BSD world (who cares (hey christoph!))
+### 18
+Despite criticism, systemd was adopted rapidly by large portions of the Linux
+Initially in RedHat, because Poettering and co work there and it was clear from the beginning that it would be there
+ArchLinux (which I'm using) and a few others followed suit quite quickly
+Eventually, the big Debian init system discussion - after a lot of flaming - led to Debian adopting it as well, which had a ripple effect for related distros such as Ubuntu which abandoned upstart for it.