Frequently Asked Questions

Q. Do you hate systemd?
A. No, we don't. In fact, we love systemd. But we would never use such a sucky piece of bloatware near anywhere we cared about security.

Q. Why, then?
A. Many, many reasons. Also, search the web for "systemd CVE".

Q. No, I mean why Artix?
A. Because running after Arch was a second-grade approach. By forking Arch Linux and cutting out all the systemd cruft we can be sure that upstream changes won't affect the project negatively and that systemd won't creep into the binary packages.

Q. Who's behind Artix?
A. Them and more. Also check out the "People" section of the sidebar.

Q. What does Artix mean?
A. It's complicated. But "The Art of Linux" sounds nice.

Q. Are you aiming towards artists and multimedia people or something?
A. No, but the software collection of Artix, Arch and the AUR can cover every need.

Q. Why are there still systemd components (i.e. logind and udev) in Artix?
A. They're elogind and udev-standalone, which is different.

Q. What about pulseaudio?
A. Technically, pulseaudio is not part of systemd. It works fine but you can also use pipewire, alsa or even oss4.

Q. Why not consolekit2?
A. It's not (yet) on par with elogind in features and requires specifically patched packages. Maybe later.

Q. I'm new to Linux, can I use Artix?
A. Yes. Just don't get a base ISO to begin with. Use a community edition.

Q. How can I help?
A. Thought you'd never ask!