|
|
Subscribe / Log in / New account

How Debian managed the systemd transition

How Debian managed the systemd transition

Posted Sep 27, 2015 21:50 UTC (Sun) by sbergman27 (guest, #10767)
Parent article: How Debian managed the systemd transition

Based upon all my bad experiences with PulseAudio... I admit I was skeptical of systemd. But I have to admit, it's working well on my Debian 8 desktop. The administration tools are well designed. And after years of hearing about other people's fast boot times... which I'd decided I wasn't sure I believed... I was shocked when after the upgrade I was able to go from Grub screen to a fully operational system, logged in, and with Chrome up and on the Google page, in (drum-roll please) 5.7 seconds. And speed was not even the main focus of the systemd design. Just a side effect. Regarding the socket-based dependencies, I think it's clear that Poettering was right and Remnant was wrong. They really are are good as they look on paper.


to post comments

How Debian managed the systemd transition

Posted Sep 28, 2015 17:30 UTC (Mon) by flussence (guest, #85566) [Link]

That's an impressive number! I doubt systemd would do much for me though; my browser already takes longer from exec to window draw than the rest of the boot process...

How Debian managed the systemd transition

Posted Sep 28, 2015 18:44 UTC (Mon) by bronson (subscriber, #4806) [Link]

Just another data point: I've only tried systemd on the server but I can't recommend it highly enough. I replaced a few different monit/god/custom setups started by all sorts of different distro-specific init.d files with a single systemd unit file. It worked first try and it's been stone stable ever since (so, no idea how helpful the support channels are since I haven't had a chance to use them).

Still waiting for the other shoe to drop.. but it's been excellent so far.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds