SteveTech

Before other people start commenting 'yeah obviously', it's their April Fools video, it's pretty funny.

What motherboard do you have?

If it's related to memory context restore, I also had to toggle 'power down enable' on my setup.

I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn't really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).

Also I'm not sure, but I don't think Windows handles RDP on the kernel level, it's just nicely tied in with DWM and doesn't have to deal with the multitude of window managers on Linux.

Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.

Windows Server Core still has a window manager, just all it does show a command prompt very similar to the one in the usual Windows recovery environment.

I wonder if this made it into the android kernel: https://www.androidpolice.com/pixel-stutter-bug-addressed-by-third-party-dev/

Or if it is just general updates.

I thought Discord gave you the option to send a message as a file now, or maybe that was desktop.

You have to be on the March update, then go to Developer options -> Linux environment, and enable it. Then 'Terminal' will appear in your apps drawer.

I hadn't restarted my serial logger after I rebooted my laptop, leaving me with no clue about what caused the crash.

Probably way too late now, but if it was a proper kernel panic, it should've saved the dmesg in the kernel's pstore which saves to either ACPI or EFI storage (depending on BIOS or UEFI), which systemd then extracts to /var/lib/systemd/pstore/ on next reboot.

Oh damn, phoronix comments are usually bad, but they really got off the rails this time!

I noticed it the other day too. The flatpak version let me add one SSH key, but another with password protection would only error.

I've never tried it, but there's Waypipe.

Unless you are moving gigabits of data, you won't notice the difference the smaller header payload of ipv6 offers.

IPv6 headers are usually bigger anyway^1^, so the only advantage is more efficient routing (so infinitesimally better latency), but in my experience most routers only support IPv4 hw offload and not IPv6, so it's only more efficient in theory.

I just like IPv6 because I get a whole /56 prefix to play with, and devices often randomise their host portion through the privacy extensions, meaning they use a new address each day or so.

^1^ IPv4 is usually ~20 bytes, but it can be up to 60 bytes if you stack a lot of options, IPv6 is only 40 bytes AFAIK.