I installed Ubuntu the other day, wiping out my long-standing Crux installation and putting the whole Gnome suite on my Inspiron. I did it for three reasons — first, I wanted to give Ubuntu a few tries, after opening my network to rsync, torrent and other traffic. I don’t have any particular insights to offer, but it was important to see the whole Ubuntu Hardy sphere working without networking restrictions.
The second reason was to install Gridwars 2, which I mentioned in a previous post. That has proven to be both a blessing and a curse — great game, serious time consumer though. It’s either good or bad, as always, depending on your perspective.
The last reason was a pie-in-the-sky idea that I might be able to hijack my Ubuntu installation and hotwire it Crux-style, compiling a very sparse kernel and kicking it straight into bash with something like
init=/bin/bash, and whatever else was necessary to make it work.
It was getting a little hairy though, and I admit I didn’t have enough desire to see it through. I downloaded a kernel, then needed build-essential. Then I needed ncurses-dev just to run
make menuconfig. And a mess of options had been enabled and I didn’t have the time to wade through them all.
In the end I just scrapped the idea. I knew I was going to run into a lot of other problems and I didn’t feel like disentangling Ubuntu when what I really want is Crux’s speed and efficiency. Like I mention in the guide, I really don’t see the point in hacking down Ubuntu to make it superfast, because it defeats the purpose of using Ubuntu at all.
So I’m compiling right now, but I’m doing it in Crux again, where I feel the effort is well spent. I could probably go through the steps making Ubuntu work like Crux at the core levels, but it wouldn’t be Ubuntu any more — and I’d have to jump through so many hoops, it wouldn’t be fun.
And if it ain’t fun, I ain’t interested. 🙄