| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 10 Sep 2008 16:15:11 -0700 From: David Woodhouse <dwmw2@...radead.org> To: David Miller <davem@...emloft.net> Cc: jeffm@...e.com, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, torvalds@...ux-foundation.org Subject: Re: [PATCH] firmware: Allow release-specific firmware dir On Wed, 2008-09-10 at 16:05 -0700, David Miller wrote: > > Tell that to every Debian and Debian derived system on the planet. > > To my knowledge, it is only fedora and possibly one or two other dists > that put the firmware files in a unary /lib/firmware location, rather > than a versioned /lib/firmware/$KERNELRELASE one. So every time they upgrade from one kernel to the next, do they automatically run b43-fwcutter again to make a new copy of the firmware, for the new kernel? Or if they use QLogic SCSI cards, do they download a new (but identical) version of the firmware each time they upgrade their kernel? It sounds like a daft arrangement to me -- although of course it's possible for the packager to do whatever they like, by overriding $(INSTALL_FW_PATH) in their package build. It's definitely not something we should be doing upstream though. -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists