Hilariously true
Hilariously true
I imagine this would be up to the application. What you’re describing would been seen by the OS as the device becoming unavailable. That won’t really affect the OS. But, it could cause problems with the drivers and/or applications that are expecting the device to be available. The effect could range from “hm, the GPU isn’t responding, oh well” to a kernel panic.
Curious how this is distinct from SimpleX.
Red Hat (RHEL) is not based on any other distro, like Ubuntu is with Debian. RHEL is downstream of Fedora, meaning that RHEL developers can work on code that affects Fedora AND RHEL. This is not really true of Debian and Ubuntu. They are distinct projects with different goals. In many ways, Ubuntu is beholden to what Debian does. This isn’t usually a problem because Debian is very conservative in its approach to software. Ubuntu doesn’t usually have to worry about Debian screwing with something Ubuntu is trying to do.
Which, is all to say that there is no other distribution you can officially equate to RHEL like you can with Debian & Ubuntu.
It’s always entertaining for me. I think that speaks more to the performances of Ryan Gosling, Steve Carrell, and Brad Pitt more than the movie itself. But, the way it presents the facts of the collapse is also a little unique and fun.
With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.
IMO, this is a discussion that should be taking place on the project’s GitHub. I’m going to lock the comments so I don’t get any more reports about commenters’ behavior.