systemd's Growth Over 2022

[gosh000]

Yeah yeah, "it is not Red Hat"....... And Chromium isn't Google, etc etc....

... and https://www.npmjs.com/ is not MS. I hope that THEY won't buy crates.io

[jacob]

Yeah yeah, "it is not Red Hat"....... And Chromium isn't Google, etc etc....

It wasn't created by RedHat and Lennart doesn't work for RedHat. But the main point is that even if it was RedHat, that would change nothing simply because the licence is LGPL.

[CommunityMember]

Please refrain from making factual statements.

Not to worry, as there is typically sufficient numbers of stupid and rage postings even among the occasional factual ones to drive the page view advertisement revenue to keep the site operating.

[tildearrow]

1,7MLOC. That's a helluva init process. How much memory does this PID 1 use already?

It does more than just initialize the system. It's a full-blown system manager.

PID 1 is only a small portion of these million lines of code. The rest is logind, udevd and bunch of other daemons/features that aren't necessarily in PID 1.

[AlanTuring69]

It's so bullshit how systemd is just allowed to obsolete so many jobs... it used to take one dedicated person to manage only a few servers but now with systemd one person can manage dozens. All those years learning the specialized init scripts for 10,000 distributions was for NOTHING and they were just left out to dry... Linux community, shame on you!

[abott]

Just because of the odd comments, I'd like to let you people who are script kiddies and don't actually know much about the back end of things. Unix's motto is "do one thing and do it well", but that doesn't mean it applies everywhere. The included and basic tools should be generic and easy to use! It's a great idea! however when you need an init SYSTEM, the SYSTEM should be able to handle all tasks the SYSTEM should be expected to. It's not a single tool, it's a custom SYSTEM of functions and goal, not basic Unix tools. If that's too complex for you, please don't even talk system engineering rofl.

[kpedersen]

All those years learning the specialized init scripts for 10,000 distributions was for NOTHING and they were just left out to dry... Linux community, shame on you!

Indeed. Though it means that now the kids will never manage to get a foothold into the industry since the existing greybeards can now manage everything themselves.

Probs for the best in this day and age. Experience is key. Can't have a bunch of unsecured LAMP servers laying around like you could in the early 2000's.

[darcagn]

It's so bullshit how systemd is just allowed to obsolete so many jobs... it used to take one dedicated person to manage only a few servers but now with systemd one person can manage dozens. All those years learning the specialized init scripts for 10,000 distributions was for NOTHING and they were just left out to dry... Linux community, shame on you!

So is systemd more than an init system or nah?

It's amazing how systemd defenders pick and choose when it is or isn't depending on the argument at hand.

[AlanTuring69]

So is systemd more than an init system or nah?

It's amazing how systemd defenders pick and choose when it is or isn't depending on the argument at hand.

systemd is a community and a way of life for those script kiddies who do everything on easy mode!

Actually:

systemd: An umbrella project that also has systemd the pid 1 process and has a lot of features between all the different systemd-* projects. Pedants need not use it.

[rogerx]

Just because of the odd comments, I'd like to let you people who are script kiddies and don't actually know much about the back end of things. Unix's motto is "do one thing and do it well", but that doesn't mean it applies everywhere. The included and basic tools should be generic and easy to use! It's a great idea! however when you need an init SYSTEM, the SYSTEM should be able to handle all tasks the SYSTEM should be expected to. It's not a single tool, it's a custom SYSTEM of functions and goal, not basic Unix tools. If that's too complex for you, please don't even talk system engineering rofl.

Well, that was the likely plan when beginning SystemD.

However, now it takes multitudes of people for managing one computer running SystemD.

The only one person that could manage one computer or multitudes of computers running SystemD, eh, went back to Microsoft.