| 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
| ||
|
Message-ID: <48C8D707.6090801@debian.org> Date: Thu, 11 Sep 2008 11:29:59 +0300 From: Faidon Liambotis <paravoid@...ian.org> To: Marcel Holtmann <holtmann@...ux.intel.com> CC: David Miller <davem@...emloft.net>, dwmw2@...radead.org, 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 Marcel Holtmann wrote: > it is that the Debian maintainer screwed this up. Upstream never > promoted kernel versioned directories for the firmware. I had a long > discussion with Dave about it at OLS and using the kernel version is > just plain wrong. The driver maintainers should version the firmware if > they break it in an API incompatible way. > > To shed some light into the problem with Debian/Ubuntu. They install the > firmware in /lib/firmware/`uname -r`/ and everytime they bump their ABI > number, they have to install all the firmware again. This is just > braindead. Their udev script actually checks /lib/firmware first and > then the kernel versioned directory. So that is just fine. I could not find any packages in Debian that contain a /lib/firmware/$(KERNELRELEASE) directory. Perhaps this is just an Ubuntu issue? Regards, Faidon -- 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