Frater Mus

Was it mainly a hobbyist thing at the time

Yes, I’d say so. Lots of tech geeks were playing with it but no Normals. Getting audio running was not always pleasant…

When I was in the army the S1 desk jockeys were using dedicated word processors with 8" floppies. Get off my lawn! :-)

Wireguard self hosting

I parsed this as Wireguard self-loathing and thought “that’s a little harsh”. :-)

warning: some non-linux included below

• minix
• slackware
• early Debian
• FreeBSD (ftp installs instead of 20 floppies! OMG!)
• Debian
• Crunchbang <-- loved that original project
• Solaris (friend gave me a Sparc 5)
• DSL, Puppy linux (had a tiny netbook)
• **Debian on workstations and servers since ~2014 **
• various debian-based distros on RPI

I do spin up other distros in a VM from time to time to see what’s what. Most recently NixOS since people won’t STFU about it. :-)

I’d rather mods who don’t want outside participation to be able to stop their communities from showing in All.

Agreed. Niche communities can get hammered with downvotes and “I don’t want to read this” comments from readers of ALL.

It’s confounding: “show me everything”, then “I don’t like the content in your niche community”. WTF?

In the past I’ve aliased rm to a wrapper that showed PWD and the files to be affected, slept a couple seconds in case I wanted to abort, then shredded smaller files, rm’ed big files, or placed in a Trash dir for certain kinds of files (.conf, .cfg, etc).

I might try to find or rewrite it.

I have made countless mistakes since the 90s, mostly involving rm. The most recent one was yesterday when I was trying to rm files in a directory with lots of other unrelated files.

I don’t remember the exact failure, but I was shooting for something like rm *lng and typo’ed rm *;ng (those chars are next to each other on the kb). This happily rm’ed * (d’oh!) then errored on the nonexistance ng. :-(

Agreed. I haven’t read the article yet, but my first thought was “how am I going to turn that off”

Can’t find it now, but someone once made a vi [gVim?} version with a Clippy-style helper: “I see you’ve pressed ESC. Would you like to…”

any idea why distrowatch periodically goes down for days before returning.

My guess is it’s run as a hobby by A Guy “on his own time and his own dime”.

I mainly use it to find out if some distros have updates to their ISOs but I find it very annoying that quite frequently it’s down completely.

You might follow the RSS feed. Your feedreader would catch new posts whenever they are available.

the site is still up, at least.

In the early 90s I was running a BBS on DesqView over DOS and was annoyed by the limitations. My older hardware didn’t have grunt or RAM (SIPP at $50/MB) to run OS/2 like the big dogs. I also had nearly no money (grad student).

I started experimenting with MINIX, and from there to linux. IIRC I started with Slackware, flirted with Red Hat, then found Debian and it was true lurve. Since that time I’ve generally run servers on Debian stable and workstations on Debian testing.

Am I just old or is 4GB actually loads or RAM?

First stick I bought was 1MB of SIPP, used, for $50.

“When I was a boy we had to load HIMEM and EMM386 uphill in the snow”

In the late 90s I taught an intro course for folks who wanted to run *nix boxen (Solaris, IIRC). On the afternoon of the last day I had them swap places after lunch and gain root access to each others’ machines. It was partly for root passwd recovery and other maintenance tasks, but also to demonstrate that physical access to the box was a serious issue.