██████╗██╗   ██╗██████╗  █████╗ ███╗   ██╗███████╗
██╔════╝██║   ██║██╔══██╗██╔══██╗████╗  ██║██╔════╝
██║     ██║   ██║██║  ██║███████║██╔██╗ ██║█████╗  
██║     ██║   ██║██║  ██║██╔══██║██║╚██╗██║██╔══╝  
╚██████╗╚██████╔╝██████╔╝██║  ██║██║ ╚████║███████╗
 ╚═════╝ ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚═╝  ╚═══╝╚══════╝

Cudane is a Linux distribution engineered around a direct Wayland-first architecture built for developers, advanced desktop users, and low-overhead system design.

Built around a musl-based stack, Cudane removes unnecessary GNU-heavy dependency chains, relies on a fully modern graphics path, and organizes the system into clearly separated frontend, compositor, userland, and kernel layers.

Highlights

Feature	Description
Quickshell Frontend	GPU-accelerated desktop components using QML and OpenGL.
Pure Wayland	Built around Hyprland with no legacy display abstractions.
MCX Package Manager	Parallelized dependency resolution compiled for musl-libc.
Systemfs Layout	Custom system/* hierarchy maintained by Cudane.
Linux-Zen + XFS	Low-latency scheduling with parallel filesystem throughput.
Calamares Installer	Integrated deployment workflow with Plymouth and rEFInd.

Architecture:

Cudane follows a direct stack model where every layer communicates with the next with minimal abstraction.

x86_64-linux-musl

Target triplet defines a highly optimized software architecture where x86_64 indicates the 64-bit instruction set architecture for modern Intel and AMD processors while linux specifies the underlying operating system kernel that handles direct hardware communication and process scheduling and finally musl represents the lightweight independent C standard library that acts as the clean minimalist bridge between your programs and the kernel by implementing essential system calls with ultra-low memory usage and strict POSIX compliance to completely replace the heavy standard GNU C Library.

1. Frontend (Quickshell)

The desktop interaction layer.

• Built with {QML} / {OpenGL}+{Vulkan}
• Uses {Layer-Shell} for compositor-level integration

2. Compositor (Hyprland)

The Wayland rendering layer.

• Direct GPU communication through {DRM}/{KMS}
• Input management through {libinput}
• GTK 3/4 customization via {nwg-look}

3. Userland Logic (MCX)

The package and dependency layer.

• Secure parallel package transactions
• Compiled for {musl-libc}
• Independent from glibc-heavy runtime stacks
• Includes {Calamares} integration

4. Kernel Space

The hardware execution layer.

• {Plymouth} boot rendering
• {rEFInd} boot management
• {XFS} for parallel I/O throughput
• Systemfs custom hierarchy
• Linux-Zen for low-latency scheduling

Installation

Cudane installation is handled through {Calamares}.

1. Download the ISO from Releases
2. Flash to installation media
3. Boot through {rEFInd}
4. Launch {Calamares}
5. Select storage target
6. Install and reboot

Default deployment includes:

• {Hyprland}
• {Quickshell}
• {XFS}
• Linux-Zen
• Systemfs

---

Contributing

Contributions should preserve architectural consistency.

Guidelines:

• Keep changes modular
• Maintain musl compatibility
• Avoid unnecessary dependencies
• Document subsystem changes clearly

---

FAQ

Why Musl instead of Glibc?

To keep the runtime lightweight and predictable.

Why Hyprland?

For direct Wayland-native rendering and low overhead.

What is Systemfs?

A Cudane-maintained system/* hierarchy for internal system organization.

Is Cudane based on another distribution?

No. The stack is independently structured around its own architecture.

---

Credits

Myden - Cudane Founder. | Made with 🤍 and C/C++.

Built for Creators, By a Creators.