Bug#684569: microcode module loaded on Celeron CPU
Andi Kleen wrote: On Mon, Aug 13, 2012 at 09:44:48AM +0200, Paul Menzel wrote: Looking into this some more, this seems unlikely in Debian because the microcode packages are in non-free [1] and therefore not available for Debian users not having enabled non-free repositories Because of that the microcode packages are also non-essential, that means not installed by default even when non-free packages are allowed. And normal users will never install them by themselves. Sounds like a problem. They actually fix bugs so it's recommended. BIOSes are not normally updated regularly, so the microcode update gives you a faster path to that. You can see why an OS distributor would be stuck in this situation, though. If the microcode updates are installed by default, Debian is taking responsibility for their effect (in the sense of receiving bug reports and providing updates when appropriate to address them). And that is very hard to do without the corresponding source code. At least when updates come through the BIOS the OS distributor does not have to be involved. The non-free packages also allow users to use the updates from Intel without too much fuss when they want them. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813170436.GA5995@mannheim-rule.local
Bug#684569: microcode module loaded on Celeron CPU
At least when updates come through the BIOS the OS distributor does not have to be involved. The non-free packages also allow users to use the updates from Intel without too much fuss when they want them. One alternative would be to offer a downloader. Just hiding them from the user is not a good policy. Microcode updates can contain security updates (among other fixes), so you should have some mechanism to distribute them to your users. If you don't want to offer these updates you should at least clearly explain those tradeoffs to your users. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813173246.gp2...@tassilo.jf.intel.com
Bug#684569: microcode module loaded on Celeron CPU
On Mon, 13 Aug 2012, Jonathan Nieder wrote: You can see why an OS distributor would be stuck in this situation, though. If the microcode updates are installed by default, Debian is taking responsibility for their effect (in the sense of receiving bug reports and providing updates when appropriate to address them). And that is very hard to do without the corresponding source code. It is not the lack of source code[1] that is the problem. It is the absolute lack of any sort of release guidance whatsoever from Intel when a new microcode update is made available. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813183119.gc3...@khazad-dum.debian.net
