I'm not gonna lie systemd is pretty useful. And it follows

>>61681524
This.

>>61681524
nice bait someone will fall for this and you will be yelled at and be happy

File: systemd-devours-all.gif (4MB, 426x284px) Image search: [Google]

4MB, 426x284px

>>61681524
>it follows the unix philosophy of make one simple program rather than two complicated ones

the unix philosophy is "do one thing and do it well", not "do everything and fuck it up"

As an Arch user should I remove systemd in favor of openrc or switch distros to something without systemd all together?

>>61681524
>it follows the unix philosophy of make one simple program rather than two complicated ones


isn't systemd more like making one very complicated program rather than several simple ones?

File: 1482154222066.png (158KB, 680x681px) Image search: [Google]

158KB, 680x681px

>>61681524

File: 1500369788390.png (279KB, 500x500px) Image search: [Google]

279KB, 500x500px

>>61682680
>>61682346
>>61681717

>>61681524
go away lennart

systemd cant even handle a dns query with an underscore in it without being exploited

>>>lgbt/8650537

>>61682790
Why the fuck is an init system handling anything to do with DNS?

>>>/lgbt/8650537
stop it lennart

>>61681524
can someone give me a quick rundown on systemd?

>>61682834
maybe lennart could tell us
>https://www.theregister.co.uk/2017/06/29/systemd_pwned_by_dns_query/

quick question. If I want to make an even-driven sysv rc script that is triggered by something like inotify how would I go about doing that? I know with systemd it's just make a .path file to the directory i want to watch and a .service file with the same name. Does sysvinit also have something as intuitive as this I am able to leverage?