Artix Linux is a rolling-release distribution, based on Arch Linux.

It uses real init systems, because PID1 must be simple, secure and stable.

Recent news


Server is back online



The server is back online and we managed to get some services working again.
Working services:
  • Archive
  • Galaxy repository

It may take a while for each mirror to sync again.
The Gitea instance will be restored later.
Thank you for understanding.


Server malfunction



Due to server malfunction multiple Artix services are unavailable.
This includes:
  • Gitea
  • Archive
  • Galaxy repository
If the problem is not very serious it should be fixed sometime during the Monday.
Thank you for understanding.


Changes to default password hashing algorithm and umask settings



Following the related Arch announcement

With shadow >= 4.14.0, Artix Linux's default password hashing algorithm changed from SHA512 to yescrypt.

Furthermore, the umask settings are now configured in /etc/login.defs instead of /etc/profile.

This should not require any manual intervention.

Reasons for Yescrypt
The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam) and its stronger resilience towards password cracking attempts over SHA512.

Although the winner of the Password Hashing Competition has been argon2, this even more resilient algorithm is not yet available in libxcrypt (attempt one, attempt two).

Configuring yescrypt
The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix module (i.e. in /etc/pam.d/system-auth).

General list of changes
  • yescrypt is used as default password hashing algorithm, instead of SHA512
  • pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
  • changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile



Repository structure changes (updates)



Following the related Arch migration announcement, our repository structure has changed accordingly. The [gremlins] repository has split into [system-gremlins] and [world-gremlins]; likewise, the [goblins] repository has split into [system-goblins] and [world-goblins]. The [galaxy] repository has been merged into [world].

How are end users affected?
Those who don't use testing ([-gremlins]) and staging ([-goblins]) repositories won't see any difference; those who do, will have to enable [system-gremlins] and [world-gremlins] manually.

The Universe repository
All packages from this repository have been moved to the replaced galaxy repository. As a result, those who have the universe repository enabled in pacman.conf should remove it and add galaxy.
Another change is that the [-bin] packages have been removed, as these can be built locally. Also, librewolf had to be dropped due to critical build issues that occur since the last two versions.

The omniverse repo will remain as it was and is, though some of its packages will be moved to the galaxy and world repositories.


Repository changes



Following the related Arch migration announcement, our repository structure has changed accordingly. The [gremlins] repository has split into [system-gremlins] and [world-gremlins]; likewise, the [goblins] repository has split into [system-goblins] and [world-goblins]. The [galaxy] repository is in the process of merging into [world].

How are end users affected?
Those who don't use testing ([-gremlins]) and staging ([-goblins]) repositories won't see any difference; those who do, will have to enable [system-gremlins] and [world-gremlins] manually. The updated /etc/pacman.conf will roll out of [system-gremlins] once our new layout and updated developer tools are sufficiently tested.

The unused repositories will remain active, but empty, until the transition is complete. In general, most users shouldn't notice much except for a short period of diminished updates, as packaging has frozen for the duration of the migration. Please report any issues at our forum.