News for hackers. Stuff that matters.
Re:Systemd-homed merged as a fundamental change to Linux hom... by wnoise on Friday January 31, 2020 @05:13PM (#22206432)
Without the amount of changes systemd makes to the operation of a system, at this point it should be thought of as a new operating system that shares a kernel with Linux.
Re:Systemd-homed merged as a fundamental change to Linux hom... by theclaw on Friday January 31, 2020 @06:22PM (#22207012)
I don’t have a problem with this. I am seeing systemd as a system management layer and as such it makes sense that it should manage as much of the moment-to-moment operation of the system as possible. It seems like a lot of people are upset because it’s a new thing to learn that’s being forced on them by their distro.

I used to feel the same way. I’m only a casual linux user and I didn’t want to climb this particular mountain but having learned just a little about it, created some of my own units and played with the tools the sense of alienation dissipated and I was fairly happy with it.

Re:Systemd-homed merged as a fundamental change to Linux hom... by mondoshawan on Friday January 31, 2020 @06:27PM (#22207052)
I suspect most of us are upset not at learning a new thing, but dealing with brand new bugs in new unexpected ways. Learning a new thing has never really been a problem -- fighting instability in new software has always been the issue.

Speaking as a distribution developer, I can say that systemd has bitten me in multiple ways due to upstream bugs that are either ignored or left to rot for quite a while. I've had to resort to patching them, or working around them, which makes things very difficult to live with, especially given the pace of systemd development and feature additions.

The older software had a number of bugs, yes, but they were well known and battle tested. In short, it's not "I don't want to learn" -- it's "the new shiny has a slew of unknown bugs we can't easily identify and fix".

[edit: removing bits of incendiary text]

Re:Systemd-homed merged as a fundamental change to Linux hom... by castillar76 on Saturday February 01, 2020 @11:42AM (#22211443)
Very much agree. I'd add that the reaction of the systemd developers to security and functionality bug reports has been...decidedly mixed, which is enough to make me very nervous.

For me personally, it's also that systemd keeps expanding and expanding, which both makes more things dependent on their security profile and reduces choice in the ecosystem. The number of different boot/init systems I might need to use is pretty limited and I might be OK with just one (especially since systemd /is/ really good at it). The number of DHCP clients, firewall systems, DNS clients, and so forth is decidedly not so limited, and results in a nasty choice of "use the systemd thing and hope it supports all the features you need" or "rip out the systemd thing and replace it and hope that works and continues to work" or "install something that sits on top of the systemd thing and thus has to interact with it in strange ways that may bite you unpredictably". Each of those is a recipe for a lot of Maalox moments, and it feels like the response to that concern is, "Aww, you're just being a worry-wart."

Re:Systemd-homed merged as a fundamental change to Linux hom... by eikenberry on Friday January 31, 2020 @06:36PM (#22207112)
Older software should always have fewer bugs simply due to maturity. Ie. progress isn't free. The best way to mitigate that is where distros like Debian stable come in. They help gate these developments, releasing more well tested versions of the software and fixing any critical issues that come up with it over the time of the release.
Re:Systemd-homed merged as a fundamental change to Linux hom... by mondoshawan on Saturday February 01, 2020 @10:20AM (#22210932)
My distribution is based on Debian. Systemd is still a thorn.
Re:Systemd-homed merged as a fundamental change to Linux hom... by pmlnr on Friday January 31, 2020 @05:25PM (#22206553)
This is exactly what systemd sceptics have been shouting for years.
Re:Systemd-homed merged as a fundamental change to Linux hom... by throw0101a on Friday January 31, 2020 @05:48PM (#22206735)
We're not there yet:

Every program attempts to expand until it can read mail. — Zawinski's Law

Re:Systemd-homed merged as a fundamental change to Linux hom... by inetknght on Friday January 31, 2020 @06:15PM (#22206963)
All that's missing is a gvfs module to mount your IMAP directories...
Re:Systemd-homed merged as a fundamental change to Linux hom... by rbanffy on Saturday February 01, 2020 @04:03AM (#22209551)
From a UI perspective, this is brilliant. Windows had it with a shell extension that essentially turned Windows Explorer (not IE) into what would later be Outlook Express. It's awful that they opted out of making the desktop Explorer smarter and went the stand-alone application route.
Re:Systemd-homed merged as a fundamental change to Linux hom... by grawprog on Friday January 31, 2020 @06:25PM (#22207039)
At this point you'd think systemd was trying to catch up with Emacs as the most 'everything but the kitchen sink' of all the software
Re:Systemd-homed merged as a fundamental change to Linux hom... by salawat on Saturday February 01, 2020 @12:31AM (#22208894)
Emacs went further. It absorbed systemd.

See systemE.

Re:Systemd-homed merged as a fundamental change to Linux hom... by Koshkin on Saturday February 01, 2020 @09:37AM (#22210693)
Sure, the .emacs script could be just as good an init as any.