| |||||||||||||
Poettering: The Biggest MythsPoettering: The Biggest MythsPosted Jan 31, 2013 18:59 UTC (Thu) by HelloWorld (guest, #56129)In reply to: Poettering: The Biggest Myths by sorpigal Parent article: Poettering: The Biggest Myths
Could you please be more specific? First of all, what does "in systemd" mean to you, the code in PID1 or all of the code in the systemd project? What is it that doesn't need to be done in systemd? What would specifically be gained by not doing so, and, most importantly, what are the drawbacks?
I think that many people see the advantages of keeping things separate, such as the possibility to replace parts, but fail to see the disadvantages, such as increased complexity.
(Log in to post comments)
Poettering: The Biggest Myths Posted Jan 31, 2013 21:49 UTC (Thu) by raven667 (subscriber, #5198) [Link]
I don't know what it means to sorpigal but I would think there is a continuum between the core of systemd in PID 1 and the ancillary tools such as udev, dbus, journal and logind and the rest, most of which don't run as daemons and are CLI utilities for managing things.
|
|||||||||||||