5 ms·
Systemd is monolithic, and does a lot of things that one might want to do differently. It follows the footsteps of a similar macOS program, and apparently impor
by nine_k 7y ago
Systemd is monolithic, and does a lot of things that one might want to do differently. It follows the footsteps of a similar macOS program, and apparently imports a bit of the general philosophy from Apple: one way to do all the things, dictated by the producer of it.
It's much more than an init system; it obviates a number of other components. This may be a desired quality for some. "Linux monoculture" is a real thing, and systemd makes it seriously more monocultural.
The fact that systemd did not have the highest reliability for years did not help its popularity. It was not entirely gently pushed on everyone by Red Hat, by making Gnome dependent on it.
OTOH the history shows that technically poor, and even terrible, things can get wide enough adoption and stick with us for a long time; X is a good example, SysV init is another.
- mateuszf 7y ago> OTOH the history shows that technically poor, and even terrible, things can get wide enough adoption and stick with us for a long time; X is a good example, SysV init is another. Funnily Unix and C are also examples of "worse is better". https://www.jwz.org/doc/worse-is-better.html https://www.jwz.org/doc/worse-is-better.html
- DoctorNick 7y agoMore testicles mean more iron.
- nitrogen 7y agoClicking that link from HN will (usually?) give you something NSFW; jwz doesn't like HN, so copy/paste the link if you want to see the real link.
- SturgeonsLaw 7y agoDidn't do it for me after multiple attempts :(
- mike_d 7y agoYou end up with a redirect to https://web.archive.org/web/20191014203443/https://www.jwz.org/images/2016/hn.png https://web.archive.org/web/20191014203443/https://www.jwz.o... (Mildly NSFW)
- DyslexicAtheist 7y agoperhaps your browser strips the http referer header (with custom settings or done by some privacy extension)? https://wiki.mozilla.org/Security/Referrer https://wiki.mozilla.org/Security/Referrer
- uwydr 7y agohttps://addons.mozilla.org/en-US/firefox/addon/smart-referer/?src=search https://addons.mozilla.org/en-US/firefox/addon/smart-referer...
- pferde 7y agoWait, you do not block HTTP referers by default? In this day and age where vast majority of websites are out to scoop any and all available information about you?
- tome 7y agoThe fact that you don't send a Referer may ironically make it more easy to track you.
- minitech 7y agoIt’s information for fingerprinting, sure, but not sharing the page you’re visiting from for every link click is much more important for privacy IMO.
- pferde 7y agoAnything you do online can be used to track you. The point is that by doing this, you plug an additional information leak about yourself.
- boomlinde 7y agoThe best option I think is to spoof Referer to a random choice of known good values. This, of course, after disabling other, more reliable tracking vectors like JS and cookies that would just identify you as a Referer spoofer.
- deleted 7y ago[deleted]
- sjwright 7y agoGiven that systemd is just a set of interconnecting components, is it really fair to call it monolithic? While it does ship as a unified project, my understanding is that you can substitute individual parts of it easily enough.
- freedomben 7y agoExactly. Systemd is highly modular, and for the most part can work with a variety of different alternatives and interconnections. There a few hard dependencies but for the most part I don't think it's fair at all to call it monolithic.
- flukus 7y agoIf it's highly modular then why (according to TFA) are they struggling to incorporate a fork of a systemd subcomponent? If that's not easy to do then it's not modular.
- geofft 7y agoAs I understood the thread, the problem is not that it's hard to get elogind running, the problem is that getting applications to provide tested, supported non-systemd init scripts (or equivalent) requires a commitment from the packager and occasionally from the upstream community. This is an entirely unrelated question to modularity - the "problem" is that systemd supports certain features and if you want to run without systemd, some other component needs to support them. Such components could be designed pretty easily, sure, but people who are using those features are typically happy with systemd's implementation so there's little motivation to write them. In the article, systemd's tmpfilesd mechanism is given as an example. It's straightforward to reimplement as a standalone component, but someone has to actually be interested in writing the implementation and writing tests that it behaves like systemd does and keeping it up to date.
- flukus 7y agoWhat you just described is still very much what I'd call a monolith. Much like if you have a microservice architecure (that we had a system level prior to systemd) then each component should be testable, upgradeable and swappable in isolotation, if you don't have that then what you've really got is a distributed monolith (obligatory xkcd: https://sebiwi.github.io/comics/distributed-monolith/ https://sebiwi.github.io/comics/distributed-monolith/). What we have here is a dependency chain that pulls in all of systemd, therefor it isn't modular. It isn't modular just because it's divided into modules.
- lazyguy2 7y ago> Systemd is monolithic, It's monolythic in the same what that the GNU project or FreeBSD is monolithic. It's a large number of utilities, tools, and daemons that is designed to provide the low-level features application developers and users demand from a modern operating system. > It's much more than an init system; Systemd is a init system, but systemd is also a major project that has taken on the task of unifying low-level Linux OS features. > "Linux monoculture" is a real thing, and systemd makes it seriously more monocultural. FreeBSD is a monoculture. OS X is a monoculture. Solaris is a monoculture. OpenBSD is a monoculture. All these systems have their own init systems they designed with no regard towards Linux and replaced older systems and obsoleted them. > It was not entirely gently pushed on everyone by Red Hat, by making Gnome dependent on it. Lies and misrepresentations. > OTOH the history shows that technically poor, and even terrible, things can get wide enough adoption and stick with us for a long time; X is a good example, SysV init is another. Which is why people are working on replacing both X and SysV. You want to know the real problem with anything-but-systemd crowd? This: > Of course, this approach is not viable if it turns out that too few people are interested in init system diversity sufficiently to do the reasonably substantial implementation work required to maintain a competing implementation of the systemd unit features we care about. There is no 'If' there. Some people don't want systemd, but the only people doing the work are Systemd. So their choice is to stick with Linux from 2000's or use systemd. Because nobody wants to commit to making any alternative actually work. Making noise online is annoying, but it ultimately is not something that goes into the decision making of people designing operating systems. People willing to do the work are the ones that get to make the choices. If somebody comes along and makes a better init system then systemd then they can do it and if it is better it will get adopted. You can pretend that this is all Redhat's fault, but they are the only real enterprise that made the transition from sysv in Rhel 5, to upstart in 6, and then to systemd in 7. And, ironically with systemd, migrating to another different init system is massively simplified compared to the work it took to migrate from sysv init. So now moving to a new init system is easier then ever. Why do I say this? Because systemd has unified OS design for Linux in a way that never happened with sysv init. Sure people were using 'sysv' and all used shell scripts, but they were all fundamentally different from one another. Only the most complicated shell scripts imaginable (think Apache init) or the most trivial could be made to work on more then one Linux distribution. Meanwhile systemd uses a declarative configuration syntax that all you need to do is create a parser and you could effectively import any systemd application configuration into a system with equivalent or better capabilities in any operating system. The same can't be said for any of the bash scripts developed by any of the distributions prior to this for their own sysv variant.
- kissgyorgy 7y agoIt is NOT monolithic at all. It is probably ignorance, but I never really understood why would people say this.