As such, the workaround in this release may break with a future Shim. I consider this a "band-aid" patch, though, because it relies on a quirk of Shim's logic to bypass its de-registration. I quickly discovered a workaround, which I've implemented in this release. Since rEFInd's drivers are binaries, if you use a single driver, that means that you won't be able to launch anything that requires validation via Shim. This creates a new problem, though: rEFInd can validate just one binary before it's "cut off" from Shim.
This is done to avoid problems in a boot path in which Shim launches fallback.efi, which in turn launches another Shim.
Specifically, Shim 0.8 now de-registers itself from the EFI after a follow-on program launches another one. (See this thread for one such report.) It turns out that the problem was not a new bug in rEFInd, but rather a change from Shim 0.7 to Shim 0.8 that made it next to useless with rEFInd. Soon after releasing 0.9.1, I started receiving bug reports about problems with it and Shim 0.8.
0 kommentar(er)
