On 15/06/12 14:29, Jim Henderson wrote:
On Thu, 14 Jun 2012 17:10:55 +0000, Jim Henderson wrote:
So the scenarios are:
1. New system with no OS on it - secure boot is probably disabled and not a concern.
2. New system with Win8 on it - Secure boot is enabled and has to be disabled in order to install openSUSE, regardless of whether it's a replacement of Win8 or a dual-boot configuration I wonder what the risk is of a signed component going wrong/not validating - what would the recovery would be for such a scenario?
What I remember from reading the specs over, it seems that preserving a previous set of signed components (whatever there is that's needed) would be a good idea.
Jim
If you have to do an addendum to what you wrote only a few minutes ago then can you understand my confusion - and I cannot be alone on this - about this whole matter? :-) What I really cannot understand is that this appears to be a major problem with respect to using openSUSE and yet this whole question has been pushed onto "the community" to try and resolve! Where is "the Board"? Where is "the Foundation"? Where is anyone who actually knows what is going on and what has to done about this situation? Oh, right...one must not ask questions like this... not the sort of questions one asks in polite company..... Asking questions like this only gets you the title of "troll"...... BC -- Using openSUSE 12.1 x86_64 KDE 4.8.4 and kernel 3.4.4 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org