|
|
|
|
|
|
by Dylan16807
696 days ago
|
|
|
That doesn't make any sense. The OS loads file A into the kernel. It crashes. It reboots. It decides not to load file A this time. Wow, it's a rollback of kernel-space code. Unless your argument is that you can't guarantee a rollback of every possible kernel driver, because it might have installed a rootkit while it had full control? Okay, cool, but this isn't a malware removal idea. It's an idea for normal drivers. |
|
|