Really shooting from the hip on this one, huh?

I don’t know of anything like what you’re looking for, but I have been using CachyOS for over a year now and I really like it. If you’re looking to get the most performance out of your machine for gaming I wouldn’t think you’d want such a stable release like Debian anyway.

Edit: like the other poster mentioned, I never did any testing or anything, but I also didn’t notice any major improvements when I switched from vanilla Arch to CachyOS to be fair.

I will put in the time and effort to migrate to this from proxmox eventually.

I’ve only played the demo for this one (and liked it), but the first one is amazing, and there’s a good chance this will be my favorite series of games ever if they continue to make them. Very excited to play this.

Can you not use the same keys for multiple devices like you’d normally be able to?

Truly one of the most embarassing things I have ever seen someone share publically.

Over polite comments responding to an opinion about a video game.

The product was an LLM.

I never switched to Proton for exactly this reason. I’d much rather use a service that does one thing really well than one that does 20 things okay.

It’s all just to keep you locked into your subscription. Now they want you to keep other money tied up in it too.

I guess we’re starting to run out of video game titles already?

The issue is that the docker container will still be running as the LXC’s root user even if you specify another user to run as in the docker compose file or run command, and if root doesn’t have access to the dir the container will always fail.

The solution to this is to remap the unprivileged LXC’s root user to a user on the Proxmox host that has access to the dir using the LXC’s config file, mount the container’s filesystem using pct mount, and then chown everything in the container owned by the default root mapped user (100000).

These are the commands I use for this:

find /var/lib/lxc/xxx/rootfs -user 100000 -type f -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type d -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type l -exec chown -h username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type f -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type d -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type l -exec chown -h :username {} +

(Replace xxx with the LXC number and username with the host user/UID)

If group permissions are involved you’ll also have to map those groups in the LXC config, create them in the LXC with the corresponding GIDs, add them as supplementary groups to the root user in the LXC, and then add them to the docker compose yaml using group_add.

It’s super confusing and annoying but this is the workflow I’m using now to avoid having to have any resources tied up in VMs unnecessarily.

I’ve been doing this for at least a decade now and the drives are just as reliable as if you bought them normally. The only downside is having to block one of the pins on the SATA connector with kapton tape for it to work.

We do, standard contract law. If your contract says you should be getting credit, and you aren’t given credit, that’s an enforcable contract violation.

Damn I forgot no content existed online and could be profitable before YouTube came along and saved us all from the dark ages.

Exactly, then it could have just been a text list on a webpage and we’d all be better off.

Acts as a wildcard for any directories that exist between arteries and clot.

I’m pretty sure Fooyin meets all these. It’s still very early in development but I like it more than any of the other native Linux music players I’ve tried.

You’d be surprised how often none of that is touched, and I really doubt any repackers are bothering to block any network calls if the original scene release didn’t. I’ve used some equivalent of OpenSnitch that prompts on all network requests that I haven’t explicitly allowed already for the past decade, and at least 90% of all games I downloaded during that time tried to phone home.

ALWAYS set firewall rules to block internet access to any software you pirate.

A series whose last entry ended with revealing infinite accessible alternate universes has nowhere left to go? Also, a series whose entire reason for existing was to be a spiritual successor to System Shock now needs its own spiritual successor? Why?

Someone made something up about you once, so now your plan is to never be introspective again for the rest of your life?

Good luck with that. I’m sure the issue in that situation was definitely how self-aware you were at the time.

I like the workflow of having a DNS record on my network for *.mydomain.com pointing to Nginx Proxy Manager, and just needing to plug in a subdomain, IP, and port whenever I spin up something new for super easy SSL. All you need is one let’s encrypt wildcard cert for your domain and you’re all set.