The Asus EeePC 1000H that I bought back in 2009 is a 10 inch monitor netbook. 160 GB HDD because I didn’t go with SSD, only came with 1 GB of RAM and cruicially was offered in both Windows XP and Linux flavor which was a bit niche at the time.
Its 32-bit single core (hyperthreading) atom processor is very slow at 1.6GHz, but it can still be used with antiX for my usecase.
If you manage to get hold of one of these old dinosaurs, I’d probably opt for an SSD solution, that’s a pretty big bottleneck.

That’s a lot of choo-choo’ing

If we’re sharing silly useless projects, I quite like “activate linux”, the configurable watermark inspired by “Activate Windows”.
It’s unfortunately not a strictly terminal based goof, but wanted to share anyway.

It is nice to have guard rails like a GUI until you grasp the possibilities, that’s how I’ve learned historically coming from DOS and Windows at least, but you can still mess things up plenty with this tool.

I switched to linux a little over a year ago and went with MX Linux because they have great GUI tools for windows refugees like myself, and because they don’t like systemd over there they use cron jobs. Now, having switched to Nobara I’ve just installed both SystemD Pilot here, but also found KCron, a KDE Cron configuration module which allows for the same functionality as what I’m used to.
If I just want to setup a “when system starts” daemon, is there really any difference in using one over the other? I guess it’s possible to shut down services more gracefully?

In any case, great job on this utility.