Comment Re:rrriiiight... (Score 1) 64
Huh? It's an unsecure and unmaintained open-source driver that's causing the issue. The OS is running perfectly fine.
Perfect illustration of the thinking problem here. You don't even get WHAT the problem is.
Why is a driver able to fuck up a system? The OS should be the watchdog that says "WTF are you doing there?", not the obedient slave executing whatever.
A great illustration is W^X - first found not in Windows, but in OpenBSD. Because Windows happily goes "whatever you say, master", while the guys at OpenBSD said "no actual use case of non-broken, non-malicious software should ever behave like that, so we'll block it".
since a non-MS open-source driver is actually the problem here.
If you are responsible for a sensitive location, and a five-year old kid from the neighbourhood one day just wanders in and take a look around out of curiosity, pressing a few buttons to see what happens - you would definitely not keep your job by claiming that the little kid is actually the problem here.