You’re losing me. I’d be happy if there was nothing but a tab that read “MENU!” and a bunch of options like “Twiddle/Twaddle”, “Fiddle/Faddle” Samoflange: [Enable], etc. Don’t scare away the market of people who need a menu with esoteric options. It’s literally a value-add option for me.
@Green @frameworkcomputer the question if it's locked or not?
"We’ve handed three systems that can boot unsigned bootloaders to folks in the coreboot community"
This sounds really serious odd. It would mean they lock down the BIOS and it is *not* replaceable.
Meaning it's just a closed system like a game console or a phone.
You won't modify coreboot and replace your own BIOS with it.
Why should a community do the port of the framework if nobody else can't install and use it?
@Green @frameworkcomputer But this is so wrong on multiple layers.
I wouldn't expect anything from the 3 gifted and at least one of them stopped.
There is no sense and motivation in doing a #coreboot port in your free time if nobody can use it except if the vendor might be so kind to sign it.
Free software is also about modification. You can't even test a simple modification to fix a bug because it wont boot!
So who owns the #framework you bought? Why don't you decide which software runs on it?
@Green @frameworkcomputer I also don't get why they choose this way.
Why are the frameworks fused and signed by using #bootguard?
They could just follow the good known and working example of the chromebooks without bootguard. Simple, secure, easy to understand, open, repairable, hackable. Aren't those attributes they like to use with #frameworks?
lynxis
Grünspatz