That doesn’t give me a memorable mnemonic though.

tar -eXtract Ze Vucking File

It doesn’t seem very useful

You could use an alternate repo, like the fedora one which is curated to only open source software

Element 0 is the first element of the list

Before killing yourself, it’s your responsibility to kill your children

*char // I heard it from a friend
**char //who heard it from a friend
***char // who heard it from another
"You were messing around"

In the end, clearing my shader cache seemed to fix it

In the event someone else runs into this, go Steam>Settings>Downloads>uncheck “Enable Shader Pre-Caching” then check it again

Nevermind, still poor performance

The interface “running” is one thing, but does it know to run games in wine/proton? Does it know to grab the Linux versions of games if available? Mono doesn’t make that automatic.

Does this work well on Linux? Looks like it’s dotnet based

Also, the readme says it requires windows

Don’t use jellyfin.server.local

.local is reserved for mdns, which doesn’t support more than one dot. (Though it may still sometimes work).

In any case, to make that work you need either a DNS server on your network or something like duckdns (which supports wildcard entries).

You might be able to get the same hash if you did a backup of the disk in iso format. It doesn’t matter though since you wouldn’t be able to use that format to play anything.

All that to say that these seem to be the wrong tools for what you’re actually trying to do.

If you’re keeping the files as mkv, you’re reencoding them.

Also, if you’re reencoding the files, it’s extremely unlikely for your hash to match someone else’s

So, an aspect

makes software for pirates

please avoid pirated versions

Good luck with that.

Good luck! I’ve been very happy with my microos installs. I’ve got kalpa on my desktop and aeon on my laptop. I’m following a project that uses a microos base for the Steam Deck too (which is ironic since the steam deck is what made me aware of read only root Linux and flatpak in the first place).

I didn’t, libraries are stored in different places in flatpak vs native install. You could probably add the normal install location in the flatpak using flat seal, but having the install directory in /home (the default for flatpak) was fine for me .

For what it’s worth, I’m using steam in flatpak in microos now, and it’s been mostly seamless

I did this for a short while and didn’t run into any issues. They have their own separate libraries, though you could change that if you wanted to though.

Those are two different repositories, one hosted by GitHub, the other by linuxserver.io. both are published by linuxserver, so there shouldn’t be a practical difference between them.