this post was submitted on 19 Jul 2024
632 points (98.5% liked)
Technology
59211 readers
2517 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I love the Linux bros coming out of the woodwork on this one when this could have very well have been Linux on the receiving end of this shit show. Given that it's a kernal level software issue, and not necessarily an OS one.
It's largely infeasible to use Linux for many, most, of these endpoints. But facts are hard.
Hey man, let us have this one. Any immutable/atomic distribution could have either prevented this or easily rolled back the update. Not to mention a Linux offering by something like Red Hat, for example, wouldnt recommend installing closed source third party kernel modules for exactly this reason. Not sure about the feasibility of these endpoints, but the way things are generally done on, and the philosophy of, Linux could very well have avoided this catastrophe.
Can you explain what is immutable/atomic distribution and how it can prevent this?
My thought was mostly that this kind of invasive third party and closed source kernel module security wouldn't have been necessary. But I'm pretty sure rollbacks can include kernel changes in a previous image.