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] [thread-next>] [day] [month] [year] [list]

Message-ID: <48F7AB05.50103@msgid.tls.msk.ru>
Date:	Fri, 17 Oct 2008 00:58:45 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Harald Dunkel <harald.dunkel@...nline.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.27.1: install conflict about /lib/firmware

Harald Dunkel wrote:
> Hi folks,
> 
> Seems that there is an installation conflict about
> /lib/firmware/ess/maestro3_assp_kernel.fw (and probably
> others) between 2.6.27 and 2.6.27.1. Using dpkg I get

Since 2.6.27, firmware binaries are placed into /lib/firmware
directory.  The reason is that firmware is not kernel-dependent.
Or, rather, the firmware stored here is not kernel-dependent
(when it is, it's stored in /lib/modules/$version/).

[]
> Probably other package managers get a similar problem.

A package build script should be updated to create separate
package with the firmware, and to add proper reguiriments
and/or dependencies.

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

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