| |||||||||||||
Preparing the kernel for UEFI secure bootPreparing the kernel for UEFI secure bootPosted Sep 7, 2012 13:26 UTC (Fri) by wookey (subscriber, #5501)In reply to: Preparing the kernel for UEFI secure boot by mjg59 Parent article: Preparing the kernel for UEFI secure boot
Sorry. I don't really understand that. A computer can be both client and server depending what software I run on it. Do you mean there are different versions of Windows called 'client' and 'server' and the certification requirement of 'cannot switch off restricted boot' only applies to the 'client' version?
Can't you run server software on 'Windows client'? How do they stop that happening? (can you tell I've not taken much notice of Windows for a really long time now)
Presumably they will want Windows to run on ARM server kit so there will be a version of 'Windows server' for ARM soon enough. If that won't have the 'you can't turn off resitricted boot' antifeature certification requirement then thats good.
(Log in to post comments)
Preparing the kernel for UEFI secure boot Posted Sep 7, 2012 13:35 UTC (Fri) by mjg59 (subscriber, #23239) [Link]
The certification requirements that must be met depend on whether a hardware vendor deems their platform to be client or server, and there's a corresponding set of limitations on the supported versions of Windows. You could run a server on client editions of Windows, but you'd be missing any of the management tools that would make it a reasonable or pleasurable experience.
Preparing the kernel for UEFI secure boot Posted Sep 7, 2012 18:24 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
If hardware vendors could designate their hardware as 'server' or 'client' and have this enforced, Linux would never have gotten started.
*nix manufacturers would have loved to be able to protect their expensive systems by preventing the cheap systems from running "server" OS versions
Microsoft also would have loved to be able to lock in the 'server' vs 'client' status of hardware
the losers of this are the users and owners of the systems
|
|||||||||||||