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.

https://feddit.org/post/7894572 earliest post I could find. It’s a clever exploit, but it was patched 3 days ago.

Reading about the Tulsa race massacre is so crazy, like World War 1 planes, some say up to 12, others at least 8 of them doing stuff like: “… turpentine or nitroglycerin bombs being dropped and men shooting from planes”. Some also suspect the use of dynamite, so it’s possible they were quite literally dropping bombs.

Fuuuuuck… I was really hoping I didn’t need to migrate away from gmail… But looks like this is it.

“Bloody Just Stop Oil protesters blocking the road, preventing me to go to work just so they can spread the message that we’re all going to die! I HAVE A MORTGAGE!”

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.

That’s actually really cool. I like that the dev has expressed that he doesn’t want to make the algorithm addictive and just keep it random 😅

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.

Took me a little while to figure out where to put the .ipk3 file (easiest is ~/.config/gzdoom) but otherwise easy enough to get going using the flatpak version of GZDoom. Installing the regular gamefiles + spear of destiny (from my GOG version) was also pretty easy, but I wonder where one can get Return to Danger and Ultimate Challenge 🤔

Either way, good shout, plays excellently, although seems like hitting enemies is harder in this version than the original, at least when they’re far away.

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.

Like @prole@lemmy.blahaj.zone said, there’s a flatpak PS4 emulator that makes it trivial to apply the patch, as demonstrated here.