Jump to content

Recommended Posts




Maui features an alternative to traditional packages. The system image is built from a well defined set of upstream projects, tightly integrated and managed as a single well-focused project. During a system update only what's really changed between two version is deployed. The update system also has the ability get back to a previous version if something doesn't work and then go forward to a new release when a fix is available.





Hawaii was born to take advantage of what Qt, QtQuick, Wayland and systemd offer.


Wayland is the most exciting piece of technology for the Linux graphics stack in years and Maui is the first Linux distribution to use it, in fact Maui couldn't be done without it.







Maui is a GNU/Linux-based operating system focused on desktop experience and ease of use with a look to the future.

We want to offer a lightweight and modular desktop environment with a user interface tailored for the device (desktop, tablet and even phone) on which it runs.

We also want:

  • Safe, atomic and fast upgrades
  • To maintain API/ABI compatibility between point releases
  • Develop a platform rather than a set of packages

Packages have a central role in most general-purpose GNU/Linux systems but for our goals, packages lead to fundamental architectural conflicts.


This project seems to have a lot of Arch luuurve in the background as there are Arch packages available for Hawaii.

I'm fascinated by Wayland and have been ever since I saw a video of it in action over at Phronix. Downloading the .iso now and will be trying Maui out on a usb stick sometime over the weekend.

Wonder how it will fly ?





Edited by abarbarian
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...