1883 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Harald Hope	5234e3903d	Huge upgrade, major rewrite/refactor, new features, everything is polished!!! ... Note that due to large number of internal changes to code, a separate INTERNAL CODE CHANGES section is at the bottom. Those are changes which in general do not impact what users see that much, but which definitely impact working on and with inxi! They also make errors less likely, and removed many possible bad data error situations. BUGS: 1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd never gotten a dataset for before, this tripped a series of errors in inxi, which were actually caused by small errors and failures to check certain things, as well as simply never assigning data in corner cases. This system used only dmi handles 6 and 7, which is a very rare setup, from the very early days of dmi data being settled, but it was valid data, and actually inxi was supposed to support it, because I'd never gotten a dataset containing such legacy hardware data, the support didn't work. There were actually several bugs discovered while tracking this down, all were corrected. 2. Going along with the cpu fixes below, there was a bug that if stepping was 0, stepping would not show. I had not realized stepping could be 0, so did a true/false test instead of a defined test, which makes 0 in perl always test as false. This is corrected. 3. While going through code, discovered that missing second argument to main::grabber would have made glabel tool (BSD I think mostly) always fail, without exception. That explains why bsd systems were never getting glabel data, heh. 4. Many null get_size tests would not have worked because they were testing for null array but ('','') was actually being returned, which is not a null array. The testing and results for get_size were quite random, now hey are all the same and consistent, and confirmed correct. 5. In unmounted devices, the match sent to @lsblk to get extended device data would never work with dm-xx type names, failed to translate them to their mapped name, which is what is used in lsblk matches, this is corrected. This could lead to failures to match fs of members of luks, raid, etc, particularly noticeable with complex logical device structures. This means the fallback filters against internal logic volume names, various file system type matches, would always fail. 6. A small host of further bugs found and fixed during the major refactor, but not all of them were noted, they were just fixed, sorry, those will be lost to history unless you compare with diffs the two versions, but that's thousands of lines, but there were more bugs fixed than listed above, just can't remember them all. FIXES: 1. There was some ambiguity about when inxi falls back to showing hardware graphics driver instead of xorg gfx driver when it can't find an xorg driver. That can happen for instance because of wayland, or because of obscure xorg drivers not yet supported. Now the message is very clear, it says the gfx software driver is n/a, and that it's showing the hardware gfx driver. 2. Big redo of cpu microarch, finally handled cases where same stepping/model ID has two micorarches listed, now that is shown clearly to users, like AMD Zen family 17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and a comment: note: check, like it shows for ram report when it's not sure. Shows for instance: arch: Zen/Zen+ note: check in such cases, in other words, it tells users that the naming convention basically changed during the same hardware/die cycle. 3. There were some raid component errors in the unmounted tests which is supposed to test the raid components and remove them from the mounted list. Note that inxi now also tests better if something is a raid component, or an lvm component, or various other things, so unmounted will be right more often now, though it's still not perfect since there are still more unhandled logical storage components that will show as unmounted when tney are parts of logical volumes. Bit by bit!! 4. Part of a significant android fine tuning and fix series, for -P, android uses different default names for partitions, so none showed, now a subset of standard android partitions, like /System, /firmware, etc, shows. Android will never work well though because google keeps locking down key file read/search permissions in /sys and /proc. 5. More ARM device detections, that got tuned quite a bit and cleaned up, for instance, it was doing case sensitive checks, but found cases where the value is all upper case, so it was missing it. Now it does case sensitive device type searches. 6. One of the oldest glitches in inxi was the failure to take the size of the raid arrays versus the size totals of the raid array components led to Local Storage results that were uselessly wrong, being based on what is now called 'raw' disk totals, that's the raw physical total of all system disks. Now if raid is detected the old total: used:... is expanded to: total: raw:... usable:....used:, the usable being the actual disk space that can be used to store data. Also in the case of LVM systems, a further item is added, lvm-free: to report the unused but available volume group space, that is, space not currently taken by logical volumes. This can provide a useful overview of your system storage, and is much improved over the previous version, which was technically unable to solve that issue because the internal structures did not support it, now they do. LVM data requires sudo/ root unfortunately, so you will see different disk raw totals depending on if it's root or not if there is LVM RAID running. Sample: inxi -D Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB lvm-free: 84.61 GiB used: 8.49 GiB (3.1%) lvm-free is non assigned volume group size, that is, size not assigned to a logical volume in the volume group, but available in the volume group. raw: is the total of all detected block devices, usable is how much of that can be used in file systems, that is, raid is > 1 devices, but those devices are not available for storage, only the total of the raid volume is. Note that if you are not using LVM, you will never see lvm-free:. 7. An anonymous user sent a dataset that contained a reasonable alternate syntax for sensors output, that made inxi fail to get the sensors data. That was prepending 'T' to temp items, and 'F' to fan items, which made enough sense though I'd never seen it before, so inxi now supports that alternate sensors temp/fan syntax, so that should expand the systems it supports by default out of the box. 8. Finally was able to resolve a long standing issue of loading File::Find, which is only used in --debug 20-22 debugger, from top of inxi to require load in the debugger. I'd tried to fix this before, but failed, the problem is that redhat /fedora have broken apart Perl core modules, and made some of them into external modules, which made inxi fail to start due to missing use of required module that was not really required. Thanks to mrmazda for pointing this out to me, I'd tried to get this working before but failed, but this time I figured out how to recode some of the uses of File::Find so it would work when loaded without the package debugger, hard to figure it, turned out a specific sub routine call in that specific case required the parentheses that had been left off, very subtle. 9. Subtle issue, unlike most of the other device data processors, the USB data parser did not use the remove duplicates tool, which led in some cases to duplicated company names in the output for USB, which looks silly. 10. Somehow devtmpfs was not being detected in all cases to remove that from partitions report, that was added to the file systen filters to make sure it gets caught. 11. Removed LVM image/meta/data data slices from unmounted report, those are LVM items, but they are internal LVM volumes, not available or usable. I believe there are other data/meta type variants for different LVM features but I have added as many types as I could find.. Also explictly now remove any _member type item, which is always part of some other logical structure, like RAID or LVM, those were not explicitly handled before. 12. Corrected the varous terms ZFS can use for spare drives, and due to how those describe slightly different situations than simply spare, changed the spare section header to Available, which is more accureate for ZFS. ENHANCEMENTS: 1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/ model/stepping IDs (E8C2), so that is fairly up to date now. 2. Added in a very crude and highly unreliable default fallback for intel: /sys/devices/cpu/caps/pmu_name which will show the basic internal name used which can be quite different from what the actual microarch name is, but the hope is that for new intel cpus that come out after these last inxi updates, something may show, instead of nothing. Note these names are often much more generic, like using skylake for many different microarches. 3. More android enhancements, for androids that allow reading of /system/build.prop, which is a very useful informative system info file, more android data will show, like the device name and variant, and a few other specialized items. You can see if your android device lets inxi read build.prop if you see under -S Distro: Android 7.1 (2016-07-23) or just Android. If it shows just android, that means it can't read that file. Showing Android however is also new, since while inxi can't always read build.prop if that file is there, it's android, so inxi finally can recognize it's in android, even though it can't give much info if it's locked down. Inxi in fact did not previously know it was running in android, which is quite different from ARM systems in some ways, but now it does. If the data is available, it will be used in Distro: and in Machine: data to add more information about the android version and device. 4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID, Logical reports. Note that /dev/mapper/ is removed from the mapped name since that's redundant and verbose and makes the output harder to read. For mapped devices, the new --logical / -L report lets you drill into the devices to find out what dm-xx is actually based on, though that is a limited feature which only supports drilling to a depth of 2 components/devices, there can be more, particularly for bcache, luks setups, but it's just too hard to code that level of depth, so something is better than nothing in this case, which is the actual choice I was faced, the perfect in this case really is/was the enemy of the good, as they say. 5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number, which again lets you trace each device around the system and report. 6. Added mdadm if root for mdraid report, that let me add a few other details for mdraid not previously available. This added item 'state;' to the mdraid report with right -x options. 7. Added vpu component type to ARM gfx device type detection, don't know how video processing vcu had escaped my notice. 8. Added fio[a-z] block device, I'd never heard of that before, but saw use of it in dataset, so learned it's real, but was never handled as a valid block device type before, like sda, hda, vda, nvme, mmcblk, etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number. 9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note that in their nomenclature, L0 and L1 are actually both L1, so add those together when detected. 10. RAM, thanks to a Mint user, antikythera, learned, and handled something new, module 'speed:' vs module 'configured clock speed:'. To quote from supermicro: <<< Question: Under dmidecode, my 'Configured Clock Speed' is lower than my 'Speed'. What does each term mean and why are they not the same? Answer: Under dmidecode, Speed is the expected speed of the memory (what is advertised on the memory spec sheet) and Configured Clock Speed is what the actual speed is now. The cause could be many things but the main possibilities are mismatching memory and using a CPU that doesn't support your expected memory clock speed. Please use only one type of memory and make sure that your CPU supports your memory. >>> 11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This will let users make apples to apples speed comparisons between different systems. Since MT/S is largely standard now, there's no need to translate that to MHz. 12. And, even more!! When RAM speeds are logically absurd, adds in note: check This is from a real user's data by the way, as you can see, it triggers all the new RAM per Device report features. Sample: Memory: RAM: total: 31.38 GiB used: 20.65 GiB (65.8%) Array-1: capacity: N/A slots: 4 note: check EC: N/A Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 61910 MT/s (30955 MHz) note: check Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 2 MT/s (1 MHz) note: check 13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity exists, here, now, and manifests every day!! Thanks to linux-lite hardware database for this eternally generating list. Never underestimate the creativity of mankind to make more disk drive companies, and to release new model IDs for existing companies. Yes, I feel that this is a metaphore for something much larger, but what that is, I'm not entirely clear about. CHANGES: 1. Recent kernel changes have added a lot more sensor data in /sys, although this varies system to system, but now, if your system supports it, you can get at least partial hdd temp reports without needing hddtemp or root. Early results suggest that nvme may have better support than spinning disks, but it really varies. inxi will now look for the /sys based temp first, then fall back to the much slower and root / sudo only hddtemp. You can force hddtemp always with --hddtemp option, which has a corresponding configuration item. 2. The long requested and awaited yet arcane and obscure feature -L/--logical, which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well as handling LVM raid, both regular and thin, is now working, more or less. This took a lot of testing and will probably not be reasonably complete for a while, mainly because the levels of abstraction possible between lvm, lvm raid, mdraid, LUKS, bcache, and other caching and other encryption options are just too deep to allow for easy handling, or easy outputs. But a very solid and good start in my view, going from nothing to something is always a big improvement!! LVM reports require root/sudo. This will, finally, close issue #135. 3. Going along with -L, and serving as a model for the logic of -L, was the complete refactor of -R, RAID, which was a real mess internally, definitely one of the messiest and hardest to work with features of inxi before the refactor. It's now completely cleaned up and modularized, and is easy to add raid types, which was not possible before, now it cleanly supports zfs, mdraid, and lvm raid, with in depth reports and added items like mdraid size, raid component device sizes and maj:min numbers if the -a option is used. Note that LVM RAID requires root/sudo. 4. Added some more sensors dimm, volts items, slight expansion. Note that the possible expansion of sensors made possible by the recently upgraded sensors output logic, as well as the new inxi internal sensors data structure, which is far more granular than the previous version, and allows for much more fine grained control and output, though only gpu data currently takes advantage of this new power under the covers, although as noted, the /sys based hdd temps use the same source, only straight from /sys, since it was actually easier using the data directly from sys than trying to map the drive locations to specific drives in sensors output. Well, to be accurate, since now only board type sensors are used for the temp/fan speed, voltage, etc, reports, the removal of entire sensor groups means less chance of wrong results. 5. To bring the ancient RAID logic to fit the rest of inxi style, made zfs, mdraid, and lvm raid components use incrementing numbers, like cpu cores does. This got rid of the kind of ugly hacks used previously which were not the same for zfs or mdraid, but now they are all the same, except that the numbers for mdraid are the actual device numbers that mdraid supplies, and the LVM and ZFS numbers are just autoincremented, starting at 1. 6. Changed message <root/superuser required> to <superuser required> because it's shorter and communicates the same thing. INTERNAL CODE CHANGES: 1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All tests passed, no legacy code issues in inxi as of now. 2. Although most users won't notice, a big chunk of inxi was refactored internally, which is why the new -L, the revamped -R, and the fixed disk totals finally all can work now. This may hopefully result in more consistent output and fewer oddities and randomnesses, since more of the methods all use the same tools now under the covers. Ths refactor also significantly improved inxi's execution speed, by about 4-5%, but most of those gains are not visible due to the added new features, but the end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but does more, and does it better, internally at least. If you have a very good eye you may also note a few places where this manifests externally as well. Last I checked about 10-12% of the lines of inxi had been changed, but I think that number is higher now. Everything that could be optimized was, everything could be made more efficient was. 3. Several core tools in inxi were expanded to work much more cleanly, like reader(), which now supports returning just the index value you want, that always happened on the caller end before, which led to extra code. get_size likewise was expanded to do a string return, which let me remove a lot of internal redundant code in creating the size unit output, like 32 MiB. uniq() was also redone to work exclusively by reference. 4. Many bad reference and dereference practices that had slipped into inxi from the start are mostly corrected now, array assignments use push now, rather than assign to array, then add array to another array, and assign those to the master array. Several unnecessary and cpu/ram intensive copying steps, that is, were removed in many locations internally in inxi. Also now inxi uses more direct anonymous array and hash refernce assignments, which again removes redundant array/hash creation, copy, and assignment. 5. Also added explicit -> dereferencing arrows to make the code more clear and readable, and to make it easier for perl to know what is happening. The lack of consistency actually created confusion, I was not aware of what certain code was doing, and didn't realize it was doing the same thing as other code because of using different methods and syntaxes for referencing array/hash components. I probably missed some, but I got many of them, most probably. 6. Instituted a new perl builtin sub routine rule which is: if the sub takes 2 or more arguments, always put in parentheses, it makes the code much easier to follow because you see the closing ), like: push(@rows,@row); Most perl builtins that take only one arg do not use parentheses, except length, which just looks weird when used in math tests, that is: length($var) > 13 looks better than length $var > 13. This resolved inconsistent uses that had grown over time, so now all the main builtins follow these rules consistently internally. Due to certain style elements, and the time required to carefully go through all these rules, grep and map do not yet consistently use these rules, that's because the tendency has been to use the grep {..test..} @array and map {...actions...} @array 7. Mainly to deal with android failures to read standard system files due to google locking it down, moved most file queries to use -r, is readable, rather than -e, exists, or -f, is file, unless it only needs to know if it exists, of course. This fixed many null data errors in android even on locked androids. 8. Added in %mapper and %dmmapper hashes to allow for easy mapping and unmapping of mapped block devices. Got rid of other ways of doing that, and made it consistent throughout inxi. These are globals that load once. 9. Learned that perl builtin split() has a very strange and in my view originally terrible decision that involves treating as regex rules string characters in split string, like split('^^',$string), which should logically be a string value, not a ^ start search followed by a ^, but that's how it is, so that was carefully checked and made consistent as well. Also expanded split to take advantage of the number of splits to do, which I had only used occasionally before, but only updated field/value splits where I have a good idea of what the data is. This is very useful when the data is in the form of field: value, but value can contain : as well. You have to be very careful however, since some data we do want in fact the 2nd split, but not the subsequent ones, so I only updated the ones I was very sure about. 10. Going along with the cpu microarch fixes, updated and cleaned up all the lists of model/stepping matches, now they are all in order and much easier to scan and find, that had gotten sloppy over the years. 11. More ARM, moved dummy and codec device values into their own storage arrays, that let me remove the filters against those in the other detections. Makes logic easier to read and maintain as well.	2020-12-15 15:13:14 -08:00
Harald Hope	0eedb2c89e	typo fixes	2020-11-11 15:49:05 -08:00
Harald Hope	f30d907c4c	man page fix	2020-11-11 15:45:10 -08:00
Harald Hope	0e56aeeb74	updted changelog	2020-11-11 15:35:59 -08:00
Harald Hope	285c6f715f	Bug fixes, new features!! Update now!! Or don't, it's up to you. ... Bugs: 1. Let's call some of the android fixes and debugger failures bugs, why not? Those are fixed. Note that many of these fixes will impact any system that is ARM based, not just android. Fixes: 1. Related to issue #226 which was a fine issue, fine tuned the debugger debuggers to allow for smoother handling of /sys parse failures. Also added debugger filters for common items that would make the /sys parser hang, oddly, most seem to be in /sys/power for android devices. 2. Added some finetunings for possible mmcblk storage paths, in some cases, an extra /block is added, which made inxi think mounted drives were unmounted. I've never seen this extra /block except on mmcblk devices on android, but you never know, it could be more widespread. 3. Also mainly related to android, but maybe other ARM devices, in some cases, an errant 'timer' device was appearing as a cpu variant, which is wrong. That was a corner case for sure, and part of the variant logic in fact uses timer values to assign the actual cpu variants, but it was wrong in this case because it was ....-timer-mem, not ...-timer, which led to non-existent CPU variants showing. 4. Issue #236 by ChrisCheney pointed out that inxi had never updated its default /proc/meminfo value to use the newer MemAvailable as default if present, which led to incorrect memory used values showing up. That's because back in the old days, we had to construct a synthetic Memory used from MemFree, buffers, cache, etc, but that wasn't always right, since sometimes the cache actually isn't available, often is, but not always. 34e431b0ae This commit on the kernel explains it pretty clearly. Thanks Chris for bringing this to our attention. 5. Kind of more future-proofing, got rid of a bunchy of hard-coded strings internally and switched those to use the row_defaults values, which is where string messages are supposed to go. That was mostly in the initial program check messages on start-up, but also a few other stray ones. Also consolidated them a bit to get rid of redundant messages, and added more variable based messages, like for missing/permissions on programs etc. The idea in general is that all the strings are contained in subs so that in theory they could be swapped for other strings, eg, languages, but honestly, I no longer see this as very likely to ever happen. But it's still nice to be consistent internally and not get sloppy with english strings. This also got rid of some largely redundant items in row_defaults, and expanded the list of handled events, and of variable based events, so it shouldn't be as necessary to add new row_defaults items for similar events. Enhancements: 1. Debugger item to maybe try to find distro OEM, this was connected with issue #231 but the issue poster vanished, and didn't do the work required, so this one won't happen until someone who cares [not me, that is] does the required work. It's always funny to see how quickly people vanish when they have to do the actual boring research that they want me to do for them, lol. Or maybe, sigh is more appropriate than lol. But it is pretty much par for the course, sad to say. Or maybe this was an OEM hoping to have someone do their corporate work for them for free, who knows. Anyway, there's a certain category of items that I'm reasonably happy to implement, but NOT if I have to do all the boring research work, so such features being added will depend on the poster actually doing the boring work. I've gotten burned on this a few times, cpu arch: for example, some guy said he'd track that and provide updates, he never even made it to the first release, so I got stuck doing that one forever after. But that one at least has some general value, so that's ok more or less, but I definitely won't take on stuff that I really don't personally care at all about unless the person requesting the feature does all the work beforehand. The boring part, that is.... 2. Related to issue #226, much improved android ID and many small android fixes for machine data etc. Now uses /system/build.prop for some data, which is a nice source, sadly, most modern android devices seem to be locked down, with both build.prop and /sys locked down, which makes inxi unable to actually get any of that data, but if your device either does not have these root only readable, or if you have an android rooted phone, the android support will be more informative. Hint: if you run inxi in termux on your non rooted android device, and it shows you what android version you are using in System:... Distro: line, then your android is not locked down. I have one such phone, android 7.1, but I cannot say how usual or non usual this is. The poster of issue #226 for instance had to root his android 7 phone to get this data to display. So it seems to vary quite a bit. Note that due to these file system lockdowns, in general, trying to do android arm support remains largely a waste of time, but on some devices sometimes, you can now get quite nice system info. As I noted in the issue, if I can't get the features to work on a non rooted phone in my possession, I'm probably not going to try to do the work because it's too hard to try to work on android issues without having the device in front of you for testing and debugging. In this case, one of my phones did work, so I did the work just to see where android is at now. Android showed some slightly odd syntaxes for some devices, but those are now handled where I got a dataset for them that revealed the changes required. 3. Also related to issue #226 for termux in android, will show -r info. That's an apt based package manager, but termux puts the apt files somewhere else so needed to change paths if those alternate paths existed for apt. 4. Added PARTFLAGS to debugger to see what knd of data that will yield, that's a lsblk key/value pair. 5. Just because it's easy to do, added new -Ixxx item, wakeups: which is a subset of Uptime, this will show how many times the system has been woken from suspend since the last boot. If the system has never been suspended, shows 0. 6. Many more disk vendors and disk IDs. The list just never ends, possibly a metaphor for something, the endless spinning of maya, who knows? 7. Added newest known ubuntu release, hirsute, to buntu ID logic. Might as well catch them early, that will be 21.04.	2020-11-11 15:35:08 -08:00
Harald Hope	e45c696010	Bug fixes, updates!!! Yes!! Why wait!!! Can't stay frozen forever! ... Bugs: 1. Not an inxi bug, but a weird change in defaults for ubuntu GNOME ENV variable values when running at least the gnome desktop, result to end users appears to be a bug. This resolves issue #228 Note that so much weird non desktop data was put into those environmental variables that inxi simply could make no sense of it. The fix was to make the detections more robust, using regex instead of string compare, as well as to at least try to strip out such corrupted data values, though that can never be fully predictable. As far as I know, this issue only hits ubuntu gnome desktops, I've never seen these value corruptions on any other distro, or on any other ubuntu desktop, though they may be there, but I'm not going to test all the ubuntu spins to find out. I'm hoping the combination of logic fixes and junk data cleaning will handle most future instances of these types of corruptions automatically. Again, this only happens on relatively laste ubuntu gnomes as far as I know. Fixes: 1. An oversight, added sshd to list of whitelisted start clients. This permits expected output for: ssh <name@server> inxi -bay that is, running inxi as an ssh command string. Should have done that a while ago, but better late than never. This corrects issue #227, or at least, has a better default, it worked fine before, but required using --tty to reset to default terminal behavior. The problem is that if inxi can't determine what it's running in, it defaults to thinking it's in an IRC client, and switches to IRC color codes, among other changes. But it was nice to get sshd covered automatically so users don't have to know the --tty option. Changes: 1. More disk vendors and vendor IDs!!! Yes, that's right, the list never ends!!	2020-10-16 13:54:25 -07:00
Harald Hope	4e4c0d8e14	more edits	2020-09-29 16:41:46 -07:00
Harald Hope	31e1a933a0	small edit	2020-09-29 16:32:31 -07:00
Harald Hope	ef428e75e1	Bug fixes, feature updates, changes!! ... Bugs: 1. There was a glitch in the pattern that made -D samsung / seagate not ID right, fixed. 2. I do not like calling this a bug, because it's not an inxi bug, it's an upstream regression in the syntax used in /proc/version, they changed a fully predictable gcc version .... to a random series of embedded/nested parentheses and other random junk. inxi tries to deal with this regression, which will be perceived as a bug in systems running kernel 5.8 or newer and inxi 3.1.06 or older, since it will fail to show the kernel build compiler version since it can't find it in the string. I really dislike these types of regressions caused by bad ideas done badly and without any thought to the transmitted knowledge base, but that's how it goes, no discipline, I miss the graybeards, who cared about things like this. Fixes: 1. more -D nvme id changes, intel in this case. 2. FreeBSD lsusb changed syntax, which triggered a series of errors when run. Since I never really got the required data [hint bsd users, do NOT file issues that you want fixed and then not provide all the data required, otherwise, really, why did you file the issue? did you expect magic pixies to fly in with the required data?] See the README.txt for what to do to get issues really handed in BSDs. tldr; version: if you won't spend the time providing data and access required, I won't spend the time on the issue, period, since if you don't care enough to do those simple steps, why on earth do you expect me to? Changes: 1. -C 'boost' option changed from -xxx feature to -x feature. Consider it a promotion! 2. Added --dbg 19 switch to enable smart data debugging for -Da. 3. Some new tools to handle impossible data values for some -D situations for SMART where the smart report contains gibberish values, that was issue #225 -- tools were convert_hex and is_Hex. The utility for these is limited, but might be of use in some cases, like handling the above gibberish data value.	2020-09-29 16:22:15 -07:00
Harald Hope	ddbd8e8679	fixed seagate/samsung glitch	2020-08-17 15:23:55 -07:00
Harald Hope	b1650ea2a8	New features, new changes, new bug fixes!!! Excitement!!! Thrills!!! ... Bugs: 1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank, only inxi short, which I rarely use so I didn't notice. 2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed. Also failed to test for null data, so showed errors for packages as well. Both fixed. 3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME drives do NOT follow the age old /proc/partitions logic where if the minor number is divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not a partition. nvme drives use a random numbering when > 1 nvme drives are present, and the old tests would fail for all nvme drivers more than the first one, which led to wrong disk size totals. Thanks gardotd426 who took the time to help figure this out in issue #223 - fix is to not do that test for nvme drives, or rather, to add a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor number. Fixes: 1. Corrected indentation for block sizes, children were not indented. 2. Updated some older inxi-perl/docs pages, why not, once in a while? 3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been corrected, and the kernel gcc version now shows correctly for the previous syntax and the new one. Hopefully they do not change it again, sigh... 4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and are also usually not board/cpu sensors, but things like ath10, iwl, etc, network, or disk sensors, etc. In some cases hwmon sensor data would appear Enhancements: 1. Big sensors refactor, now inxi supports two new sensors options: --sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that in the refactored logic, and in the old logic, gpu sensors were already excluded. Now other hardware specific sensors like network are excluded as well. --sensors-use - use ONLY list of supplied sensor IDs, which have to match the syntax you see in lm-sensors sensors output. Both accept comma separated list of sensors, 1 or more, no spaces. The refactor however is more far reaching, now inxi stores and structures data not as a long line of sensors and data without differentiation, but by sensor array/chip ID, which is how the exclude and use features can work, and how granular default hardware sensor exclusions and uses can happen. This is now working in the gpu sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk temperature sensors values, which will lead in some cases to being able to get sensors data for disks without root or hddtemp. This is a complicated bit of logic, and I don't have time to do it right now, but the data is now there and stored and possible to use in the future. To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data and its structures, which makes debugger a lot easier for new features. This issue was originally generated by what was in my view an invalid complaint about some inxi sensors defaults, which led me to look more closely at sensors logic, which is severely lacking. More work on sensors will happen in the future, time, health, and energy permitting. 2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor data will be added as new data samples show what will be available for the free modules like amdgpu, nouvean, and the intel graphics modules. 3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended, so statement remains true. Thanks linux-lite hardware database. Changes: 1. This has always bugged me since it was introduced, the primary cpu line starter Topology: which was only technically accurate for its direct value, not its children, and also, in -b, cpu short form was using the value as the key, which is a no-no, I'd been meaning to fix that too, but finally realized if I just make the primary CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both problems. To keep the -b cpu line as short as before, I removed the 'type:' and integraged that value into the primary Info: string: CPU: Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz -b 3.1.05 and earlier: CPU: 6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz These resolve something that has irked me for quite a while, 'Topology:' didn't fit, it was too geeky, and worst, it only applied to the value directly following it, NOT to the rest of the CPU information. It also could not be shortened or abbreviated since then it would have made no actual sense, like topo:, and the same issue with value being used for key in -b, and wrong word for line starter in -C would have existed. Besides, someone might think I was trying to make a subtle reference to the great Jodorowsky film 'El Topo', which would be silly, because that's art, and this is just some system specs that are reasonably readable... 2. Was using opendns for WAN dig IP address, but apparently cysco bought that company, and now I've noticed the old opendns dig queries were failing more and more, so replaced that with akamai dig requests. Also made the WAN IP fallback to HTTP IP method if dig failed. New option: --no-http-wan and config item NO_HTTP_WAN with override --http-wan added to let you switch off http wan IP requests if you want. Note that if dig fails, you will get no wan ip address. Updated/improved error messages to handle this more complex set of wan ip options, so hopefully the error alert message will in most cases be right. 3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming from the old techpatterns.com/incoming. Updated man/help to remove those urls too.	2020-08-16 15:27:11 -07:00
Harald Hope	f16e714dc6	two bugs fixed, first: forgot to set shell generator on inxi short feature, ... so shell is blank, second, unhandled new 5.8 kernel /proc/version syntax. Normally I'd do a new numbered release, but I want these out asap and will do a full new release later, there are some features under development in pinxi for sensors that will take some time to handle.	2020-08-10 19:08:29 -07:00
Harald Hope	2ebd05dfb6	bug fix for pacman-g2, used bad data source for the info command for g2.	2020-08-10 18:17:07 -07:00
Harald Hope	6ce9149bb1	bug fix, bad copy paste	2020-07-28 07:54:33 -07:00
Harald Hope	b3b734d87a	tiny patch to fix indentation on disk block-physical	2020-07-27 15:22:41 -07:00
Harald Hope	3224a39f80	man page typo fix	2020-07-26 20:36:27 -07:00
Harald Hope	bbcaed9475	Bug fixes!!! New Features!! Why wait!!! ... Bugs: 1. Issue #220 on github: inxi misidentified XFCE as Gnome. This was a kind of core issue, and pointed to some logic that needed updating, and some inadequate assumptions made, and some too loose cascade of tests. Hopefully now xfce will almost never get misidentified, and the other primary desktops ID'ed either from $ENV or from xrop -root will be slightly more accurately identified as well. Note that this fix creates a possibility for obscure misconfigured desktops to be ID'ed wrong, but in this case, that will be technically a bug for them, but with the new fixes, that situation will be cleaner to handle internally in the desktop ID logic. Also tightened the final Gnome fallback detection to not trigger a possible false positive, it was testing for ^_GNOME but that is not adequate, because some gnome programs will trigger these values in xprop -root even if GNOME is not running. Should be safer now, hopefully no new bugs will be triggered by these changes. Fixes: 1. Missed an indentation level for -y1, gcc alt should have been indented in one more level, now it is. 2. In disk vendors/family, didn't clean items starting with '/', this is now corrected. Yes, some do, don't ask me why. Might be cases like: Crucial/Micron maybe, where the first ID is grabbed, not sure. Enhancements: 1. New Disk vendors, vendor IDs!!! The list never ends!!! We've finally found infinity, and it is the unceasing wave of tiny and not so tiny disks and their Ids. 2. New feature: for -Aa, -Na/-na/-ia, -Ga, now will add the modules the kernel could support if they were available on the Device-x lines of those items. This was made an -a option because it really makes no sense, if it's a regular option, users might think that for example an nvidia card had a nouveua driver when it didn't, when in fact, all the kernel is saying is that it knows those listed modules 'couid' be used or present. This corresponds to the Display: item in -Ga, that lists 'alternate:' drivers that Xorg knows about that could likewise be used, if they were on the system. In other words these are --admin options because otherwise users might get confused, so this is one where you want to know the man explanation before you ask for it. It is useful however if you're not sure what your choices are for kernel modules. When the alternate driver is the same as the active driver, or if none is found, it does not show the alternate: item to avoid spamming.	2020-07-26 19:22:59 -07:00
Harald Hope	776c788273	one more changelong typo fix	2020-06-28 22:42:50 -07:00
Harald Hope	7255a3dedc	fixed changelog typos	2020-06-28 22:40:03 -07:00
Harald Hope	0645c3a7a6	New version, new man, huge update, bug fixes, cleanups, updates!! ... What started as a relatively minor issue report ended up with a refactor of big chunks of some of the oldest code and logic in inxi. So many bugs and fixes, updates, and enhancements, that I will probably miss some when I try to list them. Bugs: 1. In the process of fixing an issue about sudo use triggering server admin emails on failure, when --sudo/--no-sudo and their respective configuration items were added, sudo was inadvertently disabled because the test ran before the options were processed, which meant the condition to set sudo data was always false, so sudo for internal use was never set. The solution was to set a flag in the option handler and set sudo after options or configs run. 2. Issue #219 reported gentoo and one other repo type would fail to show enabled repos, and would show an error as well, this was due to forgetting to make the match test case insensitive. If only all bugs were this easy to fix!! 3. I'd seen this bug before, and couldn't figure out why it existed. It turned out that the partition blacklist filters were running fine in the main partition data tool, but I had forgotten to add in corresponding lsblk partition data filters, lol, so when the logic went back and double checked for missing partitions [this feature had been if i remember right to be able to show hidden partitions, which the standard method didn't see, but lsblk did, anyway, when the double check and add missing partitions logic ran, inxi was putting back in the blacklisted partitions every time, despite the original blacklists working well and as intended. This was fixed by adding in all the required fs type blacklists, then adding in comments above each black list reminding coders that if they add or remove from one blacklist, they have to do the same on the other. 4. Found while testing something unrelated on older vm, the fallback case for cpu bugs, which was supposed to show the basic /proc/cpuinfo cpu bugs, was failing inexplicably because the data was simply being put into the wrong variable name, sigh. Fixes: 1. While not technically an inxi bug, it would certainly appear that way to anyone who triggered it. We'd gotten issue reports before on this, but they were never complete, so couldn't figure it out. Basically, if someone puts inxi into a simple script that is $PATH [this was the missing fact needed to actually trigger this bug in order to fix it], the script [not inxi], will then enter into an endless loop as inxi queries it for its version number using <script name> --version. This issue didn't happen if the script calling inxi was not in PATH, which is why I'd never been able to figure it out before. Only simple scripts with no argument handlers could trigger this scenario, and only if they were in PATH. Fixing this required refactoring the entire start get_shell_data logic, which ended up with a full refactor of the program_version logic as well. The fix was to expand the list of shells known by inxi so it would be able to recognize when it was in a shell running a script running inxi. This resulted in several real improvements, for instance, inxi will now almost always be able to determine the actual shell running inxi, even when started by something else. It will also never use --version attempts on programs it does not know about in a whitelist. So we lose slightly the abilty to get version data on unknown shells, but we gain inxi never being able to trigger such an infinite loop situation. 2. As part of the program_version refactor, a long standing failure to get ksh, lksh, loksh, pdksh, and the related posh shells, all of which ID their version numbers only if they are running the command in themselves. The mistake had been having the default shell run that command. These all now correctly identify themselves. 3. As part of the wm upgrades, many small failures to ID version numbers, or even wm's, in some cases, were discovered when testing, and corrected. Some I had not tested, like qtile, and the lisp variants, were not being detected correctly by the tests due to the way python or lisp items are listed in ps aux. 4. As part of the wm update and program_version refactor, updated and simplified many desktop and wm detections and logic blocks. Ideally this makes them more preditable and easy to work on for the future. 5. As some last tunings for the new -y1 key: value pair per line output option, fixed some small glitches in -b indentation. Also improved RAID indenting, and Weather, and made it all very clean and predictable in terms of indentations. 6. Something I'd slightly noticed but never done anything about, while testing desktop fixes, I realized that for Desktop: item, dm: is a secondary data type, but if it's Console:, then DM: is a primary data type, not a secondary one. So now if Console: it becomes DM: whic makes sense, previously it implied a dm: was used to start the console, which was silly. Also, since often the reason it's Console: with no dm in the first place is that it's a server with no dm. So now if console, and no dm detected, rather than showing DM: N/A it just doesn't show dm at all. 7. As part of the overall core refactor, the print_data logic was also refactored and simplified, by making -y1 a first class citizen, it led to significantly different way of being able to present inxi data on your screen, and now print_data logic is cleaner and reflects these changes more natively, all the initial hacks to get this working were removed, and the logic was made to be core, not tacked on. 8. A small thing also revealed in issue #219, battery data was not being trimmed, not sure how I missed that, but in some cases, space padding was in the values and was not removed, which leads to silly looking inxi output. 9. Several massive internal optimizations, which were tested heavily, led to in one case, 8-900x faster execution the second time a data structure is used, previously in program_values the entire list was loaded each time program_values was called, now it's loaded into a variable on first load and the variable is used for the tests after that. This was also done for the vendor_version for disk vendors, which also features a very long data structure which can be loaded > 1 times for instances where a system has > 1 disk. I also tested while I was at it, to see if loading these tyeps of data structures, arrays of arrays, or hashes of arrays, by reference, or by dereferencing their arrays, was faster, and it proved that it's about 20% faster to not dereference them, but to use them directly. So I've switched a number of the fixed data structures internally do use that method. Another tiny optimization was hard resetting the print_data iterator hash, while this would never matter in the real world, it showed that resetting the iterator hash manually was slightly more efficient than resetting it with a for loop. 10. While not seen inside inxi, I updated and improved a number of the vm's used to test inxi and various software detections, so now I have a good selection, going back to 2008 or so, up to current. This is helpful because things like shells and window managers and desktops come and go, so it is hard to test old detections on new stuff when you can't install those anymore. You'll see these fixes in many of the less well known window managers, and in a few of the better known ones, where in some cases the detections were damaged. 11. As part of the program_version refactor, updated and fixed file based version detections, those, ideally, will almost never be used. Hopefully programmers of things like window managers, shells, and desktops, can learn how to handle --version requests, even though I realize that's a lot harder than copying someone's code and then rebranding as your own project, or whatever excuse people have for not including a --version item in their softaware. Enhancements: 1. As a result of the shell, start shell, shell parent refactors, inxi was able to correctly in most cases deetermine also the user default shell and its verison, so that was added as an -Ixxx option: Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16 2. As part of the program_version refactor, a more robust version number cleaner was made, which now allows for much more manipulation of the version number string, which sometimes contains, without spaces, non version number ' info right before the actual version. 3. Many more wm IDs were created and tested, and some old virtual machines that were used years ago were used again to test old window managers and their IDs, as well as new vms created to test newer ones. Many version IDs and WM ids were fixed in this process as well. All kinds of new ones added, though the list is basiclaly endless so ideally inxi would only use its internal data tables for window managers that have actual users, or did. 4. First wayland datatype, now it may show Display ID: with -Ga, so far that's the only wayland screen/display data I can get reliably. 5. As part of the shell parent/started in: updates and fixes, added every shell I could find, and installed and tested as many of them as possible to verify that either they have no version method, or that their version method works. This shell logic also is used to determine start parent. Obviously using whitelists of things that can change over time isn't ideal, but there was no way to actually do it otherwise. The best part of the fixes is that it's now remarkably difficult to trick inxi into reporting the wrong shell, and it generally will also get the default shell right, though I found cases in testing where a shell when started replaces the value in $SHELL with itself. 6. I found a much faster and reasonably reliable way to determine toolkits used by gtk desktops, like cinnamon, gnome, and a few others. Test is to get version from gtk-launcher, which is MUCH faster than doing a package version query on the random libgtk toolkit that might be tested, and actually was tested for pacman, apt, and rpm in the old days, but that was removed because it was a silly hack. It's possible that now and then gtk desktops will be 0.0.1 versions off, but in most cases, the version matched, so I decided to restore the tk: item for a selection of gtk or gnome based desktops. So now gtk desktops, except mate, which of course will be using gtk 2 for a while longer, toolkit version should be working again, and the new method works on everything, unlike the old nasty hack that was used, which required package queries and guessing at which gtk lib was actually running the desktop, it was such a slow nasty hack that it was dumped a while ago, but this new method works reliably in most cases and solves most of the issues. 7. As part of the overall program_versions refactor, the package version tester tool was extended to support pacman, dpkg, and rpm, which in practical terms covers most gnu/linux users and systems. Since this feature is literally only used for ASH and DASH shell version detections, it was really just added as a proof of concept, and because it fit in well with the new Package counts feature of -I/-r. 8. Updated for version info a few other programs, added compositors as well. 9. Last but not least!! More disk vendor IDs, more disk vendors!! And found another source to double check vendor IDs, that's good. New Features: 1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most package managers plus snap, flatpak, and appimage. I didn't test appimage so I'm not 100% sure that works, but the others are all tested and work. If -r, Packages shows in the Repos item as first row, which makes sense, packages, repos, fits. Note that in some systems getting full package counts takes some time so it's an -x option not default. If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia, the following data shows: * -Ix or -rx: show total package counts: Packages: 2429 * -Ixx or -rxx: shows Packages then counts by package manager located. If there was only one package manager with packages, the total moves from right after Packages: to the package manager, like: Packages: apt: 3241 but if there were for example 2 or more found, it would show the total then: Packages 3245 apt:3241 snap: 4 * -Ia or -ra: adds package managers with 0 packages managed, those are not show with -xx, and also shows how many of those packages per package manager is a library type lib file. Sample: inxi -Iay1 Info: Processes: 470 Uptime: 8d 10h 42m Memory: 31.38 GiB used: 14.43 GiB (46.0%) Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 5/6/7/8/9 Packages: apt: 3685 lib: 2098 rpm: 0 Shell: Elvish v: 0.13.1+ds1-1 default: Bash v: 5.0.16 running in: kate pinxi: 3.1.04-1	2020-06-28 22:22:12 -07:00
Harald Hope	03e6abe3e2	fixed accidental patch number bump	2020-06-17 12:20:42 -07:00
Harald Hope	e7f7110e6c	Fixed a bug with repos, failed to do case insensitive test, which ... resulted in issue #219 failure.	2020-06-17 12:18:17 -07:00
Harald Hope	166c1364d2	Big internal refactor!! Fully adjustable indentation logic, built in, native! ... NOTE: none of these changes have any impact on normal inxi -y -1, -y, or -y xx operation, everything will remain exactly the same, this only changes and makes robust -y 1 single key: value pair per line output. 3.1.03 finishes the -y1 introduced in 3.1.02, but makes it a core part of the inxi logic for line printing, not a tacked on afterthought. Because the first draft of this in 3.1.02 was really a hack tacked onto the existing logic, which was not very flexible or robust, and required way too much literal test logic in the black box print_data() subroutine, which is supposed to be a 'dumb' logic, that just does what you give it automatically, I added in key changes that hard code the indentations per key, like so: Now: 34#0#3#key-name Before: 34#key-name Note that anyone using the json or XML output option may need to redo their code a bit to handle these extra 2 values that preface the actual key names. Fixes: 1. In order to make this work, changed a few small things internally, a few key names were slightly altered to make them more clear. Changes: 1. Redo of all internal full key strings, added two new # separated items: xx#x#y#key-name: * xx remains the main 0 padded 2 digit sorter per row/block. * x is a new 0/1 boolean, that shows if the value is a container or not. As currently implemented probably not hugely useful since it won't say when the following items it is a container of ends. Note that the following y value will always be 1 for the item contained by the container, so you can check that way if you want. the next item can also be a container, but it would have either the same indentation level as the previous container or be different. Thus, if a key is a container, it can contain either non containers, or other containers, but that primary container does not end until the indent value equals or is less than the indent value of the first container. If you are a programmer you should be able to figure this out. * y is the indentation level, 0-xx is supported, but in practical terms, only 4 levels are used. For single line output, these set the indentation for that key. * key-name remains the key string ID name. 2. For -y 1 -G will show drivers then indented one more level unloaded, FAILED, and alternate: to make it clear those are a subset of drivers. driver: itself will contain the actual driver. In cases where no driver is loaded, a note will show indented after driver: 3. For -y 1, driver v: versions will be indented 1, and driver will be a container that contains that version key: value pair. Samples: ----------------------------------- inxi -Razy1 RAID: Device-1: g23-home type: zfs status: ONLINE size: 2.69 TiB free: 1.26 TiB allocated: 1.43 TiB Array-1: mirror status: ONLINE size: 1.82 TiB free: 602.00 GiB Components: online: sdb sdc Array-2: mirror status: ONLINE size: 888.00 GiB free: 688.00 GiB Components: online: sdd sde ----------------------------------- sudo inxi -dazy1 Drives: Local Storage: total: 1.98 TiB used: 1.43 TiB (72.2%) ID-1: /dev/sda vendor: Intel model: SSDSC2BW180A4 family: 53x and Pro 1500/2500 Series SSDs size: 167.68 GiB block size: physical: 512 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s serial: <filter> rev: DC32 temp: 37 C scheme: MBR SMART: yes state: enabled health: PASSED on: 291d 17h cycles: 1346 read: 431.94 GiB written: 666.16 GiB Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH20LS10 rev: FL00 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running ----------------------------------- inxi -Aazy1 Audio: Device-1: NVIDIA High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:0be3 Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 0b:00.3 chip ID: 1022:1457 Device-3: N/A type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 5-1.3.4:5 chip ID: 21b4:0083 serial: <filter> Sound Server: ALSA v: k5.4.0-11.2-liquorix-amd64	2020-06-12 19:27:04 -07:00
Harald Hope	46ae081ec6	Big change, cleanup, small bug fixes. Hot, grab it now!! ... The new -y 1 feature exposed several small and larger glitches with how sets of data were constructed in inxi output. See Changes: for list of changes made to improve or fix these glitches. These errors and minor output inconsistencies became very obvious when I was doing heavy testing of -y 1, so I decided to just fix all of them at the same time, plus it was very hard to make the -y 1 indenter work as expected when the key values were not being treated consistently. Note that this completes the set of all possible -y results: Full -y Options: 1. -y [no integer given] :: set width to a default of 80. this is what you usually want for forum posts, or for online issue reports, because it won't wrap and be hard to read. Help us help your users and others!! Teach them to use for example -Fxzy or -bay for their bug reports. Just add y to whatever collection of arguments you generally ask for in support forums or issue reports. Highly recommended, easy to type, and joins cleanly with other letters. 2. -y -1 :: removes line width limits, this can lead to very long lines in some cases, and removes all auto-wrapping of line widths. 3. -y 1 :: Switch to stacked key: value pairs, with primary data blocks separated by a blank line. Think dmidecode type output, or other command line sys info tools. By request, a forum support guy noted it was hard for newbies to understand the -G values, particularly -Ga when in lines, so this is another way to request data. WARNING: for lots of data, this gets really long!!! But if you are curious how inxi actually constructs its data internally, this sort of shows it. 4. -y 80-xx :: set width to 80 or greater. Note you can also set these in your configurations if you want using the various options supported. ----------------------------------- Bugs: 1. Once again, no real bugs found beyond a few trivial things I can't remember. Fixes: 1. When out of X, dm: showed after Console: and often said dm: N/A particularly on headless servers, which was silly. Now DM: only shows after Console: if a DM: was actually found. If regular Desktop output, either in X, or via --display out of X, no changes. 2. There was a pointless sudo test when sudo values are set initially, they were still running even if --no-sudo was used. Now they don't run in that case. Enhancements: 1. The biggie, now inxi can output in a similar indented way as something like dmidecode if you use the -y 1 option. This feature was originally by request, though the initial request actually just wanted to see it stacked simply, but that was almost impossible to read for any output reasonably long, so I made the indentations very dynamic and deep, they go up to 4 levels in, which is roughly how deep in the inxi sub Categories go. This output format makes it very easy to see how inxi 'thinks' about its data, how it views sets, subsets, subsubsets, and subsubsubsets of data. Note that each data block, as with dmidecode data, is separated by a blank line. You know what this means!!! Yes, that's right!!! You can parse inxi output with awk!!, same way legacy bash+gawk inxi used to parse its data!! Or if your brain just does not like lines of data, you can make it appear in indented single key: value pairs. Here you can see for example that 1 Xorg Display has 1 or more Screens, and each Screen has one or more Monitors. Note that this -Ga data first appeared in inxi 3.1.00. Sample [with bug in OpenGL output!, and showing -Ga newer values as well for dual monitor setup, with one Xorg Screen]: inxi -aGy1 Graphics: Device-1: NVIDIA GT218 [GeForce 210] vendor: Gigabyte driver: nouveau v: kernel bus ID: 09:00.0 chip ID: 10de:0a65 Display: x11 server: X.Org 1.20.8 driver: nouveau unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1 Screen-1: 0 s-res: 2560x1024 s-dpi: 96 s-size: 677x271mm (26.7x10.7") s-diag: 729mm (28.7") Monitor-1: DVI-I-0 res: 1280x1024 hz: 60 dpi: 96 size: 338x270mm (13.3x10.6") diag: 433mm (17") Monitor-2: VGA-0 res: 1280x1024 hz: 60 dpi: 86 size: 376x301mm (14.8x11.9") diag: 482mm (19") OpenGL: renderer: N/A v: N/A direct render: N/A 2. Refactored and cleaned up print_data(), got rid of some early testing code, dumped some unnecessary tests, simplified old tests, and optimized the new indentation logic reasonably well. Hopefully the print_data() will not be quite as much of a black box now as it was. 3. Even more drive vendors and ID matches!!! The list never ends!! An endless series of new vendors and IDs of existing vendors sprout up, then float away. And inxi follows them to the best of its ability. Thanks again to Linux-Lite hardware database, which help make this ever expanding list possible, since their users appear to use every disk known to humankind. Changes: 1. When out of Display, and Console: shows, -S will not show dm: if no display manager is detected, and if it is detected, it shows DM: since it's not part of the Console: set of data. If out of X and --display is used to get Xorg data out of X, it will show Desktop: set of data as normal, at least it will show the stuff it can find. This resolves the issue where dm: appeared to be a member of the set of Console: data, instead of either its own thing, DM:, or a member of the set of Desktop: data. 2. For RAID Devices with sub Array-x: values, Array-x: is capitalized, it used to be array-x: That was silly. 3. In USB, now Device-x: resets inside each Hub: so that the Device-x: are numbered starting at 1 within each Hub:. This makes the counter behavior act the same as it does in for example RAM Array-x: / Device-y:, where each Array-x: resets Device-y: count to 1. This changes the old default of having Device-x: not reset, to let you see the total number of devices plugged in or attached no matter which hub they were plugged into, but the output actually gets sort of confusing in single key: value pair mode per line. 4. The key: value syntax for weather was changed completely, now it works like the rest of the features, with Report:... [Forecast:...] Locale:... and Source:. Locale makes the source of the times and other date related features, and the location if shown or available, much more obvious. Before it was never clear if Current Time referred to your local or the remote time, now it's clearly from the Locale: you specified with -W, or the default -w local info. Also made Report 1 line if unwrapped, Forecast 1 line if not wrapped, and Locale: 1 line if not wrapped, which makes the output easier to read. NOTE: automated weather queries are NOT allowed, if you do it, you will be banned!! inxi is NOT a desktop weather app!! Don't confuse it with one!! Weather is just a small service to users who might for example want to check the weather on a remote system, or something like that, and is not intended to be used on a routine basis. 5. Cleaned up and re-ordered the --version output. It had some pretty old contexts in the language, which were removed or cleaned up and brought up to date. If you're wondering, I roughly use rsync and nano --version as guides for what to show or not show there.	2020-06-12 00:47:10 -07:00
Harald Hope	e51ada6bfe	forgot a help item	2020-06-01 11:20:33 -07:00
Harald Hope	ea2c06f1db	fixed copyright year	2020-05-31 14:43:50 -07:00
Harald Hope	7ca58b94d2	New inxi, man. New information types, fixes, man updates. ... Bugs: No bugs of any importance fixed or found!! Fixes: 1. Tiny fix, didn't use partition/slice assignment in help menu. BSD interest only since default partition is standard for Linux. Enhancements: 1. Disc Vendors: added a large number of possible disk vendors, without having actual detection data available for all of them, using a different source. Also added, as usual, more disc vendor IDs from linux-lite hardware database, always ready with more vendors! 2. Added groovy gorilla ID for ubuntu 3. Very nice usability change, mostly for support people, now if -y without an integer is supplied, it will assign default column width of 80, which is what you usually want for forums or issue reports, otherwise the output can wrap outside the post or issue report, which is hard to read. Hopefully support people will catch onto this one. 4. This closes issue #217 - Adds dmidecode based extra data: -xxx - shows CPU voltage and external clock speeds -a - shows CPU socket type and base/boost: speed items. These are --admin options because neither is particularly reliable, sometimes they are right, sometimes they aren't, as usual with dmi data. As far as tests show, base speed, what dmidecode misleadingly calls 'Current Speed', which it isn't, is the actual normal non throttled speed of the CPU / motherboard setup. boost is what dmidecode calls 'Max Speed', which it also isn't, though sometimes it is, as with AMD cpus with boost, and no overclocking. With overclocking, sometimes base will be higher, sometimes the actual real current cpu speeds will be higher than all the max/boost values. Motherboard CPU socket type is likewise randomly correct, incorrect, empty, misleading, depending on the age and type of the system, and the CPU vendor. It appears that in general, AMD CPUs will be more or less right if they have this data, and Intel CPUs will sometimes be right, sometimes not, or empty. For > 1 CPU systems, the data is much less reliable.	2020-05-31 14:41:20 -07:00
Harald Hope	383aa21b0d	forgot to consistently use partition/slice for help.	2020-04-22 22:00:47 -07:00
Harald Hope	05063841f3	help menu typo	2020-04-22 21:06:13 -07:00
Harald Hope	2329d54318	small man fix, had wrong copyright date	2020-04-22 21:00:43 -07:00
Harald Hope	c06a034c98	man page fixes, lintian stuff.	2020-04-22 20:04:46 -07:00
Harald Hope	70d13aca4e	New inxi, new man. Huge update, new line types, huge graphics upgrade, new ... switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!! Note that since this features a new primary line item (-j / --swap Swap:), the version number has been bumped to 3.1.0, making this a major version upgrade, the first since the new Perl inxi rewrite was launched, though of course 3.0.0 contained many new line items as well, but this is the first actually new line item since then. Bugs: 1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME directory, the partitions would buggily duplicate in the output. 2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver because it was using the wrong Xorg log, it was only searcing in the original /var/log/Xorg.0.log file, not the newer alternative path locations. Fixes: 1. Both an enhancement and a fix, users reported Xorg log file location changes. Fix is that now inxi uses wildcard searches of all readable locations that can contain the log files, then collects a list of them, and uses the last modified one. This ensures that the best possible guess is made about which actual log file is current, which should lead to significantly more reliable Xorg driver reports overall. Note that this fix works for user level and root level, it will always use the most recent readable file no matter what. For root, that should translate to the most recent on an absolute level Xorg log file. This issue was caused by gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and also, the location is often but not always now: ~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why root has to search for all user Xorg log files to find the most recent one. There were many red-herrings in this issue report, so it took some research to dig through those to the real data sources. 2. Now that the compositor detection is out of early testing mode, enabled always on compositor detection for Wayland systems. Since the compositor is the Wayland display server, it makes sense to always show it if Wayland. Note that there is still no known way to actually reliably get Wayland data beyond simple environmental variables that let inxi detect Wayland is running the desktop. Lack of reliable logs or debugging tools across Wayland compositors makes this entire process about 10-50x more difficult than it should have been. 3. In keeping with 2., also moved compositor: item to be right after server: item. 4. Debian bug: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi requested that HTTP::Tiny be set to default always check SSL certificates. Now inxi does that, and --no-ssl flag disables this, which makes the Perl http downloader now work roughly the same as wget, curl, etc. 5. Man page fixes, added pointer placeholders for out of alphabetical order options, so you can find anything by looking down the alpha sorted lists, like: --swap - See -j. Since inxi is running out of single letters that match new features, it's easier to point man readers to the right item without them having to already know it to find it. Also added --dbg [2-xx] pointer to github inxi-perl/docs/inxi-values.txt so people interested can learn how to trip the various per feature screen debuggers. Enhancements: 1. updated ubuntu ids, added 'focal LTS'. 2. USB Graphic devices added. This will add support for USB graphics adapters, an uncommon but existing category, often used in SOC boards, for example, but also on desktops, and things like USB webcams. Leaving these off was really just an oversight, the programming internally had the data, it just wasn't using it. 3. Support added for TV card type multimedia devices in Graphics. That was actually a long term oversight, I'd simply missed that in the device ID documentation, one of the multimedia device subtypes is Video device. 4. Huge, massive, internal upgrade to allow for -Ga output, which gives a technically accurate Xorg > Display > Screen > Monitor breakdown. Note that Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr, but if xrandr is missing, the Screen information shows. Technically for -G, -Gxx, end users see very little difference except the per Screen / per Monitor resolutions are listed with a 1: type counter per item. Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs out of the pieces of hardware that make up the Screen space. In many cases, 1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty different. New output items: Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]] Screen-x: [Screen number]; s-res: [Xorg Screen resolution]; s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size; s-diag: [diagonal of Xorg Screen size] Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions]; hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated from actual monitor resolution/size; size: [actual monitor size in mm (inch); diag: [actual diagonal size in mm (inch). 4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution section for -G. 5. Big improvement in error messages and logging for Xorg driver detections, this logic is much more robust now, but after the main driver fix, also much less likely to ever be seen. 6. Almost not visible to users, but major internal graphics refactor allows now for more modular treatment, and eventual Wayland data sourcing. Currently most Wayland data sourcing is in stub form, or only logically possible, but as it grows possible (if ever, since Wayland protocal appears to have totally neglected enforcing single location logging, and single tool debugging for the entire Wayland protocol of compositors, a massive oversight in my view). The -Ga refactors internally made this much more possible, and I integrated switches and tests, and fallbacks, and stubs in some locations, so it was clear where current Xorg specific logic is, and where future Wayland logic will fit in, sort of anyway. 7. Debugger tools added for new features, or most of them. 8. New primary line item: --swap / -j. This moves all swap data to a dedicated Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap is used, all swap types, not only physical partition swaps, show. This should make some users happy. 9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later Intel cpu family ids in terms of cpu arch name tool. 10. By request, added ability filter out all UUID or Partition Label strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and --filter-uuid. Mostly useful in fringe cases, for example, replacing label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>, or in cases you want to show full -v8 output without showing UUID or Labels, whatever. 11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables dig in cases where dig is installed but failed due to maybe network firewall rules or something, and WAN IP detection fails. Normally you always want to use dig, it's faster, more reliable, and safer, than all the other regular downloader based methods, but we have seen server setups where for some reason those types of dig requests were blocked, thus disabling WAN IP detection. 12. Added in WAN IP failure case, if dig was used, suggestion to try again with --no-dig, since most users are unlikely to learn about this issue, or the solution to it. 13. Added single letter shortcut -J for --usb, maybe this will help people discover usb component of inxi, now you can request for instance: inxi -FJaz 14. Added xonsh to supported shells, that had tripped a perl undefined value for start client bug since xonsh uses single word for version, xonsh/234 so the default value, 2nd word, was undefined. 15. More SSD and USB drive vendors from the endless fountain over at Linux Hardware Database (linuxliteos.com). Changes: 1. Small change in how screen resolutions are output in -G non -a mode, now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key. This helps make it more readable. Note that in non -a mode, the increments are just based on Screen, then Monitor, Monitor, Screen, and so on, counts. Most users will only have one Screen systems, but more advanced setups may use the Xorg > 1 Screen, each screen able to run > 1 monitors. The counts in say, a 2 Screen system, with 3 monitors, would be: 1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2] 3: res3 [from screen 1, monitor 1. If xrandr is not installed, it would show: 1: res1 [from screen 0] 2: res2 [from screen 1]	2020-04-22 19:35:53 -07:00
Harald Hope	b6f453ec39	forgot changelog headline!! made it hard to see the new inxi in commits.	2020-03-14 23:31:16 -07:00
Harald Hope	d65b40e60a	Bugs: ... 1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic. Fixes: 1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error) 2. Preventitive, was not using '-' quite correctly in all regex ranges. 3. Had wrong desktop string listed in Unity 4. Reordered Family/Drive model in usb drive reports, it's to make it more obvious what is what. 5. Adjusted indexing of splits to get better results in corner cases. 6. Fixed some numbering issues. 7. Added trimming n1 from nvme0 type names for nvme, this corrects some issues users were having. 8. Fixed a division by 0 error in smartctl data grabber. 9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0. 10. Another Perl fix, int() only wants to get numeric values sent to it, I'd assumed a different behavior, non numerics get converted to 0, but that's not how Perl sees things. Things like this, by the way, are why Perl is so absurdly fast. Enhancements: 1. More disk vendors. The list will never be complete!! We have found eternal churn!! Thanks to linux lite hardware database as always. 2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced drive information (with -a). See man and help for details. Will show failing drives, etc. Lots of info can be available, but sometimes data is not in smartctl db, so inxi can't find it, that's not an inxi bug, it's just how it is. 3. Made hours on more human readable, into days/hours, for -a smartctl disk report. 4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out. Note that advanced debugger outputs can change or vary depending on what is being worked on so don't in general rely on these always being around. But they do tend to say stuck in place once I add them. 5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it, if not, you'll never know it's there. 6. By request from some forum issue thread: made --host only be shown onif not --filter or not --host. This makes -z remove hostname, but retains ability to do absolute overrides. Hostname should have always been filtered out like that, it was an oversight. I think that was Manjaro who asked that, but I forget. Note that this change, as usual, will not alter expected behaviors if users have config item for hostname set. 7. Added support for picom compositor, thanks user codebling for that, I think that's compiz fork, the real branch that is that is being developed.	2020-03-14 23:15:16 -07:00
Harald Hope	c9c56887d8	last cleanups	2019-11-19 21:04:08 -08:00
Harald Hope	1a4ae58c2a	added a bit more to commit message.	2019-11-19 20:47:57 -08:00
Harald Hope	f2cfb7edfb	New version, man page, exciting changes!! ... Bugs: 1. issue #200 - forgot to add all variants for -p, now works with --partition-full and --partitions-full 2. issue #199 - another one, forgot to add --disk to -D for long version. Thanks adrian15 for both of these, he was testing something and discovered these were missing. 3. Issue #187 an issue with RAID syntax not being handled in a certain case, thanks EnochTheWise for following through on this one. This turned out to be a bad copy paste, a test pattern did not match the match pattern. Fixes: 1. Fixed some docs typos. 2. Issue #188 fixed protections and filters for some glxinfo output handlers. 3. Issue #195, for Elbrus bit detection. 4. Added filter to cpu data, was not skipping if arm, so Model string was treated numerically. Enhancements: 1. Added rescatux to Debian system base detections. This closes issue #202, again from adrian15, thanks. 2. For cpu architecture, updated for latest AMD ryzen and other families, like Zen 3, which is just coming out re available data. Also latest Intel, which are trickier to ID right now, but I think I got the latest ones right, That's things like coffee lake, amber lake, comet lake, etc. 3. Huge one, full (hopefully out of the box) Russian Elbrus CPU support. Thanks to the alt-linux and the others who helped provide data and feedback to get support. Note that this was also part of correcting 64 bit detection for e2k type, which is how Elbrus IDs internally. See issue #197 which I've left open for the time being for more information on this CPU and how it's now handled by inxi. Note all available data should now work for Elbrus, including physical cpu/core counts etc. Elbrus do not show flag information, nor do they use min/max speed, so that data isn't available, but everything else seems to work well. 4. Eternal disk vendors. Thanks linux lite hardware database, you continue to help make the disk vendor feature work by supplying every known vendor ever seen. 5. To close debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942194 Note that the fix is simply to give the user the option to disable this behavior with the new --no-sudo and NO_SUDO configuration file options. This issue should never have been filed as a bug since even the poster admitted it was a wishlist item, but because of how debian bug tracker works, it's hard to get rid of invalid bugs. Note that this is the internal use of sudo for hddtemp and file, not starting inxi with sudo, so using this option or configuration item just removes sudo from the command. Note that because the user did not do as requested, and never actually filed a github wishlist issue, and since his request was vague and basically pointless, the fix is just to let you switch off sudo, that's all.	2019-11-19 20:42:21 -08:00
Harald Hope	c75d037aba	changelog cleanup, issue was resolved, that's good.	2019-09-10 19:08:15 -07:00
Harald Hope	66864486b5	typo fix	2019-08-14 11:22:15 -07:00
Harald Hope	92df6e1ae0	New version, many small fixes. And a hall of shame, LOL. ... Bugs: 1. Issue #188 exposed a situation in glxinfo where the required opengl fields are present but contain null data. This happens when a system does not have the required opengl drivers, which was the case here. inxi failed to handle that. Thanks LinuxMonger for posting the required data to figure this corner case out. 2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals) where it was supposed to use regex pattern match. Oops. Would have led to disk vendor id failures in several cases. Fixes: 1. help, man updates for RAM/Memory data, more clarifications. 2. Refactored RepoData class/package, to make it easier to handle repo string data, and make it all overall cleaner internally, and enable future extensions to certain features in inxi that may or may not one day become active. 3. Added to some regex compares \Q$VAR\E to disable regex characters in strings. I should have used that a long time ago, oh well, better late than never! 4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual pixel dimensions, shame on whoever allowed that output!!! shame! Had to add a workaround to make sure numeric values are present, if not, then use the fallback, which means, 2x more data parsing to get data that should not require that, but in this example, it did (an Arch derivative, but it could be xdpyinfo itself, don't know)> Enhancements: 1. More fixes on issue #185. Thanks tubecleaner for finding and provding required data to really solve a set of RAM issues that apply particularly in production systems. This issue report led to 2 new options: --memory-short, which only shows a basic RAM report. Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%) Report: arrays: 1 slots: 4 modules: 2 type: DDR4 And a 2nd, --memory-modules, only shows the occupied slots. This can be useful in situations where it's a server or vm with a lot of slots, most empty: Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%) Array-1: capacity: 256 GiB slots: 4 EC: None Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s Note that both of these options trigger -m, so -m itself is not required. 2. More disk vendors!! The list never ends! Thanks linux-lite hardware database and users for supplying, and buying/obtaining, apparently every disk known to mankind. 3. Added fallback XFCE detection, in cases were the system does not have xprop installed, it's still possible to do a full detection of xfce, including toolkit, so now inxi does that, one less dependency to detect one more desktop. 4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this in the wild, but I did see it as the kernel reported driver from lspci, so it may exist. Unfixed: 1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there is a RAID ZFS issue that will not get fixed until the required debugger data is supplied. Please do not waste all our time filing an issue if you have no intention of actually following through so we can get it fixed. Note that a key way we get issues here is from Perl errors on the screen, which are a frequent cause of someone realizing something is wrong. This is why I'm not going to do a hack fix for the RAID ZFS issue, then the error messages will go away, and it will likely never get handled. For examples of good, useful, productive issue reports, and how to do them right: #188 and #185, both of which led to good improvements in how inxi handles corner cases in those areas.	2019-08-14 11:14:13 -07:00
Harald Hope	0757b3a816	New version. Bug fixes, updates. ... Bugs: 1. Issue #185 exposed a small long standing bug in ram max module size logic. Was not retaining the value each loop iteration, which could lead to way off max module size guesses. Note that this could lead to a VERY wrong max module size report. 2. Issue #185 also exposed a rarely seen undefined value for ram reports, was not tested for undefined, now is. Fixes: 1. cleanup of comments in start client debugger that made it unclear. 2. Got rid of all the legacy development modules that were in inxi-perl/modules. These were totally out of date and pointless to retain. Enhancements: 1. Added eoan ubuntu 19-10 release name 2. Added zen cpu model ID. 3. Disk vendors and new vendor IDs added. Thanks linuxlite hardware database. 4. Made a backend tool to check for new unhandled disks, this makes updating disk/vendor IDs a lot easier. 5. Updated inxi-perl/docs with new links etc.	2019-07-15 19:56:44 -07:00
Harald Hope	24667eb49e	fixed change.log typos	2019-05-02 11:09:22 -07:00
Harald Hope	2524888ef1	small edits	2019-04-30 19:10:22 -07:00
Harald Hope	9a3c442c9f	man edits	2019-04-30 19:06:19 -07:00
Harald Hope	f5ea688e8d	more man edits	2019-04-30 18:29:35 -07:00
Harald Hope	63d13ff858	small man edit	2019-04-30 18:26:25 -07:00
Harald Hope	b3c72ae289	New version, new man, new feature!! Bug fixes! ... Bugs: 1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it was using unfiltered strings as regex pattern, and of course, a string flipped an error. Fix was to add the regex cleaner to the string before it's used in test. 2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with data or output so it couldn't be fixed. This was related to a syntax change in usbdevs -v output in FreeBSD. Such changes are too common, but it might also simply be a variant I have not seen or handled, but so far no data, so can't fix. Don't blame me if you get this bug, but do post requested debugger data if you want it fixed! Fixes: 1. Updated man for weather, explained more clearly how to use country codes for weather output. More clarifying in general about weather location, and weather restrictions. Enhancements: 1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from liquorix for clarifying why that was a good idea. Note the initial issue came up in a Debian issue report, not here. People!! please post issues here, and don't bug maintainers with feature requests! Maintainers aren't in a position to add a feature, so you should go straight to the source. 1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all the flags, and also covers the short form flags and explains why they are used. 2. To resolve another issue, I made a new documentation file: inxi-perl/docs/inxi-custom-recommends.txt This is instructions for maintainers of distros who do not use rpm/apt/pacman but still want the --recommends feature to output their package pool package names for missing packages. I decided to not allow more than the default 3 package managers because no matter what people say, if I allow in more, the maintainer will vanish or lose interest, and I'll be stuck having to maintain their package lists forever. Also, it's silly to even include that package list for any distro that does not use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file show what to change, and how, and has an example to make it clear. Odds of this actually being used? Not high, lol, but that's fine, if people want it done, they can do it, if not, nothing bad happens, it just won't show any suggested install package, no big deal. 3. Using the new disk vendor method, added even more disk vendors. Thanks linux litet hardware database!! 4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/ Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters, from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me where to look, I'll add it for those too, but wasn't anywhere I looked. Do the BSDs even use that method? Don't know, but the logic is there, waiting to be used if someone shows me how to get it cleanly. The 'parameters:' item shows in the main 'System:' -S output, and will just show the entire kernel parameters used to boot. This could be very helpful to distros who often have to determine if for example graphics blacklists are correctly applied for non free drivers, like nomodeset etc, or if the opposite is present. For forum/distro support, they just have to ask for: inxi -ba and they will see t the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used to trigger in this case the graphics and system lines. 5. Updated man/help for 4 as well, now explains what they will see with --admin/ -a options and -S. Good user suggestion, I wish all new features were this easy, heh.	2019-04-30 17:56:10 -07:00
Harald Hope	2c53d6f3d6	changelog edit	2019-03-29 14:37:23 -07:00
Harald Hope	0a3cf24290	added issue to changelog	2019-03-29 14:31:49 -07:00
Harald Hope	2650a51d3b	New version, new man. Weather explanations, disks, bugs!! ... Bugs: 1. For sensors, in some cases, gpu failed to show correctly. This should be corrected. Fixes: 1. Made help/man explanations of weather changes more clear. Particularly in regards to no automated query info. But also for supported location syntaxes. 2. Some corner cases of null weather data return null and tripped a null data error. This is corrected. 3. Added city duplicate filter to weather output, this hopefully will in some cases avoid printing city name twice, depends on weather source. 4. Removed --weather-source option 0, that no longer works so all code was removed. 5. More deb822 fixes, loosened up even more syntax. That's a poorly designed config syntax, hard to work with. Enhancements: 1. Lots of new disk vendors. So many!! Thanks linux-lite hardware database! switched to a new method of getting disk name/vendor data, now it's a lot easier to check for new ones. 2. Added fancybar to desktop info.	2019-03-29 14:11:22 -07:00