4 ms·
To reiterate something I just wrote in another post: Whatever you think of it, systemd is doing the "ground-up rewrite" correctly. Normally, you get 90% of the
by derefr 10y ago
To reiterate something I just wrote in another post:
Whatever you think of it, systemd is doing the "ground-up rewrite" correctly. Normally, you get 90% of the features for 10% of the code in a rewrite, but then the last 10% of the features are the "plugging this thing into the ecosystem of other crufty things" features which bloat the codebase into something exactly as bad as the original.
The only successful way to do a rewrite is to scope your rewrite not to the size of one component, but rather to the size of the whole component ecosystem, such that you get to redefine all the crufty boundaries requiring convoluted code into clean and simple ones. This means you do have to rewrite more things, but each one can stay at that 10%-for-90% size, because none of the bad-API bloat has to come along.
systemd is consuming components of the Linux userland and leaving cleaner boundaries in its wake. The sheer scope of that effort can make the project look bloated—but people forget to compare the codebase with the combined codebases of all the projects it took to have equivalent functionality before.
People also forget to compare the functionality of the entire ecosystem of software—not just the big stuff everyone uses, but the niche stuff—before and after. Linux's original bazaar approach to system software meant that everything worked with whatever components it explicitly planned to work with, and nothing else. Do you know how many codebases contained some random subset of support for logging via STDOUT, logfiles (with or without rotation), syslog, rsyslog? That's what you get with a bazaar approach. systemd's "hub-and-spoke" cathedral approach means that everything just has to work with systemd, and then systemd can ensure that everything works with everything else.
- justinsaccount 10y agoExactly.. The most amusing thing about this is people claiming they are going to switch to a bsd. As another said on the other thread: > I really dislike the idea of having one project handling everything on a box Which is crazy talk because that is one of the selling points to something like openbsd.
- protomyth 10y agoI get what they mean and its not really crazy talk. The difference between a project in the sense of systemd and project in the sense of OpenBSD is pretty big. If I told you that wget was requiring changes to all user behavior, you would laugh it off and wonder where they got the agency to demand that. Many folks view the people with such agency as the kernel developers and the GNU project not a project such as systemd. They are probably wrong these days. This is different than the pick of a BSD.
- justinsaccount 10y agoMeanwhile openbsd adds pledge(2), patches most of their userspace to support it, and is praised across the board. If linux tried to add pledge you'd have people coming out of the woodwork claiming that linux was breaking UNIX and requiring "linux specific" patches to every project.
- Spivak 10y agoPledge was not praised across the board for precisely the reasons you mention. It's optional so no one aiming for portability will implement it, it's not user configurable, permissions are too broad, it's unusable by any application that isn't pledge-aware, etc.. Now SELinux isn't perfect by any meaning, but the key difference is that applications can be SELinux aware if they choose, but you can still have full protection without the application knowing that it exists. I would much rather try to improve SELinux than try to make pledge work for precisely this reason.
- Elhana 10y agoIt is also the reason why most common advice is to just turn off SELinux. It blocks valid (although sometimes weird) usage, because someone else decided that 90% of users should not do something. Developer knows better what program should and should not do and is much more capable to set this kind of rules with pledge.
- digi_owl 10y agoLets not forget that SELinux came out of the defensive side of NSA. Its to block attacks to government systems from both outside and inside. In essence it is the concept of "trusted computing" given form. And that concept in turn means that a general can put a trusted system into hostile territory and trust it to not leak secrets. And NSA still care for it. Around the time of the last kdbus dustup, someone from NSA voice a worry about how kdbus would compromise certain parts of SELinux.
- MaulingMonkey 10y ago
- busterarm 10y agoUnfortunately this includes rewriting tools that have scope beyond your ecosystem. Many of these tools have to run in other *nix. Tmux came out of the OpenBSD community. Why would they necessarily want to put in effort to make sure your house is built correctly?