3 ms·

Pretty much. There are components of systemd I really like. systemd-logind is really neat, it makes dealing with drm (direct rendering) devices nice by having a

Pretty much. There are components of systemd I really like. systemd-logind is really neat, it makes dealing with drm (direct rendering) devices nice by having a service where you can request access to GPUs without bumping into the problem of one process opened the endpoint and has exclusive control. It also makes dealing with machine events like closing your laptop's screen simple if you use a minimalistic window manager like i3. systemd-resolved is nice if you're using systemd's network configuration system, but it's a pain when you're trying to run your own DNS server. udev really shouldn't hard depend on systemd. I perfectly understand having some systemd specific integration, but why make it mandatory? There being said, various people have been working to cut it into separate components (eudev, elogind, etc.)

microcolonel 6y ago
> udev really shouldn't hard depend on systemd. I perfectly understand having some systemd specific integration, but why make it mandatory? udev is part of systemd now, because the systemd developers were the only ones willing to maintain it.
- RunningDroid 6y ago
  Doesn't the existence of eudev disprove that? (This is a serious question; I'm not trying to start a fight)
  - microcolonel 6y ago
    I think the existence of eudev proves that somebody is now willing to maintain a udev, but it wasn't always the case.
    - TheGoddessInari 6y ago
      Eudev was forked in the immediate aftermath because systemd only cares about systemd. Even Torvalds strongly criticized systemd-udev maintainership[1]. 1. https://lkml.org/lkml/2012/10/3/484 https://lkml.org/lkml/2012/10/3/484