Re:Without Systemd
by blueflow on Friday May 08, 2015 @10:41PM
(#9515241)
Something like systemd except being ONLY an init system would be really great.
[ Parent
| on HN ]
This looks surprisingly tempting. I agree with a lot of the ideas behind systemd, but at the rate it is growing, I'm going to type this in systemd-firefox in systemd-xmonad in six months. How stable is it in practice?
I can't see why most people would want that, with the exception of replacing journald. Why strip out device init, or even timers? Swap init is less useful, but I don't see the harm.
What is it that makes uselessd attractive? And why do you consider systemd to be bloated?
I like my init system to be an init system. However, the scope of systemd seems to expand monthly. I mean, you get an ntp client, a dhcp client, a logging system, and they apparently want to expand into containerized applications? I'd rather have a project with a smaller, well-defined scope.
You can turn these services off :-)
I know, but I still don't think they belong under the same umbrella.
That's just not their plan. They want to modernize and standardize (to reduce fragmentation) the whole userspace. Replacing init is a big, but far from the only part of the process.
I challenge you to show me what part of systemd isn't directly related to inititialization of services.
Maybe the parameters and interface will simplify over time. Patterns emerge with use.
Yeah, that doesn't answer my question. What isn't necessary?
I don't know all of systemd but :
- journal
- networkd
- console
journald, logind. chrooting (nspawn). tty-ask-password-agent.
nspawn inits. journald - fair point. logind inits. systemd-tty-ask-password-agent is a password agent that handles password requests of the system, for example for hard disk encryption passwords or SSL certificate passwords that need to be queried at boot-time or during runtime.