I hope NVK can one time surpass the current nvidia driver, at least for the needs of a basic (possibly gaming oriented) linux user.
Nvidia simply does not care about that and it doesn't seem like it will change anytime soon.
I am pretty sure, you can as easily have encryption only on a single logical partition of that disk, considering you first create a luks partition, unlock it and then format the mapped device with the target filesystem (and install the OS on there).
Pardon my ignorance here, but I don't get it how is the whole thing still safe with unlocking from TPM instead of me providing the password at boot time?
Considering now anyone can just boot the machine into the installed system then bruteforce/exploit something to get login/get read permissions and make a plain copy of the data?
Where, without tpm, as long as I do not type in the encryption password myself I have a pretty high guarantee that the data is safe, especially when I am not at the (powered down) computer.
I don't know about you, but while I think its an amazing game (art, idea), the current state is not. It just feels like crytek is milking it and some big upgrade to the engine is long overdue.
So, I don't really have to switch too often, only if we get full lobby with friends.
I feel this, especially the GUI/Desktop essential stuff, and I have been daily driving Linux on desktop for about 8 years now.
Going from Debian with Mate to Arch with AwesomeWM (minimal tiled window manager), there is a lot you actually need to know and it's convoluted how it interacts with each other, a lot of it is thru dbus but some things go thru env variables - .xprofile, .profile, bashrc/zshrc, pam_env.
Yesterday I found out I am actually not running any gui polkit agents - I had it installed (possibly for years) but the .deskop file had OnlyShowIn=Xfce so Dex didn't autostart it.
Sometimes I do feel like I am just making my life harder for no reason but I love the minimal UI and kb navigation.
It sounds like your main problem is that distrobox somehow eats up the output of the commands run in it? Maybe you are missing some other switch then.
I am assuming the --commands switch does actually run the commands, but does not show the outputs.
Usually when distrobox takes over the terminal as you describe it, it could be boiled down to "taking over" the terminal's stdin, stdout and stderr which your GUI terminal app/emulator thenr renders out. (What actually probably happens is that distrobox calls docker run with -it switches which allocate a pseudo-TTY, basically another terminal - keep in mind these terminals or ttys in other words, are not the same as [usually] graphical terminal emulators).
Producing the "epic drops" steadily will require having separate factories for it.
To me that sounds like you are going to hit the UPS drop sooner then (?)
Ooh, opt-in makes a lot of sense with this, with that it can be considered as a kind of "increased difficulty" setting for seasoned, veteran players who want just something more to work on optimizing.