Any module/directory that was at one time included in linbofs by listing it in /etc/linuxmuster/linbo/firmware and running update-linbofs will forever stay in linbofs even if it is removed from /etc/linuxmuster/linbo/firmware and update-linbofs is run again.
It seems that update-linbofs does not clean out /var/cache/linuxmuster/linbo/firmware/ before filling it according to the entries in /etc/linuxmuster/linbo/firmware, so the configuration file works additive instead of reflecting the actual state of linbofs' /lib directory.
If that was intended behaviour this is of course no bug, but it does seem unintuitive.
Any module/directory that was at one time included in linbofs by listing it in /etc/linuxmuster/linbo/firmware and running update-linbofs will forever stay in linbofs even if it is removed from /etc/linuxmuster/linbo/firmware and update-linbofs is run again.
It seems that update-linbofs does not clean out /var/cache/linuxmuster/linbo/firmware/ before filling it according to the entries in /etc/linuxmuster/linbo/firmware, so the configuration file works additive instead of reflecting the actual state of linbofs' /lib directory.
If that was intended behaviour this is of course no bug, but it does seem unintuitive.