linux-kernel - Re: 2.6.27.1: install conflict about /lib/firmware

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <48FF8065.9@t-online.de>
Date:	Wed, 22 Oct 2008 21:35:01 +0200
From:	Harald Dunkel <harald.dunkel@...nline.de>
To:	Michael Tokarev <mjt@....msk.ru>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.27.1: install conflict about /lib/firmware

Michael Tokarev wrote:
> 
>> Wouldn't it be more consistent to put the firmware files in a
>> kernel specific directory, e.g. in /lib/firmware/2.6.27.1 or
>> /lib/modules/2.6.27.1/firmware ?
> 
> No, because the firmware is not kernel-dependent, but device-dependent.
> It were deliberate choice.
> 

This is not about some api incompatibility, but about a packaging
conflict. Even if each firmware file is kernel-independent, the
list of files is not. If I build and install *.rpm or *.deb files
for a new kernel version (probably with a changed set of modules),
then there is a high chance that the new package for /lib/\
firmware provides a new list of files, not suitable for another
kernel.

Regards

Harri

--
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/