UEFI Formed to Replace BIOS
anonymous cow-herd writes "Businesswire reports that several leading technology companies including Intel, AMD, Microsoft, IBM, Dell and HP and others have formed the Unified EFI Forum. The non-profit corporation will assume responsibility for the development and promotion of the EFI specification, a pre-boot interface originally developed by Intel that is intended to replace the aging PC BIOS."
I've said before, and I'll say it again: Why not OpenFirmware/OpenBoot?
Let's go through the list and see what EFI has compared to OpenFirmware, shall we?
1. EFI has a built-in bootloader. (Check)
2. EFI has built-in device drivers. (Check)
3. EFI has a shell environment. (Check, except that OpenFirmware isn't so laughable.)
4. EFI is cross platform. (Check)
5. EFI maintain *some* of the old PC BIOS calls. (No Support in OpenFirmware. Boo hoo.)
6. EFI adds trusted computing. (No Support in OpenFirmware. OF believes in computers being controlled by their owners.)
So why EFI and not OpenFirmware? Could it be a Not Invented Here Syndrome, or something more sinister? Is this the beginning of Trusted Computing for all? How do they expect to get customers to purchase an EFI system when a PC BIOS one is still well supported? Will they try to make an exclusive contract with Dell and invite the wrath of the justice department?
Only time will tell.
Javascript + Nintendo DSi = DSiCade
So.. Is there really any doubt whether Apple will use EFI in their machines? Seriously.. they can't use BIOS now!
- Henrik
- when the Shadows descend -
I'm sorry but do you people take the time to read up before you complain? This is a wonderful opportunity for the open source movement. EFI makes booting multiple operating systems like a thousand times easier. Instead of having a single boot record on the hard disk boot information is stored in a data table and given as an option to the user who selections the OS they want.
This means that Linux can be installed without breaking the existing installations or screwing with the boot loader at all. The DRM is a problem but there is not too much information about if there is going to be a lot of DRM in this new bios replacement.
Please correct me if I'm wrong but isn't the BIOS of today backwards compatible with a lot of obsolete hardware that require the BIOS to still behave in a certain way? I belive there were hardware components that for example required that BIOS waited for a certain amount of time before processing some commands due to their startup time. And as years has passed by new features have been added while the old ones are kept and at some point it's a unnecesarily messy code.
Zere vere zwei peanuts valking down der Straße, and von vas assaulted...peanut
As with everytime I post a comment about DRM, someone has to come along and say, "but see, there's a way around it!" Wrong.
DRM'd OSs will not work if the hardware they run on isn't DRM'd as well. This initiative (along with others that may flurish if this doesn't work -- i.e. Phoenix BIOS) is to make certain that the hardware is protected as well so that people won't be able to easily circumvent the restrictions.
Why would they bother to go through all of this if it didn't matter?
I'm going fully Mac when the x86 powermacs come out anyway so Windows is just going to be something I use for emulation purposes.
An obvious troll but I'll respond anyway: Windows will not run in emulation because of DRM. Sure, they might get an emulation layer up and running but it certainly won't be able to do anything that you would be able to do w/the "appropriate" hardware/software... Software will be trusted. Trusted software will not run on emulation layers.
Sorry, welcome to the future.
All five would be more than happy to have "Linux" be redefined as a cryptographically-signed binary supported by a "responsible" company such as Novell or Red Hat.
The first four, because it suits their corporate customers. Debian, Gentoo, etc. just divert efforts away from supporting the two major distributions that Really Matter.
Microsoft, of course, because they know how to "deal with" corporate entities.
From Microsoft's point of view, F/OSS really is like terrorism. Honest. Like national armies, they know how to wage war against similar entites with known addresses, but have a hard time getting traction against amorphous movements which won't stay put for the ICBM treatment.
Lacking <sarcasm> tags,