Void is a general purpose operating system, based on the monolithic Linux kernel. Its package system allows you to quickly install, update and remove software; software is provided in binary packages or can be built directly from sources with the help of the XBPS source packages collection.
It is available for a variety of platforms. Software packages can be built natively or cross compiled through the XBPS source packages collection.
Visit the Void build server console for package build status updates.
Void Linux is an independent distribution, developed entirely by volunteers.
Unlike trillions of other existing distros, Void is not a modification of an existing distribution. Void's package manager and build system have been written from scratch.
Void focuses on stability, rather than on being bleeding-edge. Install once, update routinely and safely.
Thanks to our continuous build system, new software is built into binary packages as soon as the changes are pushed to the void-packages repository.
Void Linux supports both the musl and GNU libc implementations, patching incompatible software when necessary and working with upstream developers to improve the correctness and portability of their projects.
xbps is the native system package manager, written from scratch with a 2-clause BSD license.
XBPS allows you to quickly install/update/remove software in your system and features detection of incompatible shared libraries and dependencies while updating or removing packages (among others). Refer to the Handbook for an overview.
xbps-src is the xbps package builder, written from scratch with a 2-clause BSD license.
This builds the software in containers through the use of Linux namespaces, providing isolation of processes and bind mounts (among others). No root required!
Additionally, xbps-src can build natively or cross compile for the target machine, and supports multiple C libraries (glibc and musl currently).
We are aware of an ongoing infrastructure issue affecting repository synchronization and package signing. We are working to resolve this disruption, but first must resolve another unrelated infrastructure issue. We have no short term ETA for service restoration, however our worst case resolution timeline is Friday the 23rd of July.
Your patience is appreciated while we perform this work as fast as possible.
We have been made aware that during the mass channel takeover that is
ongoing on freenode that bogus
have been created in the secondary namespace.
We do not operate or engage with these channels, and we do not
maintain an official presence on the freenode network. We are still
in the process of finalizing the shutdown of the
#voidlinux channels in the primary namespace, and have removed our
channels from the public listing as part of this process.
Though you should always exercise caution when running code obtained from the internet, we urge you exercise extreme caution when using any code from any channels on the freenode network that claims affiliation with the Void Linux project. You can always find our official points of presence listed at the top of our home page.
If you want to ask the Void team questions in real-time about this or
any other Void related matter, feel free to ask at any time in