Re: I think if I'd spent
As a way to summarize what redhat wanted... Well I have the most loose of understanding when it comes to kernel code and uefi so this analogy could be entirely wrong.
Linux Kernel = manufacturer of a key component
Red Hat etc = consumer of said product.
Microsoft = competitor to both linux and red hat.
Microsoft have released a new security feature built into their hardware option, and they're enforcing this on others, there are ways around it however.
Red Hat could implement something like this themselves, but their lives would be easier if Linux kernel handled it for them, so they request "Can you implement Microsofts UEFI stuff?"
Linux turns around and say "no fuck off" why? Because not only is the idea stupid. It's not a kernel operation. The kernel has one job and one alone (well it's loads of small jobs that handle one job) UEFI is not one of those jobs. The moment they start allowing excess functionality to flood the kernel is the moment the kernel goes downhill. The fact that the kernel is (in comparison) streamlined is one of the main selling points of linux.
Okay this went from hardware to software very quickly. Fuck it carrying on.
Additional to keeping things streamlined. If they start letting excess bits go in now which aren't needed, it opens the floodgates. First UEFI, then encryption, then we'll start seeing things like GNOME built into the kernel.
If it can be done outside of the kernel, as well as it could be in the kernel, it doesn't belong in the kernel.
It's like buying a car with a GPS built in. You can either get a car for £50,000 or get it with GPS built in for £55000. OR you could buy the car for £50,000 and buy a tomtom for £100 that you just plug in. Costs less and you still have the same car.