aboutsummaryrefslogtreecommitdiffstats
path: root/inxi.changelog
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@unit193.net>2021-02-01 13:53:53 -0500
committerLibravatarUnit 193 <unit193@unit193.net>2021-02-01 13:53:53 -0500
commitbf0e64587af9db7f876d7d71416b40b5d170cc76 (patch)
tree3c61fc5a8d12bc3d1242ca90d0698f99b68786c2 /inxi.changelog
parent35876166db3cf927ff476f80da1ab8777b380151 (diff)
downloadinxi-bf0e64587af9db7f876d7d71416b40b5d170cc76.tar.bz2
inxi-bf0e64587af9db7f876d7d71416b40b5d170cc76.tar.xz
inxi-bf0e64587af9db7f876d7d71416b40b5d170cc76.tar.zst
New upstream version 3.3.00-1.upstream/3.3.00-1
Diffstat (limited to 'inxi.changelog')
-rw-r--r--inxi.changelog97
1 files changed, 97 insertions, 0 deletions
diff --git a/inxi.changelog b/inxi.changelog
index 6c52dae..5169c76 100644
--- a/inxi.changelog
+++ b/inxi.changelog
@@ -1,4 +1,101 @@
=====================================================================================
+Version: 3.3.00
+Patch: 00
+Date: 2021-01-28
+-----------------------------------
+Changes:
+-----------------------------------
+
+Bug fixes!! New Feature!! Edits, cleanups!!
+
+Bugs:
+1. Small bug, wrong regex would make mdraid unused report never show.
+Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
+
+2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
+inxi had a bunch of bugs around that. I'd assumed active and inactive would have
+roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
+for giving me the required data. This case when not corrected resulted in a
+spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
+
+3. A bug that probably never impacted anyone, but in SMART the matching rules
+failed to match field name Size[s]? in the logical/physical block sizes.
+However, those were already coming in from I believe pre-existing /sys data
+for the drives but now it's fixed anyway. I had not realized that smartctl
+made it plural when logical/physical were different, and singular when
+they were the same.
+
+4. Failed to use all possible sd block device major number matches, which
+led to false disk total/used reports, that is, totals less than used.
+
+5. Bug probably introduced in 3.2, zfs single array device did not show
+raid level.
+
+Fixes:
+1. Going along with bug 2, fixed some other admin/non admin report glitches.
+Made patterns more aggressively matching, whitelist based to avoid the types
+of syntax issues that caused bug 2.
+
+2. Added 'faulty' type to mdraid matches, that had not been handled.
+
+3. Found even more of those pesky 'card' references in help and man page,
+replaced all of them with 'device[s]'.
+
+4. Subtle fix, for debugger data collectors, added -y1 support, which can
+be useful at times.
+
+Enhancements:
+1. In USB data grabber, added fallback case for unspecified type cases, now
+uses a simple name/driver string test to determine if it's graphics, audio,
+or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
+
+2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
+Requires for the 'Report:' part hciconfig, which most all distros still have
+in their repos. With -a, shows an additional Info: line that has more obscure
+bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
+
+This closes the ancient, venerable issue #79, filed by mikaela so many years
+ago. Better late than never!! However, features like this were really difficult
+in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
+we'll slowly whittle away at these things when the mood, and global pandemic
+lockdowns, make that seem like a good idea...
+
+Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
+hopefully that's a correct way to determine bluetooth version, there was some
+ambiguity about that.
+
+-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
+devices, adding Chip IDs, Bus IDs, version info, and so on.
+Since this bluetooth report does not require root and is an upper case option,
+it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
+shows only if data is found. With -v7 or -R or -E, always shows, including
+no data found message.
+
+Includes a fallback report Report-ID: case where for some reason, inxi could
+not match the HCI ID with the device. That's similar to IF-ID in -n, which
+does the same when some of the IFs could not be matched to a specific device.
+
+3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
+actually useful for many cases of trying to figure out what devices are,
+though most users would not know what to do with that information, but that's
+why it's an -xxx option!
+
+4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
+The cornucopia flows its endless bounty over the grateful data collector, and,
+hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
+linux-lite users who really seem set on the impossible project of obtaining
+all the disks/vendors known to man.
+
+Changes:
+1. Small change in wording for mdraid report:
+'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
+and much more precise.
+
+
+-----------------------------------
+-- Harald Hope - Thu, 28 Jan 2021 19:34:17 -0800
+
+=====================================================================================
Version: 3.2.02
Patch: 00
Date: 2021-01-10