This web site is developed and maintained by the community of MX & former MEPIS users in order to support the exciting MX Linux in collaboration with the antiX Community. MEPIS itself is on indefinite hold, yet many users nonetheless run some form of MEPIS as their standard OS, and will continue to find support and a friendly reception on the MX Linux Forum.
MX Linux began in a discussion about future options among members of the MEPIS community in December 2013. Developers from antiX then joined them, bringing the ISO build system as well as the Live-USB/DVD technology. The name "MX" was chosen to combine the first letter of Mepis with the last of antiX, thus symbolizing their collaboration. In order to be listed on DistroWatch, MX Linux was presented as a version of antiX. It received its own DistroWatch page as a separate distribution with the release of the first Public Beta of MX-16 on November 2, 2016. Details here; release history here.
The MX Dev Team is composed of a group of volunteers of various backgrounds, talents and interests. These positions are filled by annual vote inside the Dev Team. Email Team Member Its administrative structure can be represented thus:
MX Linux combines packages from Debian Stable and antiX with MX packages in a dedicated repo that can be browsed on the Community Repository page. Debian Stable is a wonderful solid distribution that can be upgraded in place from version to version automatically as long as the Debian Stable repos are used exclusively. MX uses Debian Stable as a base, but updates a lot of the userland programs & libraries, and backports newer programs from testing by building them against the Stable base. That gives a better user experience but interferes with Debian's dist-upgrade path. Our current choice is to stick with sysvinit instead of going to full systemd. So it's a trade-off: better desktop user experience at the expense of having to do a quick fresh install (which lets you save /home if desired) when the Debian base changes, typically every 2-3 years.
The following Development Team members played a particularly significant role in the creation of MX-17: Adrian, anticapitalista, asqwerth, BitJam, chrispop99, dolphin_oracle, jerry3904, kmathern, mmikeinsantarosa, Paul.., peregrine, richb, Stevo, timkb4cq.
Special thanks for strong ongoing support of this project go to the MX Linux Packagers; to video producers Dolphin_Oracle, richb and m_pav; to our volunteers, especially Gordon Cooper and Old Giza; and to all our Translators!
Because the use of systemd as a system and service manager has been controversial, we want to be clear about its function in MX Linux. Systemd is included by default but not enabled. You can scan your MX system and discover files bearing systemd* names, but those simply provide a compatibility hook/entrypoint when needed.
MX Linux uses systemd-shim, which emulates the systemd functions that are required to run the helpers without actually using the init service. This means that SvsVinit remains the default init yet MX Linux can use Debian packages that have systemd dependencies such as CUPS. This approach also allows the user to retain the ability to choose his/her preferred init. A basic method of enabling systemd in MX Linux is provided in the MX/antiX Wiki, though no official support will be provided for users who choose to run MX Linux using systemd.
MX Linux is fundamentally user-oriented, so includes a certain amount of non-free software to assure that the system works out of the box as much as possible. Examples:
The “wl” driver (broadcom-sta) and non-free firmware with proprietary components
A dedicated tool for installing Nvidia graphic drivers
Adobe Flash Player (distributed by permission)
Our rationale: it is much easier for advanced users to remove these drivers than it is for regular users to install them. And it's particularly difficult to install a driver for a network card without internet access!
The name "MX Linux" is covered by LInux Foundation Sublicense No. 20140605-0483, and cannot be used in any form without our permission. Anyone distributing a respin that we do not host may only use the name for a website, ISO or download site in a manner that specifies a respin, like this: developer_mx-respin_version. Furthermore, you should specify clearly somewhere that your products are based on MX Linux but are not connected with it in any official way.
- Help: MX Forum
- Development Team: devs AT mxlinux DOT org. Not for support, use Forum instead.
- Documentation: manual AT mxlinux DOT org