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.

Never go to a second location, let a third.

You in trouble.

It will TECHNICALLY still work at whatever version Nvidia cuts off support at, which is pretty soon for GTX cards (they’ve already cut off the mobile counterparts). So you’ll stop getting updates, but it should still work as long as that driver is made available still in some form that whatever distro you are using can install it, or you compile it from scratch. I would not trust Nvidia’s installer to still be working by then in it’s current form because it’s a MESS.

Seamless. Until you find something that isn’t. Report it if so.

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.

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.

Yeah, but it’s almost pointless to give an “if, then, elsif, elsif” scenario if just removing the battery does the same thing, and all motherboards have a battery for the CMOS.

Did you read that I was saying containers are bad somewhere? You have misread.

Flatpak for one: https://github.com/flathub/com.google.AndroidStudio

Android Studio isn’t just a simple app, nor a single executable, AND it maps out to a bunch of local sockets to your already running host to provide various services. Certainly not going to be easy or stable in a container, especially since they are asking about emulation as well.

I’m confused by your question. Why would you need a container for this? There are other packages downloads for Android Studio. Container would be the most convoluted way of running it.

This sounds like you have beef with the developer.

What’s this post about?

If you don’t have an onboard display to plug into, open your PC, pull the CMOS battery for 30s, and plug it back in. This will reset all your settings to factory defaults.

Guess it depends on the theme. MacOS had it since OSX. FVWM back in the day. Just changes from time to time. If I’m in a bright ass room, sometimes it can be more comfortable.

I’m pretty sure you just have an old and degraded disc.

Not sure what the actual question is here, but if the files are there, the filesystem is mounted properly using hfsplus, and you can read the files, then any incompatible characters will be properly substituted, and the files can be copied.

Your friend will just have to put some work into properly renaming then afterward.

That’s not an actual OS. It’s an app-backed secure storage device more than anything. The app you launch on your devices accesses whatever you have on the thumb device and runs it on your phone. Mostly just marketing, but certainly not an actual self-contained OS.

Literally doesn’t matter

Sorry to say, but no, it’s the most problem solution.

I won’t even get into the details, but it’s like a heart replacement, and there are many issues by simple swapping packages from the default in this sense. Everything is shipped expecting whatever distro defaults, and just swapping things out doesn’t work that easily.

It sounds like you probably had issues with specific apps that didn’t properly support Wayland, and you couldn’t tell the difference between the entire composition environment, and a single app having issues because it only support X11.