3 ms·

Let me ask the other end. What context do you have to compare it to what it replaced for any given use case? Can you tell me why its good? Can you tell me why i

Let me ask the other end. What context do you have to compare it to what it replaced for any given use case? Can you tell me why its good? Can you tell me why its better? What problems it "fixes"? Reasons to dislike systemd as a professional sys admin? https://github.com/systemd/systemd/issues/2402 https://github.com/systemd/systemd/issues/2402 - brick EFI based systems! https://twitter.com/bitfield/status/736868148348063744?lang=en https://twitter.com/bitfield/status/736868148348063744?lang=... -- Systemd broke your very mature stable application like screen and tmux? https://nvd.nist.gov/vuln/detail/CVE-2018-15688 https://nvd.nist.gov/vuln/detail/CVE-2018-15688 - Root a box on bootup with poison DHCP offers I can keep going, but how are you doing on my questions?

baked_ziti 7y ago
>https://github.com/systemd/systemd/issues/2402 https://github.com/systemd/systemd/issues/2402 Well that seemed needlessly contentious. What a shame.
- the_why_of_y 7y ago
  Indeed, what a shame. Firmware is so crappy that deleting variables bricks it, and the Linux kernel decides to expose those variables as a filesystem so that a simple shell command like rm -rf will actually delete EFI variables, instead of exposing them via ioctl like FreeBSD did [1]. As you can see, if systemd hadn't been invented there would be no problem. [1] https://reviews.freebsd.org/rS307070 https://reviews.freebsd.org/rS307070
  - baked_ziti 7y ago
    > Like I said. Needlessly contentious.