9 ms·
A word about systemd (2016)
- oldpersonintx 2y ago[dead]
- chris_wot 2y agoA central point of their thesis is that Systemd folks bullied others into accepting it. That's not really the case, though. The Debian folks had a very transparent discussion and vote about using it: https://www.debian.org/vote/2019/vote_002 https://www.debian.org/vote/2019/vote_002
- o11c 2y agoRelated, it's also blatantly ignoring that it's the first software that even allows interoperability in its space, and was thus in huge demand by both developers and administrators. (Edit: Other anti-systemd rant sites sometimes mention these obliquely as "upstream dependencies" and "workplace-mandated", while ignoring the fact that those people have reasons to demand those things) But HN really doesn't need to litigate this all again.
- unsnap_biceps 2y agowhat do you mean by interoperability?
- jeyernhg 2y agoin the bad old times, every linux distro implemented its init scripts in a slightly different way, often with distro specific tooling and commands for accomplishing most management tasks
- westurner 2y agosystemd unit files require minimal modification by distro repackagers. With SysV-init, it was/is necessary to modify /etc/init.d/servicenamed shell scripts to get consistent logging and respawning behavior. With SysV init it's not possible to add edges between things to say that networkd must be started before apached; there are 6 numeric runlevels and filenames like S86apache, which you then can't diff or debsums against because the package default is S80apache and Apache starts with A which alphabetically sorts before the N in networkd. And then add cgroups and namespaces to everything in /etc/init.d please
- michaelmrose 2y agoThere were and are other options other than systemd and SysV years prior in fact. OpenRC and upstart predate it and s6 was not much later.
- westurner 2y agoIt's possible to pipe stdout to syslog through logger by modifying the exec args. But I'd rather take journald's word for it. Supervisord (and supervisorctl) are like s6. I don't think any of these support a config file syntax for namespaces, cgroups, seccomp, or SyscallFilter. Though it's possible to use process isolation with any init system by modifying the init script or config file to call the process with systemd-nspawn (which is like chroot, which most SysV-init scripts also fail to do at all, though a process can drop privs and chroot at init regardless of init system). systemd works in containers now without weird setup. Though is it better to run a 'sidecar' container (for e.g. certbot) than to run multiple processes in a container?
- o11c 2y agoI (and this applies both with my dev hat and with my admin hat) can now write a unit file, depending on a different unit file, that works the same across all distros (note that this includes random end users whose systems I don't directly have access to). This even works for services that start per-user; no more write-only modifications to user startup files or DE-specific autostart dirs. Pre-systemd this was unthinkable. (similar stories apply to non-systemd-proper parts of the systemd project, but I personally haven't used them as much)
- michaelmrose 2y agoUpstart and OpenRC both came years prior. As a matter of course anything which was self contained and standardized could have allowed interoperability. Systemd just actually convinced everyone to standardize not least because its integration with other parts of systemd provided both a carrot: standardization and simplicity for distro maintainers and a stick: the extra work required to use only part of it or especially if one used none of it and was expected to both write ones one unit files AND integration with stuff like gnome which was and remains the most popular singular GUI.
- yjftsjthsd-h 2y agoConformity is not interoperability. If anything, systemd is like Chrome, so popular that it persuades people to drop interoperability outright and just run with its nonstandard APIs.
- rcxdude 2y agowhat standard is systemd replacing? One of the big reasons it's popular is that there was no standard way to do most of the things it does.
- akerl_ 2y agoI have to wonder if this is some kind of statistical bias based on the type of engagement. There are some people who are vehemently opposed to systemd, for a variety of reasons with varying degrees of merit. I think it's fair to say that systemd's developers broadly ignored those people, figuring out (correctly) that if they convinced a majority of distribution maintainers, and made the user experience for the average user smooth enough, that was actually going to be successful. As it should be: distro maintainers get to pick how their distros work, and users determine which distros they use. And systemd has a clear sell for those groups: distro maintainers can standardize their service scripts, often just using what an upstream package author can write agnostically to distro, and users can handle the majority of base system functionality without having to pick things like "which of these cron daemons should I install".
- theamk 2y agoI'd also add that systemd appeals to application developers (no daemon code, one file for all distros). And it appeals to sysadmins too (no more /etc conflicts on any package update! Modify any system service! etc..) Which brings me to the question of which category systemd does not appeal to? I am guessing "minimalists" and "people who like things done the old way" - and those are simply not that numerous compared to others.
- egorfine 2y ago> broadly ignored those people, figuring out (correctly) that if they convinced a majority So, politics at its worst. Being ignored on a matter, especially when there is merit involved, can make someone a highly motivated hater.
- akerl_ 2y agoSurely for each individual distro, they get to make their own decision about how to build their system. I can’t stop you from hating, but if your pitch is that distros shouldn’t be allowed to make their own choices about what to include if you disagree… I guess your option is to start your own distro. No linux distro was forced to adopt systemd. They did it on the merits, from their determination.
- happymellon 2y agoDidn't Arch also adopt it as the defaults before anyone else. I can't see that being a project that would be bullied easily. Especially not "bullied so that it was adopted before almost everyone else".
- kemotep 2y agoIf you haven’t seen this talk[0], I think it covers in a fair shake the positives, negatives, and what even a post-systemd world would have to deal with. [0]: https://youtu.be/o_AIw9bGogo https://youtu.be/o_AIw9bGogo
- favorited 2y agoIt wouldn't surprise me if Benno Rice wrote that talk in response to this exact blog post – though there were enough posts in this same genre at the time, and he could have been responding to any/all of them.
- inferiorhuman 2y agoa fair shake Benno's entire argument is that Linux is the only operating system that matters and whatever problems systemd has are irrelevant. Everything else is obsolete. Especially when couched as "look at what this BSD guy thinks of systemd" it's a disingenuous argument. That talk is no more a fair shake than anything to come from Lennart's mouth.
- kemotep 2y agoI would think a BSD developer has a good idea of the challenges facing OS development and the implementation of an init system. I do not think it is charitable to them to say they think only Linux matters. If that’s the case why are they a FreeBSD developer?
- inferiorhuman 2y agoHave you not watched the video then? There are a couple sections on why portability is not important because only Linux matters. Benno's words: The reality is UNIX is dead… these days I think you've basically got Linux and some rounding errors. So why is he a FreeBSD developer? Good question.
- kemotep 2y agoLook, I use linux, OpenBSD, Apple and even Microsoft operating systems. I thought the video provided a unique perspective to the systemd discourse that I thought people would be interested in seeing if they hadn’t already. I couldn’t care less if Debian announced that Debian 13 is going to default to s6 or runit as the init system. I have no loyalty to systemd other than the Linux distros I use have integrated with it. The linked article introduced me to s6 which is interesting. I do think there is value in simpler codebases a la wireguard, toybox, and doas. None of the hostilities towards one init project over the other have ever made sense to me but “the battle” was mostly fought before I got into Linux.
- niobe 2y agoThis old chestnet eh?
- andrewstuart 2y ago>> The single, overarching problem with systemd is that it attempts, in every possible way, to do more instead of less. The more systemd does, the better I like the power, features, consistency and functionality my linux systems have. systemd is a beautiful work of art. Software developers owe it to themselves to full understand what systemd has to offer, because if you really understand it then you'll find you can architect your systems around systemd and often let it to the hard work for you. If anything, the old gnu/linux name should be dropped and replaced with linux/systemd to illustrate that in fact systemd is really a major part of what Linux is.
- viraptor 2y agoI can't tell if it's sarcasm or genuine, but I 90% agree. There's a lot of things that it makes easier. But there are areas which are just weird and overengineered and overcomplicated - for example resolved interacting with old files and creating lots of possible ways it can run. If you look at forums / SO it's obvious people are confused about what it tries to achieve. Instead of creating a whole new system, they could've started by implementing and standardizing the multi-interface behaviour in established projects like dnsmasq. Instead of that they went with NIH where it really wasn't necessary.
- theamk 2y agoFor resolve.conf, I think it is fundamentally bad design that is hard to get right. Before systemd, I've spent plenty of time trying to get networkmanager and resolvconf to play together. And then there was those dhcp scripts which would edit the files directly. Also, what do you mean my "standardizing dnsmasq behaviour?" From my recollection of using it (and from manpage[0]), it's pretty basic. You (1) manually edit /etc/resolve.conf to point to localhost dnsmasq instance (2) use app-specific ways to configure nameservers, in dnsmasq's case it's an ad-hoc list of secondary resolv.conf files specified on command line, with no defaults. I don't think this is worth standardizing, as this scheme cannot even represent network interface -> dns entry associations. https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
- taf2 2y agoI was a systemd hater. I agree with a lot of the post but in practice I need a whole lot less custom scripts, forking code, etc to maintain a simple service whether it’s a custom c binary, go, rust, nodejs , ruby , python… I don’t need to mess with monit(for most things) and yeah in less words then my post here I could have a working service that would both restart on crash and on reboot…. Do I miss the init.d scripts and writing pid files forking twice to change user … no
- matheusmoreira 2y ago> writing pid files forking twice to change user No idea why software tries to "daemonize" anyway. Seems to be some kind of weird tradition. It's always been the wrong thing to do. They should just run normally and output to standard streams even if it's connected to a terminal. The reasons are outlined here: https://mywiki.wooledge.org/ProcessManagement https://mywiki.wooledge.org/ProcessManagement Ironically, systemd is one of few service managers which can properly track those weird "daemonizing" processes. It uses Linux's cgroups. It doesn't matter how many times they fork, they can't hide from systemd.
- theamk 2y agoNot sure what exactly you were pointing to, but section "Doing it right" (4.3.1) recommends: mydaemon & daemonpid=$! This is a terrible advice - that's how you end up with all sorts of bad things: - you ssh'd into server, restarted server, checked it worked. Then you logged out and server got killed. - your server runs as root or power user - your server output/error goes somewhere, not clear where - your server's process got paused by SIGTTOU, because it was trying to write to console etc... The complex daemonization dance, with double-forks, closing random FDs, etc.. was required to avoid all this bad stuff before systemd days. Sysvinit/openrc folks came up with "start-stop-daemon" helper, but it was pretty terrible in general, especially in logging department (it had none).
- matheusmoreira 2y agoHandling all of those conditions is the job of a proper service manager like systemd. It does things like restart processes that died, redirect output to logs, set process user and group, etc. The point is software should be written to make the service manager's job as easy as possible by keeping it simple.
- troad 2y agoI get frustrated when people misstate the Unix philosophy. The Unix philosophy is about function, not form. Say you have a tool to send something over a network. In 1993, that tool can get by being quite simple. In 2024, that same tool now needs to be more complex, just to do the same 'one job' and to 'do it well'. It's a consistent insistence that the 'single job' be defined today just as it was in 1980 that results in Linux requiring hundreds of packages to be even remotely usable. Oh, you want Wi-Fi? Well, that's not really the job of the networking stack, the job of the networking stack is to connect PDP-11s together...
- smaudet 2y agoThe single major flaw with systemd... Linux was(is?) the system. Shell scripts could configure the system, reasonably well. Systemd meant it was no longer possible to simply fix a linux distro that had it...a massive recompile and intricate understanding of many low level systems was needed. No, you shouldn't need to know about PDP-11s to fix your buggy wifi, neither should you need to know a massive binary subsystem to configure your wifi either... So as far as doing its "one job", it did/does it fairly poorly, even today. It is a lot more standard and it does get points from me in that respect, but it fails at being a configurable system completely.
- akerl_ 2y agoI've fixed a lot of problems on a lot of systems and never needed to recompile systemd. The majority of them I've fixed by editing text files. What kinds of problems are you hitting where you need to recompile systemd?
- smaudet 2y agoI could simply trace shell scripts with some file io, or echo statements. Now there are systems using python, even better I can set breakpoints and modify, no need to recompile. Configuring the system with textfiles only works if the system anticipated all your needs, and to anticipate all needs is not only complex but error prone.
- mike_d 2y agoSystemd being one big monolithic system locks you in to, frankly, just a lot of shitty decisions. Take for example the fact that it decides to bind to port 53 on localhost, for absolutely no good reason. Now if your response is that is not a big deal, or you push your glasses up on your nose and want to explain why its important, imagine for a second if it was port 80 or 443.
- jdenning 2y agoExactly - this is a perfect example of what has always bothered me about systemd.
- rerdavies 2y agoBinding a DNS server to 127.0.01:53 is a perfect example of what has always bothered you about systemd? Seriously not getting it. Providing DNS services on 127.0.0.1:53 has nothing to do with systemd. It's a convention used by NetworkManager, and associated network services. The very good reason being that network interfaces that are being brought up and down can choose to forward their DNS requests to 127.0.0.1, and allow a completely separate unit (resolved?) to deal with the details of where DNS requests get forwarded from there. (Or not, if they so choose). Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose?
- the_real_cher 2y agoFrom the man pages: "Additionally, systemd-resolved provides a local DNS stub listener on the IP addresses 127.0.0.53 and 127.0.0.54 on the local loopback interface" https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... > Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose? The problem is... by default... resolvd routes ALL DNS REQUESTS to this stub by over writing resolv.conf with ONLY that socket and forcing you to configure resolvers elsewhere. And you have to manually reconfigure this if you want to change it and it forces you to get in the weeds way to much when all you want to do is add a DNS resolver. https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html#/ETC/RESOLV.CONF https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... The confusing thing is why the heck is SYSTEMD an init system writing DNS resolvers? Seems out of it's scope in my opinion. I was surprised resolvd existed when I was trying to troubleshoot a DNS error caused by it.
- chasil 2y agoAs a previous user/exploiter of SysV init, I really like systemd. -I can spawn/respawn daemons as someone other than root. SysV inittab runlevels are root-only. -I used runlevel 4 for all my magic. Now I can have so much more magic. -nspawn has let me craft containers from day 1. -Path units are so much better than inotifywait (and somewhat better than incron). -Do I prefer socket units to inetd? Mostly. -Free automounter! Yes, crazy syntax, but gratis! Do I wish it worked on BSD? Yes.
- m463 2y agoI think there are two parts of systemd - the functionality and the implementation. It IS functional - it does things that are helpful and important. But the implementation is hard to swallow. It is just so far away from elegant, understandable and usable.
- akerl_ 2y agoCan you give some examples of implementation that are hard to understand and use?
- m463 2y ago- symlinks - systemd took the "accepted" idea of symlinks from /etc/init.d -> /etc/rc*.d and put symlinks all over the filesystem for all kinds of units. It is less understandable and manageable. - mediocre config files - they decided that config files are declarative, which could be good, but it pushed simple (and visible) logic in /etc/init.d/* files into more complicated logic encoded in binaries. The simplistic config files seem to be more simple for systemd to implement, but harder to understand, maintain and use. - binary log files. everything has to go through systemd to access them. - responsibility creep - systemd started taking over more functions, and it doesn't seem to stop. Will systemd turn into busybox, with simpler poorer implementations of every single thing in the system? dnsmasq is similar. The thing is, busybox and dnsmasq are cut down implementations for smaller system that are alternatives to their full-featured brethren. systemd takes over the core of a system.
- miller_joe 2y agoAs a declarative process supervisor i really like systemd. I don't like all of the other things it wants to do though.
- paradox460 2y agoI was indifferent to systemd until podman shipped quadlet. Now being able to bring up containers, tied to the system, in a reliable and efficient manner, without docker compose or big bespoke commands, has been incredible
- rerdavies 2y agoTrying to compare Windows updates favorably to updates on systemd seems a bit bizarre. I can't ever remember seeing an upgrade ask for a reboot on Raspberry PI OS (debian 12). And I can't ever remember seeing a Windows update that didn't reboot the system. As a long-time Windows developer (both apps and device drivers) substantially coming to Linux long after the decision to use systemd was made, I am impressed as heck by Systemd. And was completely horrified by my very limited experience, as a user, with pre-systemd Linuxes. That was insane. Manually edit what in to which system file? And my system invariably didn't even HAVE that file. Even writing systemd units is virtually effortless.
- deleted 2y ago[deleted]
- wannacboatmovie 2y agosystemd is bringing Linux feature parity to Windows NT in the mid-90s. That's 30 years ago for those of you keeping score at home. Funny the author mentions Solaris because Solaris has SMF and other systemd-similar tools. Linux pre-systemd looked like a kernel duct taped to a bunch of random thrown-together shell scripts... because it was. A sorry state of affairs that a bunch of very stubborn people were afraid to let go. The simple fact that configuring networking out of the box is completely different on every distro and sometimes within distros depending on which tools were loaded, in 2024, is simply insane.
- wmf 2y agoIf you allow distros it's going to lead to diversity. Even Solaris has multiple incompatible distos since they hired Ian Murdock.
- matheusmoreira 2y agoThat's what makes Linux great. The entire Linux user space is replaceable. You can trash it all and make your own if you want to. You can trash systemd, write your own program and boot Linux directly into it if that's what you want. And people do, myself included. Not a single other operating system lets you do this. There's always some component that you cannot touch. I'd rather have the chaos of Linux distributions than the tyranny of "standard" ways of doing things.
- vetinari 2y ago> You can trash it all and make your own if you want to. It is important to note, that if you want to do it, you have to roll up your sleeves and do it. Not to expect free manpower of others to provide it to you. Or in another words: http://islinuxaboutchoice.com/ http://islinuxaboutchoice.com/
- matheusmoreira 2y agoAbsolutely. The biggest reason systemd is taking over is companies like Red Hat keep paying people to work on it. As time passes, systemd gets better, gets more features, makes the life of distribution maintainers easier and therefore gets adopted, and makes the lives of users easier too, mine included. I'm making my own freestanding Linux thingy but I'm not under any illusions that it's going to replace systemd or any other software any time soon. I'm just one guy doing it in his free time because he enjoys it. I really hate it when I see people complaining about systemd. The people behind systemd had a vision, they reimagined Linux user space and put the necessary work into making their vision a reality. They're an inspiration for me. Not only that, they took their work and they released it as GPL licensed free software. One would think the users would be more thankful. One would think people would not have moral objections to free software getting released to the world. Some technical criticism is certainly warranted but the sheer hatred that people display towards it and its developers certainly is not. I agree that "Linux is about choice" is often misinterpreted. It's about my choice as a programmer and software developer to redefine the entire system downstream of the kernel however I want. Users are encouraged to themselves become technical and educated so that they too can enjoy this power. However, we're not about to drop everything and start maintaining some legacy system because people who aren't paying us keep insisting that it's how things gotta be done. We're programmers, we like it when things are made in our image.
- gavinhoward 2y agoI don't like systemd, but I don't like s6 either. What we need is something simple that uses something easy like unit files. (Though I wouldn't choose the systemd unit file syntax.)
- drdaeman 2y agoUnfortunately, there aren't any concrete examples (unless I skipped something accidentally), so it's hard to tell what exactly is meant as "does more" or that it doesn't "stand out of the way" etc. Yes, systemd services can do a lot of things. Except that before rc scripts did all those things, but without any unified and standardized primitives. systemd provides those for a lot of common use cases - and that's how it ended up doing so much - because our rc scripts used to do that. systemd actually does less because unit files are not scripts (but one can hook any external program in a lot of places, if they need to). Also, as I understand it, systemd isn't a single piece of software either, it's a whole project with a bunch of semi-autonomous pieces, tied with common conventions and assumptions. It's difficult to define the scope for an umbrella project, and I believe individual pieces all have their scopes relatively well-defined.
- matheusmoreira 2y ago> It's basically an integrated redesign of all the low-level userspace of a Linux system Yes, and that's okay. Whatever it is that came before it sucked so much I don't even remember what life was like before systemd. Also, it's amazing that we even get to redesign Linux user space like that. That's something special. Not a single other operating system allows you to do this. You could boot Linux straight into your program if you want, without any user space at all. Linux is such a solid foundation it lets you swap out the entire user space, you can trash systemd and even the entire GNU stuff and just do your own thing. It's inspired me to start working on a redesign of my own.
- egorfine 2y ago> You could boot Linux straight into your program if you want, without any user space at all. That was possible from around day one of linux kernel existence.
- matheusmoreira 2y agoYes. However it's not at all obvious that there is a clean separation between Linux and user space. You look up the manual entry on some Linux system call and it gives you the glibc documentation. You look up the init system in the manual, expecting details on what the kernel requires of PID 1, and it just gives you systemd documentation. This stuff is completely mixed up. You look Linux up on Wikipedia and the article eventually starts telling you about standard C libraries as if they were part of Linux. In some articles there's even a diagram showing glibc wrapping the kernel, as if it was Linux's equivalent to the Win32 API. https://upload.wikimedia.org/wikipedia/commons/4/45/Linux_kernel_System_Call_Interface_and_glibc.svg https://upload.wikimedia.org/wikipedia/commons/4/45/Linux_ke... In reality, you can trash that entire thing and remake the entire user space in Rust or Zig or Lisp if you want. No libraries are necessary.
- rendaw 2y agoKind of a non-sequitur, but what is actually the point of systemd (and other similar tools)? Like compared to just spawning a bash processes that run a critical commands in a loop. I can come up with a couple functions, but none of them seem like core things, more like tangential benefits: - Startup ordering means you don't get log spam with "can't connect to X" until X starts - Certain dependencies like mounts look the same whether they're "running" or not, so not starting before the mount is important. Or like, if a program enumerates interfaces or something, making sure all the interfaces exist first (via a dependency). Of course, a program could do its own checks and possibly be more stateless about it. - As a standard, for packaging - you can distribute a service/socket file with your program and most distros can just plug it in and expect it to work (also thanks to having standard targets and directories). Otherwise it seems like an ugly declarative DSL for gluing programs together, which you could do in bash or python or whatever other language too. Is reducing log spam really the point? FWIW I do think systemd is better than the alternatives ATM...
- akerl_ 2y agoI'm not sure what you're asking. On any system, something has to start "first", and be in charge of figuring out what the heck happens next. On modern Linux systems (and I'm oversimplifying massively), the hardware hands off to the kernel which launches some kind of init system the first userspace thing. That could be sysvinit or upstart or s6 or systemd or any number of other things. You could write it in any language, though the nature of when it has to launch strongly incentivizes writing it in some kind of compiled language so you aren't having to make sure the right interpreter bits are in place first. That thing then, depending on its level of complexity, gets to handle things like "what else do I launch" and "what order to I launch it in" and "what do I do if a service I started stops on its own". Beyond that, your life is way easier if more than one distro uses the same thing to do this, so that an upstream package author can write "this is how an init system launches my service" and distro maintainers can use that, vs having to create and maintain their own scripts for how their init system launches a service. So, the "point" of init systems is "something has to be in charge of userspace".
- rendaw 2y ago
- slater 2y agoServer seems to have received the ol' HN hug. Archive: https://web.archive.org/web/20240917143933/https://skarnet.org/software/systemd.html https://web.archive.org/web/20240917143933/https://skarnet.o...
- smitty1e 2y agoThe author seemed to be arguing at length about some sort of technical shortcomings, as though an argument had been made.
- kreetx 2y agoThe author also makes it sound like something has been taken away from them - one can rip it out if they really want to. It's just that most of us have our focuses elsewhere and have no need to tinker with systemd.
- dang 2y agoRelated: A word about systemd - https://news.ycombinator.com/item?id=19077561 https://news.ycombinator.com/item?id=19077561 - Feb 2019 (17 comments)
- LinAGKar 2y ago>when said software is process 1 and basically the whole low-level userland layer, it is frightening. So this is yet another person who apparently thinks all the different daemons made by the systemd project runs in the same process. >Remember sendmail, BIND, INN, and, definitely a better analogy, the early days of Microsoft Windows ? Honestly, no, I know next to nothing about any of these. Someone wanna fill me in?
- raspyberr 2y agoEvery time systemd comes up everyone says it's great and how much better it is than SysVinit. No one EVER talks about the actual alternatives that people use like OpenRC, runit, s6.
- tmtvl 2y agoBy all means, be the change you want to see. All I know about OpenRC is that it doesn't support user services the same way systemd does. I know even less about runit or s6, so I'd love to hear more from people who use them in their daily computing. Because unfortunately the impression I get from never seeing anyone talk about OpenRC, Shepherd, Upstart, et cetera; is that either nobody uses them, or they don't add anything worth noting over SysVinit. Though I'm surprised that you say: > Every time systemd comes up everyone says it's great and how much better it is When my experience is usually that people complain about systemd and it being over-engineered and doing too much and having too many components (yes, I know that those projects are related to systemd, not part of it, I'm just saying what I see people mention as downsides).
- graemep 2y ago> unfortunately the impression I get from never seeing anyone talk about OpenRC, Shepherd, Upstart, et cetera; is that either nobody uses them People do use them. Multiple distros either default to one of those, or support it: Alpine, Devuan, MX Linux, Slackware, Void, Guix, Gentoo and others. > or they don't add anything worth noting over SysVinit. Not looked at this myself, but do they mostly not add something - dependencies, easier config or something?
- skydhash 2y agoOpenRC just works for me (Alpine) there’s a declarative side that’s more than enough for simple services, but you can override logic for starting, stopping, reloading,… as it’s just a shell script.
- egorfine 2y agoHere we go again. I hate systemd. I sincerely and strongly believe it to be the worst thing that happened to the world of Linux. Note: this is just my opinion, of course I'm obviously wrong, can I have it please? Having said that I have to admit that the battle has been lost and there are no practically suitable server distributions clear from it, let alone desktop. So the only fight worth fighting is to delay destruction of other parts of the OS. In Ubuntu you can easily remove systemd-resolved, get rid of ssh socket activation, bring back cronjobs to crond and install a sane NTP client. Hopefully, we will still have sudo available for many more years at least as an optional package and then as a third-party deb. And thankfully we still have logs in /var/log and journald is not a hard requirement for anything. Yet. Otherwise resistance is futile as systemd people excel at politics and seemingly no opinion or input has any influence their decision making process. Again: I'm totally wrong here and systemd is good.
- toasteros 2y agoMy issue with the "systemd violates the unix philosophy" argument is that it... doesn't. I see systemd-resolved touted as an example of this. systemd-resolved is a different tool to systemd; it does one thing and does it well. Might as well say GNU violates unix philosophy because it has text processors AND a shell.