https://youtu.be/4yDm6xNeYas?si=0VzBxIuPEHC4SMaa
This fireship video is a good, short explanation.
this post was submitted on 20 Jul 2024
160 points (98.8% liked)
Asklemmy
43790 readers
875 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
Itβs not so much that itβs ubiquitous so much as the customers that DID use it were very large and their going down was very noticeable.
When an operating system allows a single misbehaving program to take down the whole computer and leave it unbootable. I thought we left that behind with Windows 95.
Drivers usually run in kernel space, where a crash can bring the whole system down. This is not exclusive to Windows
This isn't a driver. It's anti-malware. Nobody on Linux puts such software in kernel space (as far as I'm aware). Root service? maybe, but that's still a user-space process.
Nobody on Linux puts such software in kernel space
Falcon Sensor is also being distributed for RHEL and Debian, and it caused issues there too.
https://www.neowin.net/news/crowdstrike-broke-debian-and-rocky-linux-months-ago-but-no-one-noticed/
It is a driver though, it runs at kernel level and intercepts system calls for logging, analysis, and potential blocking if malware type patterns are detected in the system calls.
Yes but only in Windows land do you see jillions of (proprietary) drivers made by 3rd parties. Many of which self-update.
That has been a thing forever. I doubt it will ever go away.
A lot of companies install it for compliance checkboxing.
Apart from fjordbasa's caveat RE "ubiquity" above, this is probably the most succinct answer π
BTW, if Windows had been an immutable OS the case would not have been so dire.
If my grandmother had wheels, she would have been a bike.
It's a different recipe!