> A subsequent reboot will fail to relink because the SHA256 file has not
> been updated, also rewriting the kernel at this point nullifies the sync
> that was recently added for a reason.
> 
> (Also as you'd probably expect, a similar suggestion has been made
> before and already rejected.)

Out of curiosity, what was the reason this idea was rejected? I'd be
interested in writing a patch that addressed them if possible.

Reply via email to