It’s been about a month since the release of Crux 2.7, and technically I still have two machines I haven’t upgraded.
Or maybe I should say one and a half. Half because the Mebius is usually bouncing between operating systems, off in la-la land, testing a wild and bizarre distro du jour.
So yes, I do have a backup Crux 2.6 system written as an image file, and when I want that system to work as I like it, I write it back and do what I need to do.
But it’s already out of date, since back releases of Crux don’t get much in the way of updates. And that means the machine I rely on most is dreadfully stagnant.
But let’s be honest for a second: A meager 80Mb of memory, a lowly 100Mbit PCMCIA network card and probably three or four gigabytes of open space. Nothing critical there, that’s for sure.
And all of the hardware is so old, it hasn’t seen attention in the kernel for years. Honestly, I don’t feel like a target demographic.
Furthermore, if it’s not broke, why fix it? Short of system underpinnings and maybe an odd utility or two, there’s not much I have in the way of installed software that will get updated very often.
On top of that, building a new system would be a little bit of a pain … and maybe this is why I am really so hesitant.
Back when I had the Celeron in the house it was the surrogate for the CF card while I installed Crux. Running the CF card to the adapter to a USB enclosure didn’t work. I don’t know why.
But it means that I would have to replace the CF card in the Mebius, build the new system in an emulator, boot the Mebius to a live environment (thanks, Slitaz Base), write out the system across USB, reverse the drive arrangement again, and then troubleshoot.
Once more, for emphasis: And then troubleshoot.
That might be just a little more intermediary steps than I like. If I can commandeer another, faster mid-grade IDE-driven machine, I might go for it, but for now, 2.6 is just fine.
I think. …