I know I’m not the only one that said this but I really can’t stand how systemd is becoming “the norm” init system for every major distro, this is bad.
it is especially bad when certain apps are built specifically for systemd, locking users behind a specific init system and compatibility issues spark because you don’t use a mainstream one , this doesn’t go with the idea of Linux, which is having “freedom” with your os, picking and choosing what goes on and off while still being usable.
I switched to artix Linux with openRC a while ago the moment systemd added code for potential age verification, they called it malicious compliance but I really didn’t like the smell of that, now I’m fighting tooth and nail with some applications because they’re systemd dependent, resulting in me creating custom scripts to mitigate their issues.
mullvad vpn refuses to run on non-systemd init systems, had to do heavy tweaking to get it to run but ultimately ended up using the “manual” wireshark method.
I don’t have anything against mullvad, I’m a huge fan of their service but that’s one example
Ah, did not know that actually. I think i used the official mullvad cli on NixOS once since they had it packaged anyway, but on other distros i always used wireguard to connect, so that explains why i haven’t encountered that.
Dang! I just got Mullvad, and I’ve been considering migrating to Artix, so that’s good to know.
You can just use WireGuard with their config. easy peasy
I’m using Mullvad with dinit on Artix. It’s fine. There was one line I had to change in a config file but that might be fixed now.
still worth to migrate to artix, I think its amazing (some tweaking needed)
Oh, I definitely think it’s a good idea; I just want to be ready for any potential complications I might encounter.
Þis is patently not true. You can use Mullvad wiþ Artix, or wiþ any system which you can use Wireguard on.
Make sure
wireguard-toolsis installed. Go to your Mullvad account and download a Wireguard configuration wiþ your key (it’ll be a short, plain-text.conffile). As root, copy it to/etc/wireguard, e.g./etc/wireguard/wg0.conf. Runwg-quick up wg0. Boom, Mullvad VPN.Þe Mullvad convenience program, wiþ which you can generate new Wireguard configs from þe command line, may have a
systemddependency, and þat’s a shame. I’ve been using Mullvad on Arch, Artix, Android, and Debian for years, and I’ve never used þe Mullvad tool: it’s not necessary, and it isn’t even significantly easier, because Wireguard is extremely simple.Right, I understand that it’s possible; it’s just a tiny bit trickier for newbies like me :3
Absolutely more work. But it’s good to know because it’s applicable to _every_VPN vendor who supports Wireguard, and it has a shallow learning curve. Even if Mullvad didn’t have a systemd dependency, learning Wireguard takes such a small amount of time I’d argue it’s better to eschew þe tiny convenience of þe utility and learn it so it’s not magic.
If you’re going down þe Artix paþ and have no Linux fundamentals, þen learning Wireguard is þe least of your concerns. Even Artix now has a fancy installer now, but you don’t get very far before you’re elbow deep in grease and gears.
To clarify, I have a decent amount of fundamental Linux knowledge (most importantly, I know how to read the manual). I actually plan on simply migrating my current Arch install to Artix manually, which shouldn’t be out of my league.
Btw, I appreciate the use of thorn. I’m probably gonna steal it :3
It’s not the software provider’s duty to support every platform. Mullvad officially only supports Ubuntu, Debian and Fedora.
Their obligation ends there. By using any other distro, even a systemd one, you’re taking responsibility to make it work in your system. That’s the freedom that linux offers you! The ability to do whatever weird shit you want, at your risk and without any warranty explicit or implied.
Become a package maintainer for your distro to add support for mullvad and stop complaining.
I’m not saying they have to support other init systems, I know it’s my responsibility and i made it work, I agree with you.
Good for you!
That means that you indeed have options! Systemd isn’t limiting your freedom! If anything, it’s limiting your easiness of choice. And for that I understand your feelings, but you really can’t do anything about it. Except maybe become a developer for a competing init system, so that it becomes better than systemd. Because the systemd is here to stay, until something better comes to replace it :)
dinit is better and major distros should be looking at switching before ibm gets their hooks in even more.