Comment 2 for bug 1617075

https://github.com/smxi/inxi/issues

You'll want to post this exact issue report on the inxi github.

You're correct re BIOS being technically incorrect however because line space is at a premium in inxi, any term that encompasses bios and uefi type firmware has to be crystal clear and SHORT, and clear enough where all users would understand it. It might actually be possible for inxi to be smart enough to detect when it's uefi and when it's bios, not sure, depends on if that data exists in the /sys data. Might. I can check some of the user data sets.

There's two levels of partitions, P and p, P is the basic stuff, p is everything I've been aware of, you'd be the first person to note they are using /var/temp and /var/log as separate partitions.

It's a whitelist test, so inxi has to know about the possible values to add them, so that's easy to correct. If you can think of others that could possibly be used as well add them to the issue report, it's easy to add stuff to that detection.

The best solution for the bios issue would be to actually detect if it's bios or uefi, which I'd need to pull out of /sys for newer gnu/linux systems, and out of dmidecode data for systems without that /sys data, like bsds and older linuxes.