I have the following output of inxi -c 0 -F
Partition: ID-1: / size: 3.4G used: 510M (16%) fs: ext3 dev: /dev/sda4
ID-2: /usr size: 20G used: 13G (70%) fs: ext4 dev: /dev/dm-1
ID-3: /boot size: 477M used: 39M (9%) fs: ext3 dev: /dev/sda3
ID-4: /home size: 50G used: 35G (74%) fs: ext4 dev: /dev/dm-2
ID-5: /var size: 23G used: 15G (68%) fs: ext3 dev: /dev/dm-4
ID-6: swap-1 size: 5.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
This misses /var/tmp (dm-0) and /var/log (sda8). I'm guessing all you're doing is the first level (e.g. /home, /boot, etc.).
Also a minor cosmetic gripe: BIOS is an acronym, so not sure why it's "Bios" in the output. I would also argue it would be more apropos to label it something like "platform firmware" or the like due to there being both BIOS and UEFI (which is often mis-called "BIOS," but it's not really).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: inxi 2.2.35-0ubuntu1 [modified: usr/bin/inxi]
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 25 18:12:16 2016
InstallationDate: Installed on 2012-09-02 (1453 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.1)
PackageArchitecture: all
SourcePackage: inxi
UpgradeStatus: Upgraded to xenial on 2016-08-11 (14 days ago)
https:/
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.