/C:

It exists because, long ago in a galaxy far far away, a sysadmin ran out of space on a drive. The system was split between two 10MB(?) drives, one was / and one was mounted at /usr, for User data. They moved some of the programs to a folder for a dummy user, /usr/bin, and put that in everybody’s PATH.

Everybody kept on doing things that way ever since. Social momentum is funny that way.

You can also use backports for some of the more “system entangled software” that cannot be packaged in a flatpak. Or, you can skip ahead to “Trixie” unstable. It has been great for me for the last several months. It’s arguably more stable than what Ubuntu calls an LTS.

Sometimes a wireless mouse problem is just “I also plugged in a USB 3.0 device, and it puts out so much RF noise that it’s jamming my mouse dongle and the local airport’s approach radar”.

USB can be bitchy that way.

Bazzite is broken AF on Nvidia right now, with no X11 and no explicit sync driver. I can’t wait to see if driver 555 fixes it.

Edit - 555 is out, and yes it is considerably better.

11 partitions… sounds like some of them need a nofail flag in fstab.

How much sandboxing is your distro generally doing?

If you set up flatpak as --user, bringing your home directory over would be 99% of the job.

It’s a lot to toggle off, on each computer, multiplied by every other computer that you’re connecting to. It’s too insecure-by-default.

Does it support “sending a file larger than 2 gigs, without mysteriously deleting it at the end, but if you manage to sneak a hardlink to the file while it’s transferring then it’s okay”?

KDE connect is a large suite of some good, some half-baked, and some just plain scary remote tools.

I’m liking LocalSend for the occasional “I want some files/pictures/text to go from here to there”.

deleted by creator

What’s the fuss over an “installer”? You just need a folder with the game’s files. If you really insist, that folder can be rolled up into a zip file dot exe.

Twitch dot tv

Sir, this is an AppleBees.

Btrfs, snapper, cp --reflink stuff back out of a snapshot.

Would you know a virus if you saw it?

Snaps (and flatpaks) have a much better way of handling DLL hell than good ol deb/rpm/pacman. As such, each app is better able to chase the latest version of all of its dependencies, without worrying about messing up the libraries for anyone else.

Snap/flatpak also sandbox their apps, reducing the blast radius of exploited or bad apps.

My personal preference is to use flatpak, and set it up so that it is all --user. With a --user install, you don’t need sudo to update anything. Use Flatseal to tighten up or loosen the sandbox, use Warehouse to roll back any broken updates. I don’t think snap has any tools like Flatseal or Warehouse, which makes it the weaker packager.

Anything that can be installed as a flatpak, I do it there first. Then I can just pick up my home directory, drop it in a different distro, and almost all of my stuff follows. A distro becomes little more than “a kernel, a compositor, a baseline desktop environment, and some background daemons”.

It’s a miracle that the battery is still working at ten years. The most realistic thing is to just keep up with your backups, and be ready to dispose of that laptop the moment the battery starts swelling.

TLP is my favourite tool for messing with the charge limit. And also far, far too many power/thermal management knobs.