41–50 of 111 posts
Reminder about alternatives: For the less extreme case, when you want mostly one distro, but also a few packages from another one, there is “alien” [0] which converts between different package formats. It sometimes needs help with system integration or dependencies, but occasionally “just works” For a more extreme case, there is a schroot (or a docker container) with /home, audio and X mapped in. Works surprisingly w…
Most of time it's 5 commands tar -xf code.tar.gz && cd blah && ./configure && make -j5 && sudo make install
Earlier quoted context omitted.
What are the top 3 alternative ways to do GNU/Linux without systemd?
Genuinely curious, for both casual and advanced users, what *major* reasons are there for not using systemd? I've used systemd for years bug-free
Earlier quoted context omitted.
Genuinely curious, for both casual and advanced users, what *major* reasons are there for not using systemd? I've used systemd for years bug-free
Something I can't accept is the use of binary logs and the requirement for programs to access the contents of the logs. Yes, most distros will put compatibility layers in place and create text "logs" in parallel. But if everyone is doing that maybe systemd's paradigm isn't right for the desktop even if it's great for servers.
Earlier quoted context omitted.
Another solid alternative is to install the nix package manager[0] and get access to thousands of packages. I have stopped installing stuff from apt and thankfully my system never breaks now. [0] https://github.com/NixOS/nixpkgs
I don't understand. I am sure the nix repository is quite large, as are Debian's and Fedora's ones. But how would nix help you mixing packages from different repositories, which is Bedrock Linux use case?
Earlier quoted context omitted.
What are the top 3 alternative ways to do GNU/Linux without systemd?
Genuinely curious, for both casual and advanced users, what *major* reasons are there for not using systemd? I've used systemd for years bug-free
I once had "systemctl restart unbound" reset my volume, consistently. How do you even start debugging something like that without a deep dive in systemd? This particular issue turned out to be a systemd bug, and that such a bug can exist in the first place didn't exactly increase my confidence in the system.
In another case I couldn't get my NFS to work at all, and it turned out that rpcbind.service somehow went missing. Not sure how that happened and it's a simple enough problem, but it was really non-obvious because systemd doesn't issue clear errors on this and the system is so complex it's not easy to spot either.
Earlier quoted context omitted.
What are the top 3 alternative ways to do GNU/Linux without systemd?
Genuinely curious, for both casual and advanced users, what *major* reasons are there for not using systemd? I've used systemd for years bug-free
Reminder about alternatives: For the less extreme case, when you want mostly one distro, but also a few packages from another one, there is “alien” [0] which converts between different package formats. It sometimes needs help with system integration or dependencies, but occasionally “just works” For a more extreme case, there is a schroot (or a docker container) with /home, audio and X mapped in. Works surprisingly w…