Broken by design: systemd

Re:Broken by design: systemd by dalias on Sunday February 09, 2014 @07:32PM (#7208284)

Functionality is not being moved out of the kernel and into userspace. It's being moved out of legacy freedesktop.org components (hald, ConsoleKit, PolicyKit, etc.) and into PID 1. Where should it be moved to? /dev/null.

[ Parent | on HN ]

Re:Broken by design: systemd by nona on Sunday February 09, 2014 @07:59PM (#7208402)

I think you need to look a bit more closely at what's actually going into PID 1. See for example: http://people.debian.org/~stapelberg/docs/systemd-dependenci...

I don't see any logind/hostnamed/journald or any of that stuff in PID1.

[ Parent | on HN ]

Re:Broken by design: systemd by Jasper_ on Sunday February 09, 2014 @09:35PM (#7208754)

hald has been dead forever.

PolicyKit is not being moved into systemd, nor is it getting systemd integration?

How do you want to replace ConsoleKit/logind? What should handle session management?

[ Parent | on HN ]

Re:Broken by design: systemd by teacup50 on Sunday February 09, 2014 @11:43PM (#7209185)

Something other than your init system. Not even Apple's launchd has the kinds of idiotic layering violations that systemd is full of.

[ Parent | on HN ]

Re:Broken by design: systemd by Jasper_ on Monday February 10, 2014 @01:22AM (#7209464)

Well, you'll be happy to learn that logind is a separate process entirely.

[ Parent | on HN ]

Re:Broken by design: systemd by teacup50 on Monday February 10, 2014 @09:12AM (#7211138)

Layering violations don't only happen within the process level.

[ Parent | on HN ]