While I generally agree, I must say that my Ryobi tools are doing just fine after 15ish years of use. Primarily the drill is what’s used, and it’s seen some shit but aside from a little cosmetic issue (rubber peeling off here and there) it’s in great working order. I can afford better now, but I’m happy enough to keep what I’ve got.

I’m just a handy home owner, so it’s not like I’m abusing these things.

Interesting. Looks like perhaps your boot loader isn’t properly pointing at your root partition.

I’m assuming you’ve just done the install and never successfully booted, yes? In that case, you can try to re-run the installer, or try rescue mode and try repairing the bootloader.

Are you doing dual-booting, or is this system dedicated to Linux?

Yes, back in the early 00s. We toyed with making a net-bootable image with it for our computer labs, but it was really not practical. It definitely taught me a ton about systems, though.

I admit, I’m not a big fan of putting more functionality into systemd (or just of systemd in general), but that is a well-reasoned argument for having sudo live in the init system.

“No lawful way…”

I just finished saving backups of the games I bought using my (hackable) Switch, and I’m planning on setting it up w/ Yuzu on my Steam Deck.

And no one’s going to stop me from fairly using my stuff.

Same here. Seems like Google did a pretty good job with the eSIM registration in their app. I’ve swapped phones a number of times with zero issues.

Read the error again. It’s journalctl.

It’s a long shot, but I hope that they keep the exposure notification framework and work with the CDC/appropriate orgs around the world to make it a generic exposure notification. The technical feature is impressive, and the usefulness (with proper adoption) would be high for the various occasions where other communicable diseases pop up. It seems easy enough to have a generic app to add the various diseases and their incubation/transmission windows to allow others to be notified.

But, because people are whiny fucks, it’ll die and we’ll be in a rush to reimplement it for the next thing that comes up.

Even if it did exist in an ideal state, people would still not use it, because people suck.

PowerShell makes that a lot better these days. It’s still not perfect, but a lot better.

It’s not that it’s deleted automatically. If you define deleting as “not being referenced by the file system,” then it’s deleted as soon as it’s unlinked.

Fun story - create a big file, and hold it open in an application. Unlink the file. Then compare the output of du and df for the mount point the file was on. It will differ until the app closes and the inode of the file is finally freed.

I’m thankful that my kids fly well, and always have. We flew with them at ~15 months with no issues.

I’ve always heard the complaints about screaming infants and whatnot…but I’ve never seen it. Granted, I don’t fly too often (and less so more recently), but I’ve never had the “classic” kid crying through the entire flight. It just doesn’t happen as often as people think. I’m sure when it does happen that it’s pretty f’n annoying, though.

Cursory Google searches will give you driver downloads. Dell/HP can give you a pre-bundled package of drivers.

Unless you’ve got some very unique hardware (or very old), it just isn’t that difficult to figure out.

I’m all for using Linux, and I’m considering moving my desktop over from Win 10, but I’ve never had any issues with the install of Windows. If it’s any level of modern hardware, it should mostly work out of the box.

These kinds of rants really trip my BS detector, because it’s just not that complicated. If you can handle Linux but can’t manage to even install Windows, I have a lot of questions.