I will tell you once the stop job finishes.

it's wibecoded

It just works, so /g/ hates it.

>>109885335
>stop jobs waiting for 5 minutes
more like doesn't work

>>109885256
>>109885313
>>109885315
>>109885335
>>109885335
It still amazes me how retarded some of the visitors here are that after all these years still dont get it (it is obvious from your statements). Truly a low IQ board.

>>109885364
You're using it in a retarded manner for a non-existent use-case.

>>109885378
Thanks for the contribution to the thread, brother. Would love to meet you some time soon.

it's a catchall "suite" that does a bunch of different system things in a way that interconnects them and somewhat leads to lock-in
for example, systemd handles (can handle) login and then initiating various devices, along with the network stack, and then also things like timers and scheduled jobs
some people think it would be much better if distinct system jobs had different packages, for example if there was a particular system login package and then a distinct network package, and then someone could write a competing network package to replace the old one
right now, in a lot of ways you can't really replace systemd (on most distros that use it), so you can't introduce an independent and novel network stack, or at least for a systemd distro to switch to it they would still be "using systemd," just disabling systemd networking and replacing it with the new package
whether or not systemd "works well" (i personally like it), this aspect of lock-in is really unappealing to some people on a philosophical level

>>109885393
I have no interest in meeting you retards.

>>109885378
Why you are so mad bitch?

>>109885413
We'll meet nonetheless.

>>109885416
She's like that sometimes. I don't really get it either desu.

>>109885378
other inits don't have that crazy stop jobs like systemd

>>109885416
Because you waste pixels on my screen.

>>109885428
you can always walk away
no one ever asked for your opinion

>>109885819
OP asked. Learn to read retard.

File: systemd.gif (3.99 MB, 426x284)

3.99 MB GIF

this

>>109885256
t. never tried OpenRC, dinit, etc.

>>109885256
PulseAudio broke my audio in 2009 and from that day forward I swore off any Poeterring-ware. And init scripts are fine and easy. I don't like service files because they're not shell scripts.

>>109885412
you don't have to use everything systemd supports, you know. pretty sure the only non-optional component is the journal.
like the networking stuff you give as an example, networkd/resolved are optional and you don't have to use them when using systemd. lots of distros use networkmanager instead of networkd

>>109885256
You answered your own question. It does too many things and the Unix ethos is to do one thing well. It's 1M lines of code, and for an init system?

Then there's the backdoored argument, which is schizo stuff (it's obviously backdoored, but everything is).

>>109885256
It's "systemd". Please post with its proper name next time. Thanks for keeping /g/ post quality high!

>>109885256
It's autism mainly.
The top guidelines are a nice sentiment, but once you get into practicaility it has it's limitations.

>>109885427
Yes, other inits just corrupt your data for no reason. So much better!

none of you people know what systemd is and what it isn't. so tiresome...

>>109886576
other inits have all the benefits with zero downsides
systemdick is the reverse

>>109886396
most people don't know and that's the main issue. They take what is served to them, lack the skill to modify it or even understand properly what's under the hood, and when something breaks, it's all going straight to the "i fell for the x" meme.

>>109886576
>init system can corrupt data
The amount of lies in one post. Pottering shills are really something.

>>109886516
More like systemdick on your face

>>109886461
its not just unix ethos
systemdevil is so convoluted that one user can never be ought to understand its complete workings, making informed consent implausible

giving something so opaque access to so much of a fundamental part of your system undermines the open source principle altogether
with its 2 gazillion lines of code systemdevil relies fully on the
>just trust me bro
mentality

It's created by Lennart Poettering. I hate that guy

Consider for a moment that the strategy of systemd - which is to say of the team behind it - is to consolidate everything the OS does in the background within one backbone. Once that happens, it won't be about what module you can or cannot do without: a distribution will require this backbone as a dependency once enough userland software embraces the infrastructure it offers. This gives a limited set of developers a very large amount of power over the FOSS ecosystem.

People including myself are weary of such power being consolidated in this way. Therefore, systemd is a threat to the very ethics of FOSS.

t. most parsimonious /g/ lurker

Lennart only cares about stock desktop and stock server experience.
systemd is riddled with assumptions that generally seem sane, but quickly get into nightmare territory in many embedded environments.

What's so fucking annoying about Lennart is that people pointed out early on in systemd development that the design is going to break a lot of use cases for absolutely zero upsides and proposed alternatives that would work for everyone. But Lennart is psychotic or something I don't know he just couldn't have anyone else propose anything so he told everyone to go fuck themselves.

>>109885256
>writes your dns to use cloudflare/google without the ability to easily change it or alerting the user that its sending your dns entries, to data brokers
>changing dns to not be selling your queries is not straightforward and most desktops dont allow you to configure systemd-resolved
>contains a bunch of other equivalently rewritten apps which didn't need to be rewritten which also are not configurable by desktop environments
this one thing actually made me dislike all of systemd