run0 is the new sudo su

Systems/Journald keeps 4GB of logs stored by default.

):

It’s priceless

I actually have my ~/.cache mounted as a tmpfs. No need to write that to disk when I have like 50GB of free RAM most of the time.

“Free” memory is actually usually used for cache. So instead of waiting to get data from the disk, the system can just read it directly from RAM after the first access. The more RAM you have, the more free space you’ll have to use for cache. My machine often has over 20GB of RAM used as cache. You can see this with free -m. IIRC both Gnome and KDE’s system managers also show that now.

So the 3rd dragon should just be /dev/nvme%d

Or they just use a distro that doesn’t frequently break dependencies. I used to experience lots of dependency issues on Ubuntu many years ago. Been on Arch for ~10 years and have only had 1 dependency issue, which was fixed within 1 day.

Did that cause breaks on certain distros? No issues with it on Arch.

That requires podman or some other program.

No, systemd-nspawn doesn’t need any other container management program, it’s its own thing.

Flatpak uses polkit for permissions. System level flatpak updates are typically permitted without password by polkit but only for local users. For SSH, most flatpak operations require a password, so it’s a mess if you try to run an update on system level flatpaks without sudo, which solves OP’s problem. They could also move everything to a user level install, which IMO makes more sense for flatpaks than the default system level mode.

Which is what flatpak will always do unless provided with the --user flag.

Because he tried to update a system-wide flatpak install as a non-root user. Flatpak uses polkit for root permissions. Polkit is usually set up to allow non-root local users to update flatpak without a password, but not remote ones, hence having to continually enter the password for polit when using SSH. He could just run the update with sudo like a normal package manager and would only have to enter the password once. But then he wouldn’t be able to complain on Lemmy.

It sounds like you’re trying to update system-wide flatpak packages as non-root. Most distros use polkit to allow you to update those without a password from the desktop (i.e. a local user), but usually require a password for remote users (like ssh). Just run as root: “sudo flatpak update”.

You could also migrate to a user flatpak installation instead a system-wide one. That’s what I’ve done. IMO that’s how it should be done, but that’s not the default on most distros for some reason.

The developer has to specifically allow it though. Epic themselves don’t let EAC for Fortnite run on Linux because they don’t trust it as much as the rootkit version that only runs Windows.

Did you not read his post? He is absolutely taking a shit on all the engineers. You can ask for help without cursing at and insulting the work of the engineers.

Yeah, I love Arch for the same reasons. Try installing it in a VM and using it a bit, and you’ll see that it’s quite an easy OS to use now.

Don’t you need a second GPU for passthrough?

Isn’t that only for Linux guests?

Do you have it on Steam? It should work if you use the Windows version on proton instead of the native Linux version.