If anything happen to Linux today, like what happened to Windows, most of the internet would be dead.

And keep in mind, the falcon sensor exists for Linux. All those big companies largely use it.

Essentially we just got lucky that their buggy patch only affected the windows version of the sensor in a showstopping way. Could have been all major OS.

This mastodon user claims otherwise:
https://nondeterministic.computer/@mjg59/112816011370924959
- That's only true if you run falcon-sensor in ebpf and not kmod mode.
The issuw didn't affect Linux and macOS systems with Crowdstrike Falcon installed, though, only Windows systems.
On Windows, booting into Safe Mode and removing C:\Windows\System32\Drivers het bestand C-00000291*.sys temporarily solves the BSOD issue, as well.
- The point is that it could have. Or maybe some unknown 0-day gets used by someone out to cause chaos instead of collect random.
Yep I know

Then the internet would blame it all on Linux.

However, the recovery process would be much faster. The Linux kernel would try to load the kernel module and if it fails it would skip it.

Don't forget that ftp.cdrom.com , the biggest server on the Internet at it's peak, was running on FreeBSD.

I have no idea what the hell that is...
But Netflix runs on some BSD too
- It's where you would download your anime and Quake 2 installer twenty years ago.
There's a free blue screen of death? All of these people paying for Windows for no reason /s

Probably not. Most Linux admins know their systems and are able to navigate out of the situation with ease. But also most people don't use any corporate off-the-shelf software, because there are better options that are freely available.

Furthermore a Linux installation is dedicated and slim for one single purpose. The flexibility creates diversity.

Are you implying that Windows server admins don't know their shit?
- No. They don't. They always need Microsoft support to solve situations and upgrades. You can also ask simple questions that they cannot answer. Try Active Directory: how to run AD in a secure fashion? Or: What services do rely on DCs in our company?
- I've scene some supposedly 20 year veterans who don't know the architecture of AD
  Not to say that is all of them but I've scene some who really can't do anything outside of click some buttons.
I think the shower thought is centered around IF a ubiquitous bug that required physical access to the machine to resolve occurred simultaneously across all Linux machines.
If you couldn't remotely resolve the issues, regardless of your competence, simply the WALK to each machine and hooking up a KVM to each one would take a long time.
- There won't be such case is my argument. No one patches a system "for fun" and automatically there except they really set it up like that. It would be only one kind of a case in one company.
  Furthermore, you cannot compare Linux systems. A modem firmware with busybox is not the same as a Debian PC desktop. It works differently and has only the kernel in common. And in both cases they aren't patched at the same time. They are not even the same version, hell not even the same platform.
  E.a. nothing will ever break like this. If it does, it will be one single case of a single IT department.
This combination of arrogance and complacency sort of thinking is how it does happen on Linux one day.
Linux also isn't as popular on the desktop or end user devices

This already happens any time the domain name servers go down: https://techcrunch.com/2022/06/20/cloudflare-outage-knocks-popular-services-offline/

Doubtful. By far, most servers responsible for Internet traffic are not running crowdstrike software.

This incident was a bunch of fortune 500 companies caught with their pants down.

Who do you think runs those servers? What do you think those companies run on their Linux servers?
- Those companies aren't "the Internet." They're products connected to the Internet.
  The OP argument is like saying the Internet is dead because Netflix is down.
If all of the parts of the internet that the average person finds useful goes down, then it matters little that technically "the internet" is not down. If it can't be useful then it is as good as "down".

2038 is the next big thing to hit older *nix based OS. It will be Y2K all over again.

Maybe on my 32-bit ARM server with ancient kernel it will. Any 64-bit machine is immune.
- ...unless it's running software that uses signed 32-bit timestamps, or stores data using that format.
  The point about the "millennium bug" was that it was a category of problems that required (hundreds of) thousands of fixes. It didn't matter if your OS was immune, because the OS isn't where the value is.
It'll be 911 times 1000.
- It'll be 911,000? As long as it's stored with 32 bits that should be fine 🤷

The end is nigh, I tell you!

Y2k38