linux-kernel - Re: RFC: install firmware in a kernel-dependent directory

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]

Date:	Sat, 14 Feb 2009 13:02:00 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Michael Riepe <michael.riepe@...glemail.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: RFC: install firmware in a kernel-dependent directory

Michael Riepe wrote:
> Currently, make firmware_install puts all firmware blobs in
> /lib/firmware. If you have several kernel versions installed, they will
> overwrite each other's files, which may lead to problems if the blobs
> eventually change. I think it would be better to use a separate
> directory for every kernel version, like /lib/firmware/$(uname -r) or
> /lib/modules/$(uname -r)/firmware (the latter is my favorite).
> 
> In either case, only a minimal modification in /lib/udev/firmware.sh is
> required to make it look in the new directory first.
> 
> Comments?

Seems reasonable to me, it seemed rather bizarre to me that this wasn't 
done in the first place..
--
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/