Sky-Knight
Well-Known Member
- Reaction score
- 5,417
- Location
- Arizona
I'm sorry, but that's not true. Because there was no previous kernel to boot. And if there was, it also loaded the appropriate software that triggered the bug, because it had a previous version of the same software loading the same busted definition files!I’m aware of that. You missed my point. To get those systems booted all they had to do was load the previous kernel. (This as assuming that you retain copies of your previous kernel when you patch it. Not everyone does). It’s an easier fix than booting into safe mode than Windows.
Fixing the Red Hat systems involved booting into single user mode, and removing the impacted file. Which is the EXACT SAME PROCESS we're seeing on the Windows side of the fence.
It doesn't matter what your kernel is, they fail the same way. This specific failure mode is always present, and it ALWAYS SUCKS when it's triggered.
Last edited: