I generally only reboot for stuff like kernel updates.

Saw the .de domain and my first thought was this was about using a potato ricer to make spätzle. I may not be normal.

keywords have some rules
need to use the Booles
that’s the way I type it baby
I don’t want to scroll forever

(search fu up-grades)
(search fu up-grades)

What tips/ideas do you have for getting better at navigating the terminal, and getting a better understanding of how the os works

Running an OS as a virtual is liberating. Dive in, make mistakes, fix them (or not and have to reinstall or redo from the last save). No real consequences for exploring.

distrohoped

This should be a word. It would mean “trying yet another flavor because it might be The One”

My father switched to linux (Mint, I think) in his 70s. I was in another state so he did it solo. He had a few questions but otherwise it was smooth sailing.

Traditionally I’ve been running lighter desktops like opebox, xfce, or lmde. Last couple of years I’ve been using MATE with good results.

In my country that would cost me 20 dollars

The first RAM I bought (SIPP for a 386-16 IIRC) was $50/MB. Jay-sus.

nowadays Mint is Ubuntu with sane default settings that will run out of the box

There’s also an official version of Mint based on Debian (LMDE)

What’s on your “Everyday Carry” USB stick?

• scans of my DL and other licenses
• scan of my DD214
• system rescue ISO
• a TEMP dir with random things I need in the short term
• portable apps versions of putty, WinSCP, etc.

Do normal people who don’t do this stuff for a living use Linux now, outside handheld gaming devices?

I run into folks using linux fairly often in tech hobbies. Ham operators, DIY solar folk, people dorking around with a RasPi, etc. And some Normals who want a lighter experience than Win.

Last dedicated windows box I ran at home was Windows NT 4, IIRC. Last time I had to use it at work was Win7 (?) before I retired. I do have a Win7 virtual somewhere around here I spin up every couple years to run something obscure I can’t get to run in WINE.

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?

the stove over to induction next. I hate it when the batteries fill back up by 10am and I waste solar meanwhile I am still buying propane for the appliances.

It’s possible. For the 11 months I’ve been cooking from excess solar power (December is a little short). I still carry propane for heating and a few things that seem to work better over flame.

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. :-(

“You’re not the boss of me” :-)