Skip to main content ↑ ↓
Topic: Why does systemd exist? (Read 2981 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Why does systemd exist?

Reply #15 –
Because R*d H*t is a company motivated by profit and simplicity and stability does not sell, so they kept bloating up Linux to create bugs and security vulnerabilities so they could sell their services.
Being that not enough, they decided to create soystemd, and they had to, because at this point they have bloated Linux enough with so many services at boot that the argument of parallel service start became logically sound. With soystemd they got plenty of bugs and security issues to keep selling support for years, again.
Now the commercialization of Linux is complete, with p*ettering working at micr*s*ft. I'm surprised that R*d H*t is not a subsidiary of Microshit yet.
Embrace, extend and extinguish.

Re: Why does systemd exist?

Reply #16 –
Quote from: throwaway927832 – on
Because R*d H*t is a company motivated by profit and simplicity and stability does not sell, so they kept bloating up Linux to create bugs and security vulnerabilities so they could sell their services.
Freedom as a Service!

Re: Why does systemd exist?

Reply #17 –
Quote from: Sulfide9842 – on
Quote from: awky – on
Why does systemd exist and why should i care about it?
Quote from: Shoun2137 – on
I think the question should be "Why systemd was adopted at such an astonishing rate"... And the answer is - control and money.
I don't want to stir up controversy, but I think the main reason systemd was adopted by most distributions is that it offered fairly good parallelization capabilities when it was introduced. My favorite init, which is OpenRC, still doesn't provide a parallelization capability as good as that of systemd. I guess reading the following pages can answer your questions:
Systemd
Debate initsystem systemd
Systemd
I think this adds to the discussion, in that it addresses what made Systemd attractive.
Specifically I would like to know what one can do with Systemd NOW, that another init(s) cannot do, or do not do well.
And in specific response to Sulfide9842, of course other inits do, right?

Re: Why does systemd exist?

Reply #18 –
Sysd has those dynamic services used by socket activation (start when neeeded), or as other non service types of what it calls "units" and parts of it is useful (getting actual status more than just stderr/fishing a metalog), i know it clashes with unix where a process does it's own thing but a sort of a standardized api won't hurt, sysd doesn't standardize much anyway (apart from like auditing?).

User services are also prettier, although dinit-turnstile-dinit works mostly (basic functions+controlling of the "slave" by the root instance), it's still not as good.

Also the measurement of service startup is sometimes useful.

"Masking" services is something that dinit lacks and kind of needs now with the new codependency scheme.