So boycott UEFI
Summary: The latest experiences with UEFI (reported by one who is experienced with UEFI) suggest that a boycott of UEFI is still justified
AS we pointed out before, UEFI ‘secure’ boot is actually a mechanism for reducing security, enabling remote entities to take control of one’s hardware or destroy it ‘IBM style’ (IBM works with the NSA on self-destroying hardware). Even the NSA recognises this ability. In addition, UEFI makes it harder for people to explore operating systems other than those which have NSA back doors.
Several days ago Jamie Watson reported  that he had purchased a computer saddled with the notoriously unwanted Vista 8. He said he was getting it “ready for Linux” and days later he reported on his findings, having had many issues with UEFI before (the UEFI Forum contacted him as part of well-coordinated attempts to change perceptions). His opinion on UEFI is hardly changed. He calls UEFI “a royal pain” after trying almost a dozen distributions with it (over the course of nearly 2 years). He said: “For those who might not be personally familiar with UEFI boot yet, and especially for those who might be familiar with only one UEFI boot implementation, I’m going to include some more details here to explain and illustrate why it is, for me, such a pain.”
Intel and Microsoft are making it very hard to dodge back doors, surveillance, etc. in pursuit and in favour of freedom. It’s time to dodge Microsoft and Intel and it’s time to seriously just boycott any hardware that comes with UEFI. █
Related/contextual items from the news:
One of the large retail chains here in Switzerland has a low-priced product range that it calls “M-Budget”, which includes everything from groceries to housewares to computers, and pretty much anything else you can think of.
As I was walking past one of its shops on Saturday, I saw that it was offering an HP Compaq laptop for 333 Swiss Francs (about £225/€272/$370), and that is so low for the Swiss market that I couldn’t resist.
But as for UEFI: what a royal pain. For those who might not be personally familiar with UEFI boot yet, and especially for those who might be familiar with only one UEFI boot implementation, I’m going to include some more details here to explain and illustrate why it is, for me, such a pain.
The UEFI BIOS boot configuration is made up of two basic parts — a list of boot objects, and a sequence in which they should be attempted. When you get a new Windows 8 system, there is usually only one “real” item in the list, that being the Windows 8 Bootloader.
There will probably also be some other “pseudo” items or “generic” items in the list which allow for CD/DVD and USB boot, for example. The boot sequence on the a new Windows 8 system will contain the Windows Boot item first, and then perhaps some or all of the pseudo/generic boot items.
This is the first place I saw something unexpected in this UEFI BIOS, because there were items included in the default sequence which don’t even exist in the list of boot objects. Weird.
When you install another bootable operating system, such as Linux, it will add an item to the boot object list for itself, and that item will be placed at the front of the boot sequence list.