I couldn't find a hard answer to whether this supports EPYC only, or Ryzen too; so I put together this script to read the CPUID to detect for INVLPGB support according to the AMD64 Programmer’s Manual, and my 7800X3D does not support INVLPGB.

(Let me know if I've made an error though!)

#include <stdio.h>
#include <stdint.h>

int main() {
    uint32_t eax, ebx, ecx, edx;

    eax = 0x80000008;

    __asm__ __volatile__ (
        "cpuid"
        : "=a" (eax), "=b" (ebx), "=c" (ecx), "=d" (edx)
        : "a" (eax)
    );

    printf("EBX: 0x%x\n", ebx);

    if (ebx & (1 << 3)) {
        printf("CPU supports INVLPGB\n");
    } else {
        printf("CPU does not support INVLPGB\n");
    }

    return 0;
}

TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process

They don't even need to be the same process. I'm pretty sure that's just a common practice if something needs both protocols, but there's nothing stopping you from having a web server on TCP 443 and a VPN server on UDP 443. Ports are an abstraction brought by each protocol, they aren't in anyway related.

I'm not a radio engineer, but my understanding is you're just bouncing signals off the moon itself, there isn't a device that echos the signal back or anything. There are mirrors on the moon to reflect lasers back though.

Sigh...

Wait for it to reboot 3 times and automatically enter recovery, Troubleshoot > Advanced Options > Command Prompt, del C:\Windows\System32\drivers\CrowdStrike\C-00000291*.sys

Is the fastest way to do this assuming no bitlocker. Also C: sometimes isn't mounted at C:, you might have to try all the letters between C: and X:, or just boot into safe mode.

It doesn't have a QR code in it's current state AFAIK, but I believe the guy wants to add one eventually. Here's what it might look like:

https://gitlab.com/kdj0c/panic_report/-/issues/1

Also from the commits it looks like the colours are configurable at compile time (white on black default), and that exclamation Tux is already there.

Looks like this is already a thing though with [systemd-bsod]

Nah, that only handles boot errors, not kernel panics.

I might be wrong, but I believe Debian ships without sudo, only su by default (or at least if you configure a root password in the setup).

NTFS-3G on Linux is very stable, and I'd recommend sticking to that, although I'd avoid the newer NTFS3 driver.

But if you really want to convert, and it's data that you don't mind loosing, ntfs2btrfs can convert NTFS partitions to BTRFS, and it's available in most distros' repositories.

Some discord servers can require a verified phone number, not any I know of, but it can be enabled.

Yeah, and I feel like someone's gonna slam that door one day and get egg all over their bananas.

Firstly, there actually isn't much difference between server grade and gaming motherboards, like sure one might support ECC + IPMI and the other RGB + overclocking, but as far as compute goes, they are both effective motherboards.

Secondly, I don't think OP was going for a 'server' but more of just a workstation type build, so why one or the other?

Thirdly, why does it even matter? OP should be proud of their system whether you like it or not. Even if they are using it as a server, my first server was just some reasonably priced consumer grade parts and I never had any sort of stability issues with it.

If you're using Oracle cloud (just guessing based off 1GB), they also offer free ARM VMs with 24GB of RAM, and netbird looks to support ARM.

Heavily depends on the server, a game server sure, for almost anything else you're probably doing it wrong.