|
|
|
|
|
|
by yjftsjthsd-h
1486 days ago
|
|
|
I guess I'd offer 2 big points. First, systemd came in and replaced a lot of the base OS, happily changing things to be... either "modern and designed with hindsight" or "breaking compatibility because they could", depending on your viewpoint. As an end user it was mostly invisible, but anyone mucking around under the hood got half the engine replaced on them, and it was not appreciated. (A major example would be the journal; for 40 years logs went into nice flat text files that could be watched with tail(1) or searched with grep(1), and then systemd came along and moved logs into a binary format that forced you to go through journalctl to access anything.) Second, systemd can be viewed as "playing dirty" in the way that it was pushed through the ecosystem. It was viewed as Red Hat pushing their preferred solution by leveraging what should have been unrelated packages - udev went from an init-agnostic database of hardware and rules engine to being part of systemd and everyone else had to factor it back out, GNOME made systemd a dependency, that kind of thing. Further, the developers tend to take a... "our way is right and anyone who disagrees is out of touch" view, while being remarkably blind to other systems; my favorite was https://github.com/tmux/tmux/issues/428 , wherein they wanted tmux (a portable program hailing from the BSD side of the ecosystem) to abandon existing daemonization code and go with a systemd-specific approach. They even came out and said that they were happy to try and make things harder for people who didn't accept their way - why try convincing someone to adopt your approach when you can just modify the ecosystem to progressively make it harder for them to do things their way (https://lists.freedesktop.org/archives/systemd-devel/2010-Se...)? |
|
|
Update: The bug was related with integrated Bluetooth card on some Dell laptops and is fixed on Ubuntu 22.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/17598...