Neonatox
← Back to home

History

NeonatoX wasn't born because Linux was broken.
It was born because I truly wanted to understand it.

For many people, free software is just "using free stuff." For me, it always meant something deeper:

  • The freedom to modify.
  • The freedom to build.
  • The freedom to understand what's really happening inside the machine.

I didn't want to install a distribution. I wanted to experience those freedoms firsthand.

Neonatox - The beginning

The beginning: From VegnuX to NeonatoX

It all formally began in 2007 with the publication of the Manifesto 0.1.0 of the MKL/VegnuX project (Venezuelan GNU/Linux eXperimental Project). This was the first initiative to develop its own distribution, guided by the principles of free software, source code availability, and experimentation.

Over time, the project's vision evolved. VegnuX became the "banner" or umbrella for a broader set of free software initiatives and projects. Within this growing ecosystem, the distribution itself needed its own distinct identity.

Everything changed the day I discovered Linux From Scratch. At first it was just copy-pasting commands. But at some point, it clicked. I stopped following instructions and started understanding why things were done that way: the toolchain, glibc, the kernel, the paths, the environment variables…

That was the moment Neonatox stopped being just a crazy idea.

Linux From Scratch - The beginning

Origin of the name and the transition

It was in this context that NeonatoX was born. While VegnuX covered more general projects, NeonatoX consolidated itself as the specific name of the distribution. The first official milestone under this new identity was the release of NeonatoX Cañaverales 0.48.0 in April 2009.

This name change not only marked a new stage of maturity for the distro, but also helped clearly differentiate it from other local initiatives with phonetically similar names (such as Venenux), consolidating its own memorable identity.

The name Neonatox came up in a conversation with my brother. I was explaining that I wasn't modifying any distro, but creating something from scratch. Then he said:

"It's like a neonate… but with an X" → Neonatox

A system being born from scratch, under the wing of the VegnuX project, but with its own personality.


First versions

The first versions were a beautiful disaster. No package manager, everything compiled by hand. I especially remember compiling XFree86… it was traumatic.

That experience made it clear I needed modularity, reproducibility, and real control.


nhopkg and the community

Then came one of the project's pillars: nhopkg.

Originally created by Jaime Gil for his project Nhoax, this package manager was simple, understandable, and adaptable. When Jaime left the project, I decided to continue it and adapt it to Neonatox.

Development was transparent and iterative. Historical records show how it went from a manager that "resolved some dependencies" to the creation of pynhopkg (a Python tool for managing package sources), thanks to community collaboration. Developers such as dominuskernel and Nehemías Velázquez contributed to the installer and the manager, demonstrating the community spirit of free software.

nhopkg - The package manager

The pause

Like almost all personal projects, Neonatox also had its winter. Years where real life won. The project froze, not from lack of desire, but because it simply wasn't the right time.


The return (2023)

When I came back, I did it with a different mindset. With more experience and clarity. What was once a messy experiment began to turn into something more serious and structured.


Philosophy and pragmatism

At the beginning of the project, the vision was strict: using linux-libre as the only kernel option, maintaining absolute purity of 100% free software. It was an invaluable learning stage and a principle we will always respect.

However, over the years and with the rapid evolution of hardware, reality imposed itself. Keeping a system usable as a daily-use machine without proprietary firmware (needed for Wi-Fi, modern graphics, or certain peripherals) became unfeasible, even for me as a developer.

NeonatoX evolved toward a more pragmatic approach, but without betraying its roots. It's not about abandoning the ideals of free software, but balancing them with technical reality. Anyone who wishes to keep a 100% free system still has that option: the free kernel, along with its sources and binaries, remains completely available in our repositories.

Today, the project seeks to offer a system that truly works in the real world, being fully transparent and giving the user total control to decide what they install on their own machine.


Today

NeonatoX is, above all, a puzzle.

It's not just another distribution. It's a platform to learn, break things, rebuild them, and understand how an operating system really works.

And it's still here. It wasn't abandoned.
It was just waiting for the right moment.

Neonatox today

Historical references