Good soundtrack, at least in the first one.

That zip file contains an rpm package that has the PPD files. You’ll need to be on an RPM-based distro to install it as-is, or use a tool to unpack it.

What distro are you running?

Nope.

Hate to keep litigating this around here, but the shift alone is enough. Explaining to people WTF an immutable filesystem is, is a sure way to frustrate them into giving up, despite whatever comms finesse you might THINK you have.

Counterpoint: STOP SUGGESTING IMMUTABLE DISTROS TO NEW USERS

For people who just want a functional OS, they don’t want to have to think about new rules. They need a quick off-ramp from Windows that acts as they expect.

Package management is already enough of a mindfuck for people switching, then you’re throwing in containers, permissions, flatpak vs native packages, what sandboxing is, why your browser likely can’t just upload a simple fucking file, and why your camera doesn’t work on Zoom, because you have a meeting in 10 minutes.

Unless you are handing people something akin to a mobile OS with everything all inclusive and configured so EVERYTHING works off the bat, you’re doing such a huge disservice to people switching over to an immutable distro, and there is ZERO benefit, but all kinds of added frustration.

You need to stop, and I yield my time.

Meta never acquired my VR Mansion. It was super cool.

Dafuq

Never go to a second location, let a third.

You in trouble.

Same way you made it work on Deck, again. SteamInput will map controllers to input devices detected by Dolphin, and you map to whatever you need to map to in whatever way you want.

Same as it is on Deck. It’s just a Deck in a different form factor from the user standpoint. Everything will operate the same.

Quite awhile ago, but that’s not the barrier here.

The PS5 is essentially just a PC anyway, you just need to get through the Hypervisor BS as this guy did. It has AMD CPU/GPU inside, so it’s just a matter of making the kernel drivers detect what I imagine to be standard AMD RDNA2, but a custom identifier GPU detect and go to work.

Nice job though.

Literally nobody in the consumer market will care, and the DC crowd won’t buy this until they can prove failure rates.

It’s not that we don’t know what it is, it, again, is just INCREDIBLY FUCKING STUPID.

This is… incredibly stupid. This man has done so many drugs he no longer realizes how computers or electricity works.

ETA: https://www.reddit.com/r/answers/comments/23nd6a/i_remember_in_the_90s_illegal_or_black_box_cable/

Sounds like you need a client that does “multiparty uploads”. Meaning interruptions should continue if there is a break in comms.

All the Cloud endpoints support this, you just need a better client. Do some research I guess.

No, it’s not.

Do your initials happen to be NCAA?

Why don’t you just fucking kill me, and replace me with an AI copy of myself. What a dumb fucking world these companies are pushing for.

Jackasses.

Whoever did this was incredibly lazy. What you using an agent to run your Terraform commands for you in the first place if it’s not part of some automation? You’re saving yourself, what, 15 seconds tops? You deserve this kind of thing for being like this.

Nah, it’s not that risky if your tooling and process is solid. I have thousands of edge devices out in the field doing firmware updates on carrier boards from a specific manufacturer and have never had one fail or brick in update. Why? Because their tooling is absolutely fantastic and pretty bulletproof.

Even a simple {checksum>transfer>checksum>write>checksum} is pretty safe, UNLESS…you know the carrier you’re flashing doesnt have the ability to do so, in which case, you definitely put a warning like this on your product because you know it has a penchant for failure.

When they do this, they know they have a problem with their flash utils and process 🤣

I’d leave it alone.

Never seen that, and I build with hundreds of variants from all the big manufacturers. Haven’t seen that once in a PC, Laptop, or SFF.