No I am fully aware that systemd targets Linux and OpenBSD is, well, not Linux. But seriously, what's the status of init in OpenBSD? Last time I used it (around 5.2 for some odd sparc servers that didn't support anything else apart from Solaris) it was still/etc/rc.d scripts, and no respawn if a service crashed etc.
If a Poettering-like asshole was detected anywhere near OpenBSD, they would be shot down like an aircraft flying over the White House without clearance.
For variable values of "improvements". Some people (usually ones with a lot of experience and insights) think that the makers of systemd do not understand how Unix works or how to do professional system administration and hence view systemd rightfully as a step backwards.
Unix is an evolving class of operating systems and they work the way we make them work. Sometimes we come up with new ideas that may or may not improve it. Almost no one agrees that Unix of the 90s was at perfection and that nothing would ever have to be changed again.
That there's no point in talking about "how Unix works" since Unix has never been consistent unless you're talking about some of the really old AT&T releases. Once there were multiple Unix vendors things started changing all the time. What we're seeing now in the Linux space is no different from what has always been the case.
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly. None of these new ideas have undergone any real testing other than shipping the distro when they compile. You're beta testing this bullshit.
by Anonymous Coward writes:
on Sunday October 18, 2015 @05:08PM (#50754851)
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly. None of these new ideas have undergone any real testing other than shipping the distro when they compile. You're beta testing this bullshit.
More accurately it's about tight versus loose coupling.
Under systemd, while there are many CLI commands, they are bound together and cannot be used independently. You can't really use journald, hostnamed, machined, timedated, etc., independently or replace them with something else that you've developed.
It's all very well to write a "better init", and maybe it has, but you're stuck with also running journald and can't put in rsyslog instead (only run in parallel). timedated may be good, and you want to use it on a SysV-based system... but you can't.
Does it have systemd? (Score:0)
No I am fully aware that systemd targets Linux and OpenBSD is, well, not Linux. But seriously, what's the status of init in OpenBSD? Last time I used it (around 5.2 for some odd sparc servers that didn't support anything else apart from Solaris) it was still /etc/rc.d scripts, and no respawn if a service crashed etc.
Re: (Score:1, Interesting)
No, it doesn't have systemd.
If a Poettering-like asshole was detected anywhere near OpenBSD, they would be shot down like an aircraft flying over the White House without clearance.
Re: (Score:-1)
Re: (Score:2, Insightful)
For variable values of "improvements". Some people (usually ones with a lot of experience and insights) think that the makers of systemd do not understand how Unix works or how to do professional system administration and hence view systemd rightfully as a step backwards.
Re: (Score:4, Insightful)
Re: (Score:1)
Your point?
Re: (Score:4, Informative)
Re: (Score:5, Insightful)
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly. None of these new ideas have undergone any real testing other than shipping the distro when they compile. You're beta testing this bullshit.
tight versus loose coupling (Score:1)
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly. None of these new ideas have undergone any real testing other than shipping the distro when they compile. You're beta testing this bullshit.
More accurately it's about tight versus loose coupling.
Under systemd, while there are many CLI commands, they are bound together and cannot be used independently. You can't really use journald, hostnamed, machined, timedated, etc., independently or replace them with something else that you've developed.
It's all very well to write a "better init", and maybe it has, but you're stuck with also running journald and can't put in rsyslog instead (only run in parallel). timedated may be good, and you want to use it on a SysV-based system... but you can't.
Re: (Score:0)
> More accurately it's about tight versus loose coupling.
Also separation of concerns [wikipedia.org].