4 ms·
I run openRC on Arch. If you want to escape from the horrors of systemd, it's a good way to do so. But I've ranted far too much about systemd here on HN to wri
by qwertyuiop924 10y ago
I run openRC on Arch. If you want to escape from the horrors of systemd, it's a good way to do so.
But I've ranted far too much about systemd here on HN to write another one without explicit prompting.
The point is, I really like OpenRC: generally speaking, it's well-designed, reasonably simple, easy to manage, and actually does what it's supposed to. What systemd-isms that have invaded haven't effected me yet.
- imiric 10y agoI'm considering doing the same. Have you had any issues migrating to OpenRC on Arch? Things to look out for?
- qwertyuiop924 10y agohttp://systemd-free.org http://systemd-free.org provides a repo with all the stuff you need, including openrc scripts, eudev, and patched versions of other software that has fallen to the cancer, like the *kits. They provide simple installation instructions, and it should Just Work. Issues are rare, although the usual Arch caveats apply (anything can go wrong depending on how your system's set up, when in doubt, check the blog/rss associated with your repos, as there might be valuable information, etc). However, I have noticed a few things: -While the repo does provide pulseaudio, it doesn't provide the 32-bit pulseaudio packages. This means that 32-bit applications that try to use pulse won't play audio properly. However, these are rare. Do be sure to force SDL and openal to use alsa, though. -Some software (like Samba) expects systemd to be there when you compile it, and wants systemd as a runtime dependancy. However, (again, as with Samba), these pieces of software sometimes provide config options to remove systemd integration. Consult the project documentation, or just run `./configure --help`. -I have experienced some audio issues in 64-bit applications (namely, firefox). Although I suspect this is unrelated, it's worth mentioning.