The story about how secure boot for Windows 8, part of UEFI, will hinder the use of non-signed binaries and operating systems, like Linux, has registered at Redmond as well. The company posted about it on the Building Windows 8 blog - but didn't take any of the worries away. In fact, Red Hat's Matthew Garrett, who originally broke this story, has some more information - worst of which is that Red Hat has received confirmation from hardware vendors that some of them will not allow you to disable secure boot.
To read all comments associated with this story, please click here.
Member since:2005-06-29
Member since:2009-08-18
I read the blog post and you article which rallies the Linux crowd.
May I remind you I actually use OpenBSD ... and I buy my OpenBSD CDs.
As another has already said on this forum ... Motherboard manufacturers for OEM systems won't be as foolish as to do this.
I don't rally to Microsoft's defence ...
I was a Linux System Admin for 2 years.
I buy OpenBSD CDs to donate to the project.
I use an Android Phone.
I use Fedora 15 for my media box.
I use Windows 7 on My girlfriends laptop and my own desktop.
What I am fed up with ... is the constant Microsoft Bashing which is like the Zerg rush on every Website that is tech orientated.
I am a pragmatist and I use whatever works. Though I was initially worried about the announcement I waited patiently to actually know WTF was going on before getting upset.
If Microsoft do indeed threaten OEMs to remove the "disable Secure boot" option ... there will be in another anti trust case.
If OEMs stop you from disabling it ... then don't buy that hardware.
At the end of the day we are a fringe case and we are far more tech savvy than most ... I always check my OS compatibility when shopping for hardware ... and I use an OS that is far less popular than Linux (OpenBSD)
Edited 2011-09-24 21:00 UTC
Member since:2005-07-06
Interesting how you didn't quote the Microsoft blog's statement:
"OEMs are free to choose how to enable this [Secure Boot] support..."
In other words, Microsoft are letting the OEMs decide whether to include a "disable secure boot" in the UEFI BIOS. It's a bit surprising that the UEFI standard didn't actually insist that the user should always be able to disable secure boot (I don't care if it's enabled by default, but I do care if it can't be disabled).
If Microsoft will indeed insist that the secure boot can't be disabled for OEMs to qualify for the Windows 8 certification logo, then *all* OEMs will do so and those machines won't be able use any other OS than Windows 8 or later. You can be guaranteed that OEMs won't advertise the fact that you can only run Windows 8 or later on their latest kit either, since that's surely a negative selling point?
As people have said, this will potentially impact Windows users too - no XP, Vista or Windows 7 on those new machines and bang goes third-party rescue CDs (you'll be forced to use MS'es signed rescue disks and no others).
There are surely anti-trust issues if Microsoft effectively force OEMs to only allow Windows to be installed on machines, even after the end-user has bought the machine and taken it home? It's a clear monopoly abuse because although MS might claim OEMs had a clear choice, the logo certification program insisting on secure boot not being able to be disabled is a major influence in the OEMs decision.
Member since:2009-08-18
So don't buy from those OEM that do. Simple.
Which is why they will leave in the option
Member since:2006-01-14
And some manufacturers have already stated that the option to disable will not be present. Many OEM's even now with just a regular BIOS do not allow users to change all the features that are present. Dell is pretty good, but that doesn't mean the option will always be there. Also, if Microsoft can mandate that OEMs include this functionality, what is to stop Microsoft from later mandating that the disable option be removed?
Case in point, I have a 1U server that has procs that include VT-x. The motherboard has a chipset that supports VT-x. The OEM set the BIOS to permanently disable hardware virtualization. Why? Because they could I guess? Because it was sold at a price point that they didn't want hurting sales of more robust expensive servers?
Member since:2009-08-18
Member since:2005-07-22
Member since:2009-08-18
The new WebKit Opera for Android has been released. "Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!"The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Member since:
2009-08-18
http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-com...
There is the damn option to disable it.
I dunno how much more black and white you guys need it.
If a manufacturer locks this down ... just don't buy from them.
BTW I have owned Laptops and Computers from Dell, HP, Acer, Asus, Apple and none of these have ever locked down the BIOS down.
Edited 2011-09-24 19:19 UTC