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.

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.

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.

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.

That’s not a bad shout at all. It does hide æøå on weird keys though, would take a lot of practice to get used to that, but I’ll definitely put that layout into the layout rotation, thanks for the suggestion.

The alt gr + ß is probably the same for nordic keyboards, the one below A. It’s <>\ for me, but afaik both < and > are also individual keys on a US keyboard. And then there’s ~. But I guess you get used to dead keys.

Shift+7 feels wrong for some reason, so I currently tend to just send my pinky on a kamikaze mission towards the numpad hoping I hit /. Sometimes I hit numlock, sometimes I hit *.
Even if I made a compose key “shortcut” via ~/.XCompose it’d still be more work than what I’m doing already.

Macro pad could be a solution, I have considered it beforehand for other purposes tbh

If you know what a nordic keyboard layout looks like, you’d probably prefer backslash. Since I moved to Linux a year ago I’ve been struggling to find the easiest way to forward slash. Shift + 7? Or numpad / with my right pinky?