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.

I use an extension which bundles 5 different solutions in one called PaywallHub. I hasn’t been updated for a while because it got hit by takedown notices, but the chrome extension and firefox addon repos are still available, you just have to install it a bit more manually: https://github.com/Angeloyo/PaywallHub

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.

The good thing about an nvidia driver update is that it forces you to take a backup. And hey, I figured out how apt-file works just so I could figure out where the nvidia driver put nvidia-settings (as it forgot to put it somewhere $path could find it, and no .desktop files were made).

It’s taken from the excellent 1998 anime “Serial Experiments Lain”. It’s so iconic, excellent intro (OP) theme. But a bit surreal, it’s kind of Lynchian in a way.

Tbf, disabling systemD autorun is the only thing I’ve ever user kwriteconfig6 for, because with it enabled bash scripts don’t run correctly.

Only thing I’ve had to edit in the terminal in the last several months has been automount on a hard drive.

I just use gnome disks for that. Tbh, that’s the only thing I use gnome disks for.

I don’t mind using the terminal, but how the fuck am I going to remember something like kwriteconfig6 --file startkderc --group General --key systemdBoot false? (In fact, there aren’t even man pages for that command). Like the scribbles of a mad man I’ve had to put down commands like that in a sort of personal instructions manual, because ain’t no way I’ll remember these commands by heart.
And you often end up just saving the most used commands as aliases or functions in the .bashrc meaning you don’t retain the syntax for the commands you use. Well, maybe I’m a unique case of fish memory… The thing about humans is that we greatly rely on our vision, and having GUI’s to show what’s possible greatly improve ones understanding of how to manage it going forward.

Thanks, this seems like a very thorough description of the situation. My limited understanding of how coding works and has worked through history is like you say “filled with a lot of jank” regarding memory because it was limited but also because compilers weren’t as efficient as they are today. So it makes sense that there are purists that believes the only good code is the one where programmers are in total control of every bit of memory themselves instead of leaving anything to automation.

Classic. But yeah, that’s how I’m reading the situation as well.

Some of the comments on that article made me realise I’m a bit out of the loop: what makes Asahi linux “woke”?
It is sad though that there is so much drama around linux development. It’s easy for me to say this, but I do think it’s important that there is a switch to a newer language like Rust away from C eventually.

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.