I've revised the logic slightly, and the fix for this specific user's issue is now in 2.2.37. When
or if unit193 packages that, and when or if that package gets into the appropriate debian pool, will
determine when the debian issue itself is resolved.
This may well create fresh new issues, but
I took a closer look, and reviewed enough user data sets to refresh my memory about reality re
distro id methods.
Here's the deal: inxi deals with the world as it actually exists, not as pedantic rules would like
the world to be. The empirical reality of how absurdly inconsistent and filthy
If I were you adam I'd stop trying to interpret things, you aren't very good at it, not in the
failed attempt to guess at the kfreebsd logic, and not in this case. Just provide the data that is
requested and leave it at that, saves us a lot of time. The debugging information you finally
Adam, I'm going to ignore this now, because you are refusing to do a few things:
1. one, you aren't providing the requested debugging information.
2. two, you keep believing that the fallback /etc/issue is the default value being printed, for no
actual reason I can see other than you believe
I forgot to update this, I also installed the latest stable kfreebsd vm shortly after posting my
last kfreebsd comment, just to check the overall inxi kfreebsd handling (I found one glitch that I
fixed, failure to blacklist /sys from the partition list, for some reason kfreebsd shows /sys
5 matches
Mail list logo
