On Fri, Jun 28, 2024, 18:28 Vitaliy Perekhovy <feri...@gmail.com> wrote:
> On Fri, Jun 28, 2024 at 04:17:23PM -0000, Grant Edwards wrote: > > Is there any graceful way to handle the elimination of unwanted > > linux-firmware blobs when doing an update? > > > > I believe I understand the process as outlined at > > https://wiki.gentoo.org/wiki/Linux_firmware: > > > > 1. install/upgrade sys-kernel/linux-firmware > > 2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmmyyyy > > 3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag > > > > I've tried that a few times, but it's rather annoying to have to do > > that every time linux-firmware gets updated. > > > > AFAICT, the list of three or four blobs that I actually need on a > > specific machine never changes. > > > > It seems like there ought to be a way to configure that required > > firmware list and have the emerge -u "just work", but I can't find > > it. Have I missed something? > > > > Yes, I know... > > Disk space is cheap. > > Premature optimization ... > > etc. > > > > It still annoys me. > > > > -- > > Grant > > Save your firmware list in > /etc/portage/savedconfig/sys-kernel/linux-firmware > That's it. > > -- > Best regards, > Vitaliy Perekhovy > After every update to sys-kernel/linux-firmware, you may get the following output: * IMPORTANT: config file '/etc/portage/savedconfig/sys-kernel/linux-firmware-20240610' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. It's a good idea to compare this file to your current file to see if any firmware blobs have gotten updates. However, it's important to then discard this file by choosing `z` in dispatch-conf. Regards, Waldo >
