This is not going to be a super long post, but it will be an informal roadmap of AxylOS as of today, 10-27-2024.

Where has AxylOS been?

AxylOS has been dead for a few years now, it has not seen an update in a significant amount of time as of this writing, and I am going to explain that in this post.

When AxylOS saw its last release a few years ago it was based on Linux-Standard had a collection of X11 Window Managers with some really sick themes. As it stands right now AxylOS does not have a kernel, and will ship with Hyprland and a collection of GUIs that will allow you to graphically configure the environment.

What are these GUIs?

• HyprGUI
• Hyprwall
• HyprSettings
• Graphical Recovery Environment

HyprGUI

HyprGUI is a graphical piece of software that will allow you to graphically configure the file hyprland.conf located in ~/.config/hyprland/hyprland.conf it is written in Rust, and you can find the sourcecode here:

GitHub - nnyyxxxx/hyprgui: GUI for configuring Hyprland, written in blazingly fast Rust! 🚀🦀

GUI for configuring Hyprland, written in blazingly fast Rust! 🚀🦀 - nnyyxxxx/hyprgui

GitHubnnyyxxxx

Hyprwall

Hyprwall is a graphical piece of software that will allow you to set your wallpaper using the wallpaper manager of your choice, this is a setting that is located in either ~/.config/hyprland/execs.conf or ~/.config/hyprland/hyprland.conf Depending on the way you choose to set your configuration up, you can find the source code here:

GitHub - nnyyxxxx/hyprwall: GUI for setting wallpapers with hyprpaper, swww, swaybg, wallutils, and feh. Written in blazingly fast Rust! 🚀🦀

GUI for setting wallpapers with hyprpaper, swww, swaybg, wallutils, and feh. Written in blazingly fast Rust! 🚀🦀 - GitHub - nnyyxxxx/hyprwall: GUI for setting wallpapers with hyprpaper, swww, swayb…

GitHubnnyyxxxx

HyprSettings

This will be a replacement for something like Gnome Settings and will allow you to set things like dark mode and your default browser, default text editor, and more. The Source Code for this is not currently available

Graphical Recovery Environment

This is going to be something in a class all of its own, We are working on a Rust MicroKernel, and at the same time we are working on a Graphical Recovery Environment that will work with the Kernel and the FileSystem to allow you to boot into "Safe Mode" and role your system back to a different version without loading anything that will break your system further. The Source Code for this is not currently available.

What is that MicroKernel?

Yes, I keep mentioning a MicroKernel that we are working on, one that is written in Rust, and the main reasons we are doing this are as follows:

• Move Drivers out of KernelSpace
• Make a Kernel that is much more stable, secure, and requires less updates
• Make a Kernel that we control and will push the developement of our Graphical Recovery Environment in a way that we can maintain, making it easier for anyone who wants to use our operating system.

Why are you doing this again?

There are a handful of driving reasons behind our move to a MicroKernel, one of these reasons is a higher level of control over the kernel, its features, and when updates are pushed.

A bit of background, I am the half owner of a relatively new company, called AlphaTek, the founder and owner of Axyl Projects, and as of recently the owner of a Gaming company called rootCORP Games, which you can read more about on the website embedded below. All of these companies focus on Linux, or more specifically the open philosophy of linux, and the ways that we can support people in their use, management of, and move to the Linux, and Open Source Ecosystem. From the Tools that we are building into AxylOS, to the rootCORP Games Anticheat, to our drive to make Minecraft more usable on Linux Computes, we want to make Linux and OSS a more open, welcoming, and friendly place.

rootCORP Gaming

rootCORP Gaming is a Linux Focused Gaming Company

Axyl Projects

Official Site for Axyl Projects

Axyl Projects

With that in mind there is our Drive to produce a Kernel that does a few things,

• Moves Drivers out of Kernel Space, and into a space that is made only for drivers
• Converts the Kernel into a more Modern, secure, and maintainable language, that has more room for other languages to be used to augment the kernel in the future, this language being Rust.
• Work on more Secure ways for the Kernel to interact with the Operating System
• Remove a lot of Code that is old, out of date, and poses a security risk the longer that it remains in active systems.
• Make a kernel that works better with our Graphical Recovery Environment

We have tried several different approaches to making a kernel that works well with what we are doing, but at the end of the day it came time to call in what I like to call the "Nuclear Approach" and that is to scrap everything we had been attempting and start fresh.

What does this mean for AxylOS?

This is a Good Question, and to be honest it means a lot, AxylOS will be delayed a while in its release but it means that when we do release it the Operating System will be in a class all of its own. Secure, Stable, Accessible, and most of All, Beautiful.

If you have any questions, would like to help, or simply want to show your support, the AxylOS Discord Server is linked below. Hope to see you there.