ElectricRider wrote:should this work with all distros even those that don't already use the shim or any otherwise UEFI compatibility? Or perhaps an older version of Mint even not based on Ubuntu 2.10?
Yes, with the caveat that the user must either modify the installer manually or install with Secure Boot disabled and then re-enable Secure Boot after setting everything up. This is no different than using shim, at least in principle. The difference is that PreBootloader is easier to get started with, since it doesn't require signing binaries; but PreBootloader requires more maintenance in the long term, since it requires registering each new binary (boot loader and perhaps kernel) whenever it's upgraded.
The problem with all distros using the shim approach is not all of them are going to want to do that - or not work on it in a timely manner. I've had some tell me they wont worry about UEFI (let alone Secure Boot) till the next version of the OS, which may come in over a year.
As I say, an end user can set up either tool. I describe the process for shim here.
I've got an update with more details about PreBootloader close to ready.
Seems to me all boot managers and apps that run at boot time like a partition managers or Windows apps like Comodo Time Machine or Rollback RX are going to have to deal with MS holding out their hands for payment. I understand this payment doesn't go to Microsoft but to the company that runs the software to purchase the keys.. I think it's Verisign.
A one-time payment will do it; or they can use shim or PreBootloader without paying, but imposing a bit of an extra burden on users to select a file in a file manager before proceeding.