H-Linux Preview

H-Linux isn't the first custom Linux distribution I have embarked on developing.

Previously, I had launched Nest Linux and its upstream sister build NEXT Linux.

Both ultimately lost momentum because I got lazy and embarked on a project not out of love but just because I could.

I recognize now that was a mistake.

This time, things are different.

I have the motivation and definitely more love for running a custom Linux distribution than any time in my entire career using and developing on Linux-based operating systems.

Let's face it, there's an infinite myriad of custom distributions.

Many of them unknown and will never be known to anyone outside of the developer or intended audience, which is usually niche and painfully minute.

H-Linux (or Harmonious Linux, influenced by Buddhism) is a project I created because I wanted a Linux distribution that doesn't just operate the part but looks the part.

Aesthetics matter!

It will target Linux developers and FOSS activists who want a Linux environment that is 100% customizable and standards compliant.

And something many open-source developers don’t consider anywhere near enough is licensing.

Using, sharing and redistributing open-source code is often well intentioned, however often violates license usage rights.

It might surprise people to hear me say that there is a place in the world of software for proprietary licensing of source code.

I have always been a proponent of open-source models, but have equally always been respectful of users having a choice.

H-Linux will contain some proprietary code, but not all.

And where licenses must be respected, they will be at all times.

I have built H-Linux using CachyOS as its base, which is itself based on Arch Linux.

So yes, this is a Linux distribution based on the Arch package ecosystem.

CachyOS provides us with a kernel and some added functional polish under the hood, but that's where it ends.

The rest, I have been working hard to give H-Linux its own genuine identity.

Any good Linux distribution should retain its own identity and I’ve always believed that yes, pay homage to the base build which makes your distribution possible, including respecting all usage licensing where required, but don’t let your distribution be another ‘just another derivative’.

That’s what I aim to do with H-Linux.

But not just through its unique aesthetic appeal, but in its function too.

First, it runs hwm (the abbreviation for Harmonious Window Manager), an Openbox variant and is obviously compatible with existing configuration syntax and X11 compliant.

Many of you are probably wondering why I decided to go this particular route.

A couple of reasons prompted my decision.

While some users think Wayland is the only display protocol on the future Linux ecosystem, wiping X11 into irrelevancy, I happen to believe that is not the case.

In fact, I would argue the fight for your display is only just getting started with several new projects being forked from the X11 code base and developers seemingly committed to bringing X11 into the modern era.

It's not outdated, at all.

For example, check exhibit A – H-Linux – running hwm, the picom compositor for effects and transparency still produce a desktop with aesthetics which are completely functional and efficient, and still making Apple's yucky attempt with its “Liquid Glass” look like a silly gimmick.

On top of gorgeous aesthetics, I am including luma, a desktop gauge and analysis tool based on Conky which thanks to picom, blends right into the rest of the desktop.

On top of our own branded tools are Cherry Terminal, which can be launched from inside the disks GUI file manager, with the latter having active file copy verification enabled by default.

Cherry Terminal is built on top of kitty to take full advantage of its OpenGL capability.

Cherry Terminal is complemented by Slothfetch, a custom adaption of common *fetch variants you’ll find on most custom desktops.

All of these tools might seem familiar to seasoned Linux users reading this, and that's a good thing.

Because I am not trying to reinvent the wheel here, when existing source code to achieve our goals already exists.

In time, all of the source code I am using and projects I base our own packages on will be fully credited openly and transparently.

I don't take any credit away from those that make H-Linux possible and give life to our new formed and evolving identity, in fact, in time our efforts will be a living homage to those efforts.

Our main selling point is H Core, the system menu launcher which is accessed by pressing the Ctrl+H key combination.

H Core can be launched from anywhere during system use, and is not limited to only being accessible from the desktop.

It may look similar to the old Openbox style pipe menus, and underneath it is, but with a heck of a lot of changes, not just to the theme powering H-Linux, but functional improvements which don't seem to exist in current Linux distribution offerings of the style H-Linux employs (or deploys, depending on how you look at how hwm functions under the hood).

With H Core, I have developed the entire menu launcher to not just operate and function through scripts, with Bash, Python and Perl all being supported, but the menu itself is launched via script running on the V1 subsystem, which is included and running on H-Linux by default.

Again, as far as I can tell, nothing like this exists and hasn't been done.

With H-Linux, old code has become new again with redevelopment, repurposing and reinvigorating.

Ok, so what's on your mind?

I know, I know, you're thinking "But it's still X11!". 🙄

True, yes.

But as I said, I believe not only is there a vibrant future ahead for X11.

Also, I am working to make H-Linux flexible and adaptable for a future transition to Wayland, if the need arises.

But that would only occur if it becomes unsustainable to keep using X11.

So no direction is yet set in stone and there is no development path or milestones I am working towards.

But the point I am making here is that H-Linux will be flexible in a sense that I can adapt it to the best available packages and architecture available.

I prefer X11 for now.

Should I be forced at some point to shift to a Wayland base, then so be it, there are several options and directions I could take with H-Linux should that happen, and I am actively engaging with several projects and developers about where Linux development is heading.

For now, this is closed development.

But since I have on a number of occasions written social network posts and referenced either H-Linux or hwm (or possibly even the V1 subsystem, I am not sure), I figured I may as well put it out there that these things I do talk about do actually exist and are under active development.

As I said, H-Linux at the moment is closed development and I haven't put any modification I have made into the public domain, not because I don't want to, but because they're not ready.

What you see in a screenshot doesn't show that it's only 25-30% at best complete, with many things under the hood still requiring lots of manual user intervention.

In time, more things will be automated, cutting out the necessary user intervention, as well as having installation scripts to implement changes which effectively bring H-Linux to life on the desktop.

All of this takes time.

For now, just enjoy what I show you and embrace what I tell you.

Things are happening, and I am more than happy with the progress I have made so far with bringing H-Linux to life.