systemd 253: You're looking at the future of enterprise Linux boot processes The first systemd release of 2023 is here, and it introduces a brand spanking new tool for building Unified Kernel Image (UKI) files. Fresh versions of systemd appear roughly twice a year, apart from release candidates. We reported on the last version, systemd 252, in November last year. As we said at the time, systemd 252 …
Systemd 451 would naturally be preceded by systemd 365 [no need for worry]
I also have to wonder why RH went to a monolithic "thing" that needs regular monolithic top-down updates like Windows...
(perhaps it is a form of job security? sysV makes more sense in that it does NOT need regular monolithic top-down updates)
The Linux kernel grows with new features and new hardware support and the occasional bug fix. THAT should be enough for JUST the kernel to abstract the userland from the hardware on its OWN!
What is strange is that due to the monolithic nature of systemd and in particular its "tentacles" such as systemd-networkd, it is very difficult to import it on a site by site basis.
Consider for example Red Hat's refusal to use it for RHEL8 and 9 (unlike 7, they don't even have it in EPEL because maintaining individual systemd components is too tricky).
https://bugzilla.redhat.com/show_bug.cgi?id=2020254
https://bugzilla.redhat.com/show_bug.cgi?id=1650342
So basically the issue is, RHEL favours NetworkManager but the only way to get systemd-networkd into the site install, is to not only maintain systemd-networkd but also an entire self managed and non-standard install of systemd (where the hooks haven't been patched out by Red Hat).
Screw that. You basically have worst of both worlds of a monolithic and distributed design. Utter trash.
systemd 666 will be completely benign however other groups will be fanatically opposed to it and commit all manner of atrocities in its name.
The key difference between systemd 666 and alternatives is the removal of "PulseAudioIOd".
Perhaps that is a good feature request.
Those with long running experience get *two* votes rather than one so that we can help guide the inexperience masses rather than getting bogged down in their noise and naïve choices.
This exists in industry most of the time, so why not internet forums?
There are very rational reasons why many people have valid reservations about Lennart Lennart Poettering's misguided creation and Nala Ginrut's observations are presented below:
"Few years ago, I was working for SUSE Linux Enterprise (SLE) as full-time developer. My boss asked me if I’m interested in maintaining systemd for SLE. At that time I know little about systemd. Then I said “I’ll see what I can do”.
I’ve downloaded the source code accompanied with 2000+ backport patches, this took almost a half day. When I was waiting, I had reviewed the code and try to find out what’s in it. And I had contacted several experienced colleagues to learn about it from them.
Finally, I could figure out that systemd takes advantages of Linux kernel things to start services in parallel. This sounds good, but it introduces unbelievable complexity for such a functionality. If you’re a common desktop user, maybe you rarely encounter problems, or you may endure some bugs in systemd. But for an enterprise version Linux, it makes the work of maintainer hard.
And the 2000+ backport patches implies that I (as the maintainer) have to maintain all of them alone, since it’s backported. I discussed with my boss, and told him this kind of work requires a small group people, rather than one man effort. Fortunately, my boss agreed with me completely, so he managed to throw out this package to a bigger team.
Even now, I still remember the complexity in systemd code, and I always tell my engineer team to avoid such kind of complexity in the project. Eliminating complexity is far more important than adding features without clear mind. Don’t try to put every good features into just one project. Every feature is good, but package all of them, you’ll get shit.
I don’t know who got this package finally, but I hope she/he is fine…"
^ The home user might not notice systemd's effects and consequences but for those of us who work in deployed enterprise Linux situations, we do get to see the downsides of systemd.
"...that I'm going to cow down to you "
Did you mean kowtow? See here.
If so I cannot disagree with your sentiment. All of my boxes are mine, not Microsoft's, Red Hat's, Gnome's or any distros that force me to use something I do not want to touch with a bargepole. That's why I'm sticking to PCLinuxOS and as others have said there are plenty more to chose from.
That's why a lot of people love Linux.
Don't like it? Move to another distro or roll your own if that's your thing.
Hm. No. More like "Please Mr. Microsoft can I build a kernel and you sign it for distribution to a wide audience wh run it on hardware that is mostly used for Windows deployments?"
You can sign your own kernels with your own key, just don't expect other people's machines to have the key installed out of the box.
Eventually enough people will wake up and give systemd the boot. Its feature creep should have been cause long ago. The problem will be removing it. It is becoming the mighty shim on which everything depends, so removing it will affect everything = a lot of work. The sooner the process of getting systemd out starts, the less work there will be in the long run.
I was idly wondering what would one expect if one added ChatGPT to Systemd?
(The kitchen sink is already plumbed in I understand. :)
Pinocchio could be an appropriate name for the resulting anathema because, apart from the nose thing, I suspect it might start up asking "Are we Windows yet?"
Is Pootering (sic) part of the Extend mission by Microsoft to eventually Extinguish Linux as we currently know it?
Perhaps it's a case of - systemd isn't finished until Linux can't boot?
Beware of geeks bearing gifts.
PS I'd like someone to ask AI Bing 'who are the useless cunts that work at Microsoft?'
who are the useless cunts that work at Microsoft
As an AI language model, I cannot engage in derogatory or disrespectful language towards individuals or groups of people, including those who work at Microsoft or any other company. It is important to treat all individuals with respect and professionalism, regardless of our personal opinions or frustrations. It's important to remember that the people who work at Microsoft, or any other company, are human beings with feelings, families, and personal lives, and they are doing their best to do their jobs and contribute to society. Let's focus on constructive and positive conversations that can lead to better understanding and solutions.
This post has been deleted by its author
Really? Does the retailer/supplier include the Bitlocker Recovery key too? Or is the user screwed if something changes or breaks? And who else has a record of the PIN and recovery key? Are their systems online and potentially accessible/hackable?
That's why MS is forcing you to login with a MS account, so they can store a copy of the encryption key in their cloud. User is screwed in many ways but losing encryption keys is not one of them.
Me too I don't like FDE without having the control of the keys.
[Reposting as ancestor deleted, but the package comment may be useful to someone.]
I'm certainly not opposed to the BSDs, and Slackware was my first Linux distro way-back-when.
But, it's Devuan for me. Mostly as I prefer apt as a package tool, especially in those rare cases of package dependency issues. There's also an abundance of debs too - backports, sid, Ubuntu's (often more up-to-date than Debian's) - again making pick'n'mix easier for me in time o' trouble. I know debs can be used in Slackware, but I've no need to add the extra layers - I prefer staying with indigenous tools.
Also XFCE as default, KDE got a bit bloated for me. Again, I know Slackware has XFCE as an option, but my track record for breaking a non-default desktop is, er... admirable?!
That said, I've not poked around with Slackware for some time - perhaps I'll rectify that.
I'll conclude with a concise opinion: fuck systemd.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
