Unfortunately it forced all existing users to submit as well, but we already gave it a bunch of photos of ourselves before the beast had revealed itself
I think xvnc does this with vnc. If using gnome start gnome-remote-desktop with systemctl --user start gnome-remote-desktop then use grdctl to set it up (or the settings gui). I've had luck with rdp on a Wayland session this way.
I get paid by the hour! 😅 But for real though it's a struggle. Mostly I try to use msys2 for everything but. I still have native git. There are some long standing bugs that make the vim excruciatingly slow to open or close, really I should go try to fix it but it doesn't feel like a fun problem.
For AC power, capacitors don't effectively store energy for later, and would change the power factor to make the resistive load reactive which can bring down the efficiency of the power transfer. For AC power a big ol resistive heater is probably as efficient as you can get, which is part of why those kettles are so simple and boil water so fast.
A kettle that stores energy would need to use DC power, converting it from AC and probably have a very large capacitor, more likely a battery.
Don't be afraid of the command line, breaking Linux is how you end up learning how to use it!
I haven't done this tutorial but if that kind of thing helps you this one looks pretty good.
My best guess is you need to do something like:
(In the shell, one line at a time, enter runs the command)
mkdir /mnt/tmp
mount /dev/sda2 /mnt/tmp
nano /mnt/tmp/etc/fstab
Nano is a text editor that uses your whole terminal, so you will see the contents of /mnt/tmp/etc/fstab (the file that controls where disks are mounted) and replace 'sdb' with 'sda' on the line starting with /dev/sdb2. The bottom of nano's screen shows you the keyboard shortcuts, I think Ctrl W will make it write the file, asking for confirmation of the filename, which should stay the same. Exit nano (Ctrl+x maybe?) then reboot with the command 'reboot'
If you get any errors about access denied or permissions, run 'sudo bash' to get a shell with more power and try again.
Good luck!
What most likely happened is your disk order switched and, as others have mentioned, using /dev/sda1 or something similar to point to partitions is unstable and can't be trusted. Once your system is back up, look up how to specify partitions in /etc/fstab using UUID (something like /dev/disks/by-uuid/xxxx-xxxxxxxxxx-xxxx instead of /dev/sda2)
When this happens to me I mostly assume Linux shutdown automatically because of a critical over temperature event. I've seen it in the logs a few times but I don't usually check anymore.
Idk I just bought a 32GB stick of ddr4 sodimm for $60, adapters are less than $10 each so maybe not if you stay away from scalpers and don't pay attention to ram speed 😅
I was also thinking the soldered CPU motherboard with 8 cores must cost at least 200 but maybe that's a bad assumption and I didn't look it up.
Also, what do you mean by crashes? Kernel panic? Random app death because the oom killer was activated should be expected when pushing the memory limits on Linux.
Maybe.... In 2027 👀