9 ms·
I see a lot of hate about systems and I used to loathe it too. Then I took a course on systemd specifically and it opened my eyes, and now I'm quite fond about
by znpy 7y ago
I see a lot of hate about systems and I used to loathe it too.
Then I took a course on systemd specifically and it opened my eyes, and now I'm quite fond about it.
Systemd actually does ONE thing and does it well: it manages the system. It's the missing layer between kernel space and user space. It has quirks and bugs like all software, but I think it works very well, all things considered.
To those who say that it's complex and does a lot of things: it's complex because it does a complex work.
- znpy 7y agoRegarding knoppix abandoning it... Meh. Knoppix is a live system, so all of the things systemd was designed for don't apply. I guess it can make sense for their knoppix's use case.
- craigsmansion 7y agoKnoppix is very installable and usable as a main operating system. Knoppix claim to fame is automatic configuration. If your Xorg or sound was giving you grief after a fresh install, you'd live boot Knoppix and copy the configuration files back to your installation. From this p.o.v. it makes sense for Knoppix' use case, because, as stated by Klaus Knopper: "This bypasses systemd's interference with many system components and reduces the complexity of the overall system."
- Kwpolska 7y ago> Knoppix claim to fame is automatic configuration. If your Xorg or sound was giving you grief after a fresh install, you'd live boot Knoppix and copy the configuration files back to your installation. Is it really so? I would expect all distributions to have stolen that feature by now. Xorg works out of the box basically everywhere. I've had a glitch with a microphone on a 3-pin jack on a Ubuntu system, and I doubt Knoppix would have known that a modprobe config change was needed.
- rwmj 7y agosystemd is a perfectly fine init system. The problem is that it comes bundled with a whole bunch of other tools for handling networks, cron, ntp, etc which really ought to be separate projects. By bundling them with the successful init system they're not exposed to the usual Darwinian selection processes that shake out the best free software.
- nickserv 7y agoThey're separate binaries, and can be easily unbundled. That they're part of the same project is actually a win for me, it helps to make the various components work well together. Also there is a common thread or philosophy in how things are built, making learning easier. In fact "the system is a single project" approach reminds me of the BSDs, which is arguably better than Linux as far as usability and security is concerned.
- pdkl95 7y ago> They're separate binaries https://news.ycombinator.com/item?id=19024256 https://news.ycombinator.com/item?id=19024256
- nickik 7y agoWhen you design a library you have to design a way to interact with it. Complaining about systemd because of that is basically saying 'I don't like the api you provide'. People who hate systemd want traditional C API, systemd wants message passing. If you don't like some of binaries, you can remove them and make your own package. If you don't like a particular implementation you can write your own subsystem that uses the same API (as many projects have done). Basically its just people complaining that it does work exactly as they want, when in reality message passing is the exact right way to make system like that.
- labawi 7y agoUnification wouldn't be a such an issue, if it was done with forethought, design and consistency, like BSDs tend to have.
- qubex 7y agoI concur with your characterisation of systemd as “doing one thing, and doing it well”. Those who seem to malign it most are those who are, for historical reasons, profoundly conversant with the myriad daemons, configurations, and init systems (generally) of “old UNIX/Linux”. They have a point and a genuine axe to grind, I’ll concede, but systemd is an enormous simplifier for those who are recent to the scene: learn systemd, and you’ve learnt how to manage (most) of your system at a very low level.
- goatinaboat 7y agoSystemd is Red Hat’s version of the old “embrace, extend, extinguish” playbook.
- qubex 7y agoNo it isn’t. Firstly: they weren’t the originators of systemd, they simply hired the guy who first developed it to continue developing it. Secondly: it: being open source and GPL, anybody can use it or fork it and not be due anything to Red Hat. Thirdly, it isn’t extinguishing anything as a business strategy; it’s just out-competing alternatives in the “mindshare” arena.
- elygre 7y agoWithout having much opinion on systemd, hiring the developer sounds very much like “embrace”. Continuing developing sounds like “extend”.
- majewsky 7y agoBy that logic, every company that funds open source development is eeeeeevil.
- robin_reala 7y agoEmbrace in the EEE metaphor specifically refers to an existing standard or pseudostandard.
- 7y ago
- hyperman1 7y agoI think you are missing the point: Something like systemd has a good reason to exist. But the devil is in the creating team. We've seen pulseaudio, a good system in theory, but an untrustworthy unstable system in practice. And if it wont work, it is so complicated and non-transparent that you need a specialist. Taking a step backward from Alsa is hard, and they managed to do it. Now that same team is messing with system critical stuff. We know from the kernel command line debug debacle they rather see the world burn down than admit they did something wrong. They are again creating a super-complicated incomprehensible half- documented mess, that puts it tentacles everywhere. But the stakes are a lot higher. I am not saying they are incompetent. At a low level, the code works. But at a high level, something is very wrong. Bugs can be fixed, but arrogant architecture astronauts not listening to their users, messing with core infrastructure, that's where systemd keeps failing.
- orf 7y ago> We know from the kernel command line debug debacle they rather see the world burn down than admit they did something wrong Can you expand? I've not heard of this.
- Tomte 7y agoIIRC, they printed more messages to the console when booting Linux with a debug parameter than Linux could handle. Systemd developers were like "nobody can tell us how much detail to print", until the kernel developers made clear that the boot console belongs to them and if systemd doesn't back down immediately they would take away all console access. Systemd then backed down.
- turbinerneiter 7y agoSo you are saying two teams maintaining two systems which are working together tightly had a conflict about how those systems are supposed to work together and resolved it after some heated discussion? Sounds like Open Source to me.
- hyperman1 7y ago
- pdkl95 7y ago> does ONE thing and does it well: it manages the system "managing the system" is not "ONE [problem]". A big part of the problem with systemd is this presupposition that management of something as large and complex as a modern OS is a single monolithic[1] problem. > it's complex because it does a complex work. See, you agree that it's a complex problem! It's so complex with so many different use cases it isn't even possible to have one solution, because some of those use cases are mutually exclusive. Hench why a modular design is important, so it isn't too difficult to replace the management of different areas if needed. > It's the missing layer between kernel space and user space. That "missing layer" isn't well defined. There certainly wasn't any "missing layer" on my old server, or the compute boxen we used at ${research_lab}. If you're talking about desktop system, I agree that there was a gap between traditional system management and the GUI, but that isn't really a new "layer" between kernal and user space (it might involve GUI userspace programs with perhaps some of them being SETUID or a privileged daemon). [1] Any objections trying to claim systemd isn't a tightly coupled, monolithic design will be ignored. If you think the number of binary program files is in any way useful as an objection, see: https://news.ycombinator.com/item?id=19024256 https://news.ycombinator.com/item?id=19024256
- ninkendo 7y ago> it isn't even possible to have one solution, because some of those use cases are mutually exclusive Could you elaborate? What of systemd’s use cases conflict with one another?
- AsyncAwait 7y agoYou still have s6, openRC etc. as choices, but it's funny that nobody of the anti-systemd folk was willing to pick up the work needed to maintain consolekit, yet when logind came around, had lots of strong things to say. How about picking up the work as well? And none of the alternatives seem to really get away from the bash script paradigm & more towards the declarative side of things, which doesn't feel like much beyond keeping all that was terrible about sysvinit around in thin wrappers. Maybe GuixSD is the one exception to this.
- pdkl95 7y ago
- tannhaeuser 7y ago> It's complex because it does a complex work Hence it's pointless because it doesn't make things any simpler. All it does is making things monolithic and wrapping concepts that are perfectly fine by themselves, forcing third-party software to write to systemd's APIs. > Systemd actually does ONE thing and does it well: it manages the system. "Managing systems" is not what is meant by "doing one thing, and doing it well". Systemd takes over init scripting, logging, host names, IP, time, locale, and login, plus tens of more services. Making development of this software a Lennart Poettering/RH-only business rather than community-driven. The trend to get rid of systemd and its metastasis into most of Linux is excellent news. Note that Slackware and Devuan are also systemd-free (and have been from the beginning).
- ses1984 7y agoAs an end user, meaning a web app developer, I actually like systemd a lot. I perceive the software quality to be good enough. I've used it in production since 2014 and encountered zero bugs. It does seem to me to be vastly simpler compared to the old way of doing things. I don't really feel strongly either way. I'll be pretty sad if Debian and redhat diverge.
- tannhaeuser 7y agoI don't know what you're doing to start your web/app server, but for eg. apache httpd it's a matter of sudo apachectl start (and likewise for all SysV-like startup scripts). For node, it's node <yourapp.js> (or rather using node-forever or node-cluster in prod). If you want to have it started on boot automatically, you put that line into your startup script. It doesn't get any more simple and transparent than that. Why would you be sad if Debian and RH diverge? Linux started as a one-man show and became a huge community effort because it could run a wealth of F/OSS software. If you want a single-vendor OS, there's Windows, Mac OS, the BSDs, and others. Or maybe IBM RHEL in the future.
- ses1984 7y agoIf you do `sudo apache start` in production, how do you do it? Log in to the server and type it in? What about log and metrics agents, how do you start and configure those? Also why are you so judgemental? I don't want Debian and rhel to diverge because I have clients who use both and I don't want to have to do more work to support both.
- einpoklum 7y ago> Systemd actually does ONE thing Yeah, except that the "one thing" it does is "everything".
- devit 7y agoThe best way to see systemd is simply as the userspace part of the Linux kernel, with a similar monolithic but modular design.
- tiew9Vii 7y agoI'm an end user. As an end user I don't mind SystemD for writing / managing service unit files. I often find the restart policies and one time only jobs useful especially in cloud with automated deployments. My feelings on SystemD as end user are neutral, it does have some useful things but I understand some of peoples grievances with it. On the other side I have some OpenBSD systems and the simplicity of OpenBSD service management just being plain bash files is really pleasing to use if anything because of the simplicity and power/functionality it provides without actually doing much itself.
- tannhaeuser 7y agoCongrats on "getting" the Unix philosophy! Nit: OpenBSD uses ksh not bash
- StreamBright 7y agoNo, systemd does many other things than just managing the system. It provides time, dns, dhcp and other services. None of which is required for achiving what it is suppsed to do: managing unix services.
- crb 7y agoCan you link to the course you did?
- std_throwaway 7y ago> it manages the system It manages the system in a way that not everybody needs or even likes. To the people who hate it, it solves problems that other people have but brings new problems that they now have. It's not so much about if it's good or bad but more about whom it was made for.
- badrabbit 7y agoIt has it's place but it doesn't work for everyone. I mean,there's something called user-acceptance testing for software dev lifecycles right? (Not a pro dev myself) systemd obviously has an issue being accepted by a lot of users even after almost a decade now(?) Even before systemd there were other init systems used by different distros. The fact that systemd demands other things to adopt to it instead od smoothly integrating with existing systmes is one pain. A bigger pain is how it is expected to work well for everyone. I mean, dislike for "one size fits all" solutions is a major reason why most Linux users became Linux users.
- deleted 7y ago[deleted]
- axaxs 7y agoI used to be a sysadmin. I still hate systemd, and think a lot of who like it are suffering from Stockholm syndrome (joking, maybe :)). It's not that I don't understand it, or use it, because I've been forced to for years. It's that it made everything about my job harder, and abstracts or attempts to abstract everything. As an end user, I get liking it. It's fast, and mostly works. As a person who likes to poke and prod, it's a gross nightmare of inconveniences.
- gabrielblack 7y ago> it manages the system No, really. I, the system administrator, manage the system(s). Does Systemd make my life easy ? No, again. It's something I have to deal for. If I could, I would follow the example of Knoppix.