New version, tarball, man page. This corrects many 80 column width line wraps, including on:
-o, -p, -l, -u, -P, -S, -G, -N, -A
Now most output should tend to not wrap, though some strings are unpredictable and
will have to be trimmed by adding them to the min size trimmers one by one.
But it's much better than it was.
Note the following changes required to make the wraps more consistent:
-S - the gcc/bits have been made separate, like: bits: 32 gcc: 5.3
-C - the new microarchitecture -x option now is: arch: K7 [for example]
cache wraps to next line with arch. with -f, bmips now shows on same line as
arch/cache
2017-07-30 21:22:14 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.31
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-30
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. This corrects many 80 column width line wraps, including on:
|
|
|
|
|
-o, -p, -l, -u, -P, -S, -G, -N, -A
|
|
|
|
|
|
|
|
|
|
Now most output should tend to not wrap, though some strings are unpredictable and
|
|
|
|
|
will have to be trimmed by adding them to the min size trimmers one by one.
|
|
|
|
|
|
|
|
|
|
But it's much better than it was.
|
|
|
|
|
|
|
|
|
|
Note the following changes required to make the wraps more consistent:
|
|
|
|
|
|
|
|
|
|
-S - the gcc/bits have been made separate, like: bits: 32 gcc: 5.3
|
|
|
|
|
-C - the new microarchitecture -x option now is: arch: K7 [for example]
|
|
|
|
|
cache wraps to next line with arch. with -f, bmips now shows on same line as
|
|
|
|
|
arch/cache
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 30 Jul 2017 14:02:33 -0700
|
|
|
|
|
|
2017-07-30 02:38:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.30
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. More optimizations, I'm not sure these will make a big difference
|
|
|
|
|
but I believe the overall collection has dropped execution time by around 10% or so.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 29 Jul 2017 19:36:55 -0700
|
|
|
|
|
|
2017-07-29 23:41:49 +00:00
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.29
|
|
|
|
|
Patch Version:
|
|
|
|
|
Script Date: 2017-07-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. More optimizations, and fixed a bash 4 syntax regression that
|
|
|
|
|
would have caused failure on older systems. Also added Bash version checker.
|
|
|
|
|
|
|
|
|
|
Most ps aux data is now searched using bash parameter expansion, and several functions
|
|
|
|
|
that were in subshells are now printing to globals instead.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 29 Jul 2017 16:37:01 -0700
|
|
|
|
|
|
2017-07-29 19:38:34 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.28
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes a subtle gawk issue that could in some systems make -G
|
|
|
|
|
hang endlessly.
|
|
|
|
|
|
|
|
|
|
Also started on more optimizing, getting rid of as many subshells as possible.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 29 Jul 2017 12:37:27 -0700
|
|
|
|
|
|
2017-07-29 01:42:17 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.27
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2017-07-29 03:30:21 +00:00
|
|
|
New version, tarball, man page. More cpu arch fixes, and added stepping/release info
|
|
|
|
|
as well so you can see which revision of the cpu microarchitecture your cpu has.
|
2017-07-29 01:42:17 +00:00
|
|
|
|
2017-07-29 03:30:21 +00:00
|
|
|
Also fixed a few random vm id issues, I found cases where systemd believes it's bochs
|
|
|
|
|
but it is actually kvm, so now the systemd data is not fully trusted, but is confirmed.
|
2017-07-29 01:42:17 +00:00
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 28 Jul 2017 18:39:19 -0700
|
|
|
|
|
|
2017-07-28 07:18:42 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.26
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. First attempt at adding cpu microarchitecture support.
|
|
|
|
|
Will need some updates to bring the family/model ids to fully current, but should show data for most
|
|
|
|
|
cpus. Next release will hopefully include latest model/family ids and microarchitecture names.
|
|
|
|
|
|
|
|
|
|
Note that while /proc/cpuinfo has the family/model id in decimal, the values are actually generally
|
|
|
|
|
found as hexadecimal, so inxi translates that interally so we can store the data the way it is presented.
|
|
|
|
|
|
|
|
|
|
See issue #116 for ongoing additions to this feature.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 28 Jul 2017 00:12:56 -0700
|
|
|
|
|
|
2017-07-25 04:13:03 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.25
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This fixes a bug where if there is a remote filesystem mounted, the path
|
|
|
|
|
would crash gawk when searching for unumounted file systems, eg:
|
|
|
|
|
|
|
|
|
|
12.34.2.10:/remote/file/system
|
|
|
|
|
|
|
|
|
|
Fix is to escape '/'.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 24 Jul 2017 21:10:54 -0700
|
|
|
|
|
|
New version, tarball. This corrects a case I'm seeing where wayland/mir are running desktop
but Xorg has not started, which means inxi can't get the video driver from Xorg.0.log as with X.
Added in extra data collection from lspci -v to include the driver for graphics card. this is
only used, for now, if the initial Xorg based driver test works.
Note that this may also work for systems that have not yet started X out of X, in console, I'm
not sure about that, but the graphics driver reporting should be improved.
Note that I'm not yet linking the driver to the specific card/device, it's just going to show
in a comma separated list, I couldn't find multi card systems where the card types are different,
like amd gpu with nvidia card, for example.
But this should correct an issue, at least to start, with expanding wayland support for systems
that don't use or have not started the desktop with Xorg/X11 etc.
2017-07-23 21:40:53 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.24
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-07-23
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This corrects a case I'm seeing where wayland/mir are running desktop
|
|
|
|
|
but Xorg has not started, which means inxi can't get the video driver from Xorg.0.log as with X.
|
|
|
|
|
|
|
|
|
|
Added in extra data collection from lspci -v to include the driver for graphics card. this is
|
|
|
|
|
only used, for now, if the initial Xorg based driver test works.
|
|
|
|
|
|
|
|
|
|
Note that this may also work for systems that have not yet started X out of X, in console, I'm
|
|
|
|
|
not sure about that, but the graphics driver reporting should be improved.
|
|
|
|
|
|
|
|
|
|
Note that I'm not yet linking the driver to the specific card/device, it's just going to show
|
|
|
|
|
in a comma separated list, I couldn't find multi card systems where the card types are different,
|
|
|
|
|
like amd gpu with nvidia card, for example.
|
|
|
|
|
|
|
|
|
|
But this should correct an issue, at least to start, with expanding wayland support for systems
|
|
|
|
|
that don't use or have not started the desktop with Xorg/X11 etc.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 23 Jul 2017 14:35:56 -0700
|
|
|
|
|
|
2017-06-29 19:56:23 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.23
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. Added support for Alpine Linux apk package manager for
|
|
|
|
|
the -r option. Fixed typos and glitches in man page as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 29 Jun 2017 12:54:21 -0700
|
|
|
|
|
|
New version, tarball. Bug fix for GLX/OpenGL output. There was an unhandled case with
core profile data being null, which in turn triggered a bash oddity, where if the IFS is
\n for an array, and if the value of one element is '', then bash ignores that and does
not simply set an empty array key as you'd expect. The correction was to change the IFS
to ^, which worked fine for empty array values.
However, since this bug will impact anyone with empty opengl core profile data, I recommend
updating inxi.
Also, added support for two smaller wm, Sawfish and Afterstep.
This is a good source for lists of wm: http://www.xwinman.org/ http://www.xwinman.org/others.php
However, that does not show how to ID it, so i have to do it on a case by case, but I'll
add an issue for showing how to get your wm of choice if it's missing to inxi.
2017-06-25 01:16:29 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.22
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Bug fix for GLX/OpenGL output. There was an unhandled case with
|
|
|
|
|
core profile data being null, which in turn triggered a bash oddity, where if the IFS is
|
|
|
|
|
\n for an array, and if the value of one element is '', then bash ignores that and does
|
|
|
|
|
not simply set an empty array key as you'd expect. The correction was to change the IFS
|
|
|
|
|
to ^, which worked fine for empty array values.
|
|
|
|
|
|
|
|
|
|
However, since this bug will impact anyone with empty opengl core profile data, I recommend
|
|
|
|
|
updating inxi.
|
|
|
|
|
|
|
|
|
|
Also, added support for two smaller wm, Sawfish and Afterstep.
|
|
|
|
|
|
|
|
|
|
This is a good source for lists of wm: http://www.xwinman.org/ http://www.xwinman.org/others.php
|
|
|
|
|
|
|
|
|
|
However, that does not show how to ID it, so i have to do it on a case by case, but I'll
|
|
|
|
|
add an issue for showing how to get your wm of choice if it's missing to inxi.
|
|
|
|
|
|
2017-06-25 01:23:17 +00:00
|
|
|
Also, changed the slightly inaccurate:
|
|
|
|
|
|
|
|
|
|
GLX Renderer: .....GLX Version: ....
|
|
|
|
|
|
|
|
|
|
to
|
|
|
|
|
|
|
|
|
|
OpenGL: renderer: ...... version: .....
|
|
|
|
|
|
New version, tarball. Bug fix for GLX/OpenGL output. There was an unhandled case with
core profile data being null, which in turn triggered a bash oddity, where if the IFS is
\n for an array, and if the value of one element is '', then bash ignores that and does
not simply set an empty array key as you'd expect. The correction was to change the IFS
to ^, which worked fine for empty array values.
However, since this bug will impact anyone with empty opengl core profile data, I recommend
updating inxi.
Also, added support for two smaller wm, Sawfish and Afterstep.
This is a good source for lists of wm: http://www.xwinman.org/ http://www.xwinman.org/others.php
However, that does not show how to ID it, so i have to do it on a case by case, but I'll
add an issue for showing how to get your wm of choice if it's missing to inxi.
2017-06-25 01:16:29 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 24 Jun 2017 18:00:21 -0700
|
|
|
|
|
|
2017-06-13 18:01:24 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.21
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Fix for root graphics/desktop data when not available as root.
|
|
|
|
|
|
|
|
|
|
Was showing in -S line N/A instead of the fallback Console: tty 1 that would match the
|
|
|
|
|
-G no data for root when unavailable for root.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 13 Jun 2017 10:59:41 -0700
|
|
|
|
|
|
2017-06-13 01:37:12 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.20
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-12
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. Added floppy disk support, basic, for -d. Fixed a
|
|
|
|
|
long-standing issue where /dev/ram.. data shows in unmounted disks output. This is
|
|
|
|
|
now properly filtered out.
|
|
|
|
|
|
|
|
|
|
Note that the floppy disk output has no information beyond it's /dev id, eg: /dev/fd0
|
|
|
|
|
|
|
|
|
|
I could find no meaningful data in /sys related to the floppy disk, not the model, etc, so
|
|
|
|
|
I'm just showing presence of disk.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 12 Jun 2017 18:31:48 -0700
|
|
|
|
|
|
2017-06-09 18:55:19 +00:00
|
|
|
=====================================================================================
|
2017-06-11 04:34:15 +00:00
|
|
|
Version: 2.3.19
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-10
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This version has some bug/edit fixes and a new distro id, mx-version.
|
|
|
|
|
|
|
|
|
|
Simple.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 10 Jun 2017 21:32:55 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2017-06-09 18:55:19 +00:00
|
|
|
Version: 2.3.18
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-09
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
|
|
|
|
|
New version, tarball, man page. New option -! 34 - skip SSL certificate check on
|
|
|
|
|
wget/fetch/curl. This allows systems with for example out of date certificate stores
|
|
|
|
|
to still download without error. Also a legacy system fix where tty size failed to show.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 09 Jun 2017 11:52:26 -0700
|
|
|
|
|
|
2017-06-09 17:07:40 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.17
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-09
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. Bug fix for issue #105, had core and compat versions reversed.
|
|
|
|
|
|
|
|
|
|
Also cleaned up man page, slightly changed output for compat version to: (compat-v: 3.0)
|
|
|
|
|
|
|
|
|
|
gfx variable name fixes to make more obvious the logic as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 09 Jun 2017 10:00:48 -0700
|
|
|
|
|
|
2017-06-09 04:04:08 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.16
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Tiny change, new version, tarball. Tumbleweed distro id fix.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 08 Jun 2017 21:02:53 -0700
|
|
|
|
|
|
2017-06-09 02:29:55 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.15
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. New option -! 40 which lets you get gfx information out of X.
|
|
|
|
|
|
|
|
|
|
Default will get data from display :0, but if you append :[display-number] to -! 40, it will
|
|
|
|
|
use that display instead, for example: inxi -! 40:1 would get information from display 1. Note
|
|
|
|
|
that most multi-monitor setups use :0 for both monitors, depending on how it's setup.
|
|
|
|
|
|
|
|
|
|
This will also let users see any desktop information based on xrop -root output, but it will
|
|
|
|
|
depend how it works based on how environmental variables have been set. gnome and kde, which use XDG for
|
|
|
|
|
primary detection would not work, for example.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 08 Jun 2017 19:25:21 -0700
|
|
|
|
|
|
2017-06-09 00:49:34 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This corrects an issue I noticed a while ago, glxinfo and xpdyinfo
|
|
|
|
|
used to not work as root in X, but they do now. So I've removed the root tests for graphics
|
|
|
|
|
output, and now only rely on the returned data to determine the output when in X. Out of X
|
|
|
|
|
behavior remains the same.
|
|
|
|
|
|
|
|
|
|
Note that at some point I'll have to see if wayland systems have usable reporting tools to get
|
|
|
|
|
screen resolution, opengl info, and so on, but that will have to come one step at a time.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 08 Jun 2017 17:46:30 -0700
|
|
|
|
|
|
New version, tarball, man page. Shows as default OpenGL core profile version number.
-xx option will show OpenGL compatibility version number as well, though that's largely useless
information for most users, thus the -xx. Note that this reverses the default, which previously
showed OpenGL version, which is actually the compatibility version.
This should resolve #105 pull request, though it does it differently, by switching the default
output to what is more relevant, and offering the compatibility version as an optional output item.
Note that much of the glx information will probably change to more neutral terms once wayland support
starts growing, and systems without xwayland etc libraries appear.
Further note that non free drivers showed the OpenGL core profile version numbers all along, so really
this simply corrects misleading output for free drivers.
2017-06-08 22:59:37 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.13
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. Shows as default OpenGL core profile version number.
|
|
|
|
|
-xx option will show OpenGL compatibility version number as well, though that's largely useless
|
|
|
|
|
information for most users, thus the -xx. Note that this reverses the default, which previously
|
|
|
|
|
showed OpenGL version, which is actually the compatibility version.
|
|
|
|
|
|
|
|
|
|
This should resolve #105 pull request, though it does it differently, by switching the default
|
|
|
|
|
output to what is more relevant, and offering the compatibility version as an optional output item.
|
|
|
|
|
|
|
|
|
|
Note that much of the glx information will probably change to more neutral terms once wayland support
|
|
|
|
|
starts growing, and systems without xwayland etc libraries appear.
|
|
|
|
|
|
|
|
|
|
Further note that non free drivers showed the OpenGL core profile version numbers all along, so really
|
|
|
|
|
this simply corrects misleading output for free drivers.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 08 Jun 2017 15:54:04 -0700
|
|
|
|
|
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-06-06
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
|
|
|
|
|
and compositor support.
|
|
|
|
|
|
|
|
|
|
This finally implements a first try at mir/wayland detection, along with basic handling of actual
|
|
|
|
|
display server type output.
|
|
|
|
|
|
|
|
|
|
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
|
|
|
|
|
|
|
|
|
|
Note that since almost all current Wayland systems will have X.org also installed, for the time
|
|
|
|
|
being, the data in the parentheses will be from X.org regardless of what display server is detected running
|
|
|
|
|
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
|
|
|
|
|
|
|
|
|
|
No other data is available to me yet until I get way more debugger data so I can see what information the various
|
|
|
|
|
implementations of wayland without x tools actually makes available, my guess is it won't be much.
|
|
|
|
|
|
|
|
|
|
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
|
|
|
|
|
|
|
|
|
|
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
|
|
|
|
|
start handling the wide range of wayland compositors being created.
|
|
|
|
|
|
|
|
|
|
This feature will probably take several versions to get stable.
|
|
|
|
|
|
|
|
|
|
Also added new debugger data collector data for wayland information, but the pickings are slim, to
|
|
|
|
|
put it mildly.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 06 Jun 2017 18:43:31 -0700
|
|
|
|
|
|
New version, new tarball, new man page. This corrects several oversights of the 2.3.10 IPv6 update.
Now there is an -x option for -i that will show the additioanl IPv6 address data for scope global,
temporary, and site. Also a fallback for unhandled scope: unknown. If the tool 'ip' is used, it will
filter out the deprecated temp site/global addresses, ifconfig tool does not appear to offer this
option.
Also changed is that now ipv6 address always shows, it's not an -x option. Probably about time to
start rolling out ip v6 data to users now that ip v6 is starting, slowly, to be used more.
Another small change, the link address for ipv6 is changed from ip-v6: to ip-v6-link so that it's
more clear which IP v6 address it is.
The last commit had a significant logic error in it that did not distinguish between the link address,
which is what should have only shown, and the remaining possible addresses.
I've tried to get a basic bsd support, but it's difficult to know the variants of ifconfig output syntax
2017-05-31 22:33:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.11
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-05-31
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. This corrects several oversights of the 2.3.10 IPv6 update.
|
|
|
|
|
|
|
|
|
|
Now there is an -x option for -i that will show the additioanl IPv6 address data for scope global,
|
|
|
|
|
temporary, and site. Also a fallback for unhandled scope: unknown. If the tool 'ip' is used, it will
|
|
|
|
|
filter out the deprecated temp site/global addresses, ifconfig tool does not appear to offer this
|
|
|
|
|
option.
|
|
|
|
|
|
|
|
|
|
Also changed is that now ipv6 address always shows, it's not an -x option. Probably about time to
|
|
|
|
|
start rolling out ip v6 data to users now that ip v6 is starting, slowly, to be used more.
|
|
|
|
|
|
|
|
|
|
Another small change, the link address for ipv6 is changed from ip-v6: to ip-v6-link so that it's
|
|
|
|
|
more clear which IP v6 address it is.
|
|
|
|
|
|
|
|
|
|
The last commit had a significant logic error in it that did not distinguish between the link address,
|
|
|
|
|
which is what should have only shown, and the remaining possible addresses.
|
|
|
|
|
|
|
|
|
|
I've tried to get a basic bsd support, but it's difficult to know the variants of ifconfig output syntax
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 31 May 2017 14:22:21 -0700
|
|
|
|
|
|
2017-05-31 17:43:22 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.10
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-05-31
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixes issue #78 and issue #106
|
|
|
|
|
|
|
|
|
|
Shows multiple ipv6 addresses, filters out ipv6 temp addresses and ipv6 local addresses.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 31 May 2017 10:39:00 -0700
|
|
|
|
|
|
2017-05-29 19:44:58 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.9
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-05-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Tiny fix, due to a data bug, changing ft to m in weather altitude.
|
|
|
|
|
|
|
|
|
|
Note that this bug is not universal, but I believe this will make inxi more right than wrong
|
|
|
|
|
as a general rule. Further note that altitude is NOT actually the altitude of the city/location
|
|
|
|
|
requested, in most cases, but rather the altitude of the weather station data assigned to that
|
|
|
|
|
location request.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 29 May 2017 12:40:12 -0700
|
|
|
|
|
|
2017-01-14 20:48:56 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.8
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2017-01-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Tiny change, added sisimedia video driver to support list.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 14 Jan 2017 12:47:31 -0800
|
|
|
|
|
|
2016-12-24 23:02:59 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.7
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-12-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes an issue where sloppy regex was removing the BIOS
|
|
|
|
|
from BIOSTAR. Also fixed a few other sloppy gsub, and fixed a few gensub errors as well.
|
|
|
|
|
|
|
|
|
|
Since BIOSTAR is a fairly common mobo, I'm surprised I haven't gotten this bug report
|
|
|
|
|
before.
|
|
|
|
|
|
|
|
|
|
This closes issue #102.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 24 Dec 2016 14:53:31 -0800
|
|
|
|
|
|
2016-12-21 03:57:41 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.6
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-12-20
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No new version. New tarball, man. Small text changes and cleanup and updates in man page,
|
|
|
|
|
but no actual meaningful changes. Feel free to ignore this one if you just did 2.3.6.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 20 Dec 2016 19:53:54 -0800
|
|
|
|
|
|
New version, new tarball. This is a significant change, but inxi should handle it smoothly.
While default configs remain in /etc/inxi.conf, the user overrides now use the following order of tests:
1. XDG_CONFIG_HOME / XDG_DATA_HOME for the config and log/debugger data respectively.
2. Since those will often be blank, it then uses a second priority check:
$HOME/.config $HOME/.local/share to place the inxi data directory, which was previously here:
$HOME/.inxi
3. If neither of these cases are present, inxi will default to its legacy user data: $HOME/.inxi as before
In order to make this switch transparent to users, inxi will move the files from .inxi to the respective
.config/ .local/share/inxi directories, and remove the .inxi directory after to cleanup.
Also, since I was fixing some path stuff, I also did issue 77, manual inxi install not putting man pages in
/usr/local/share/man/man1, which had caused an issue with Arch linux inxi installer. Note that I can't help
users who had a manual inxi install with their man page in /usr/share/man/man1 already, because it's too risky
to guess about user or system intentions, this man location correction will only apply if users have never
installed inxi before manually, and have no distro version installed, unlike the config/data directory,
which does update neatly with output letting users know the data was moved.
Note that if users have man --path set up incorrectly, it's possible that the legacy man page would show up
instead, which isn't good, but there was no perfect fix for the man issue so I just picked the easiest way,
ignoring all man pages installed into /usr/share/man/man1 and treating them as final location, otherwise
using if present the /usr/local/share/man/man1 location for new manual install users.
Also, for users with existing man locations and an inxi manually installed, you have to update to inxi current,
then move your man file to /usr/local/share/man/man1, then update man with: mandb command (as root), after that
inxi will update to the new man location.
Also added some more XDG debugger data as well to cover this for future debugger data.
This closes previous issue #77 (man page for manual inxi install does not go into /usr/local/share/man/man1) and
issue 101, which I made today just to force the update.
Just as a side note, I find this absurd attempt at 'simplifying by making more complex and convoluted' re the XDG
and .config and standard nix . file to be sort of tragic, because really, they've just made it all way more complicated,
and since all 3 methods can be present, all the stuff has to be tested for anyway, so this doesn't make matters cleaner
at all, it's just pointless busywork that makes some people happy since now there's even more rules to follow, sigh.
2016-12-20 02:57:56 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.6
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-12-19
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This is a significant change, but inxi should handle it smoothly.
|
|
|
|
|
|
|
|
|
|
While default configs remain in /etc/inxi.conf, the user overrides now use the following order of tests:
|
|
|
|
|
|
|
|
|
|
1. XDG_CONFIG_HOME / XDG_DATA_HOME for the config and log/debugger data respectively.
|
|
|
|
|
|
|
|
|
|
2. Since those will often be blank, it then uses a second priority check:
|
|
|
|
|
$HOME/.config $HOME/.local/share to place the inxi data directory, which was previously here:
|
|
|
|
|
$HOME/.inxi
|
|
|
|
|
|
|
|
|
|
3. If neither of these cases are present, inxi will default to its legacy user data: $HOME/.inxi as before
|
|
|
|
|
|
|
|
|
|
In order to make this switch transparent to users, inxi will move the files from .inxi to the respective
|
|
|
|
|
.config/ .local/share/inxi directories, and remove the .inxi directory after to cleanup.
|
|
|
|
|
|
|
|
|
|
Also, since I was fixing some path stuff, I also did issue 77, manual inxi install not putting man pages in
|
|
|
|
|
/usr/local/share/man/man1, which had caused an issue with Arch linux inxi installer. Note that I can't help
|
|
|
|
|
users who had a manual inxi install with their man page in /usr/share/man/man1 already, because it's too risky
|
|
|
|
|
to guess about user or system intentions, this man location correction will only apply if users have never
|
|
|
|
|
installed inxi before manually, and have no distro version installed, unlike the config/data directory,
|
|
|
|
|
which does update neatly with output letting users know the data was moved.
|
|
|
|
|
|
|
|
|
|
Note that if users have man --path set up incorrectly, it's possible that the legacy man page would show up
|
|
|
|
|
instead, which isn't good, but there was no perfect fix for the man issue so I just picked the easiest way,
|
|
|
|
|
ignoring all man pages installed into /usr/share/man/man1 and treating them as final location, otherwise
|
|
|
|
|
using if present the /usr/local/share/man/man1 location for new manual install users.
|
|
|
|
|
|
|
|
|
|
Also, for users with existing man locations and an inxi manually installed, you have to update to inxi current,
|
|
|
|
|
then move your man file to /usr/local/share/man/man1, then update man with: mandb command (as root), after that
|
|
|
|
|
inxi will update to the new man location.
|
|
|
|
|
|
|
|
|
|
Also added some more XDG debugger data as well to cover this for future debugger data.
|
|
|
|
|
|
|
|
|
|
This closes previous issue #77 (man page for manual inxi install does not go into /usr/local/share/man/man1) and
|
|
|
|
|
issue 101, which I made today just to force the update.
|
|
|
|
|
|
|
|
|
|
Just as a side note, I find this absurd attempt at 'simplifying by making more complex and convoluted' re the XDG
|
|
|
|
|
and .config and standard nix . file to be sort of tragic, because really, they've just made it all way more complicated,
|
|
|
|
|
and since all 3 methods can be present, all the stuff has to be tested for anyway, so this doesn't make matters cleaner
|
|
|
|
|
at all, it's just pointless busywork that makes some people happy since now there's even more rules to follow, sigh.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 19 Dec 2016 18:38:57 -0800
|
|
|
|
|
|
2016-12-03 00:03:42 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.5
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-12-02
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This will matter to some users, inxi had failed to add 'modesetting'
|
|
|
|
|
graphics driver, so it would not show in output, which causes support issues for users of that specific
|
|
|
|
|
driver, like some cases of Intel. Also inxi would always have failed to show it unloaded in cases where
|
|
|
|
|
radeon/nouveau were used but it had been loaded by xorg to begin with. So probably worth updating packages
|
|
|
|
|
I'd say.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 02 Dec 2016 16:00:57 -0800
|
|
|
|
|
|
2016-11-04 03:21:51 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.4
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-11-03
|
|
|
|
|
-----------------------------------
|
2016-11-22 19:14:31 +00:00
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No new version, just fixed some unwanted executable bits in files.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 22 Nov 2016 11:13:15 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.4
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-11-03
|
|
|
|
|
-----------------------------------
|
2016-11-04 03:21:51 +00:00
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Squeezing in a last change for 2.3.4, added to -m if valid output, and if no -I or -tm
|
|
|
|
|
triggers used, will show system ram used/total, from the -I line.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 03 Nov 2016 20:20:37 -0700
|
|
|
|
|
|
2016-11-04 02:44:48 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.4
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-11-03
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This improves -D output, now capacity is on its own line, and
|
|
|
|
|
each disk is on its own line always, this makes it easier to read and/or parse.
|
|
|
|
|
|
|
|
|
|
Also, the lines now wrap nicely for extra data > console width, or -y 80 for example if
|
|
|
|
|
you're trying to force most of the data to fit into 80 columns.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 03 Nov 2016 19:39:15 -0700
|
|
|
|
|
|
2016-10-29 22:15:43 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.3
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-10-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, updated man page.
|
|
|
|
|
|
|
|
|
|
This is a small syntax fix that will have essentially no impact on anyone. I've just cleaned
|
|
|
|
|
up the man code to make it simple enough for roffit man to html conversion. There should be
|
|
|
|
|
no real visible differences as far as I know.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 29 Oct 2016 15:13:40 -0700
|
|
|
|
|
|
2016-10-25 19:20:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.3
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-10-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Extended support and tests for vm id to include better BSD
|
|
|
|
|
handling, and legacy linux. VM id will remain a work in progress, and will probably
|
|
|
|
|
require a few fixes for fringe cases. Nice to have would be things like OpenBSD's
|
|
|
|
|
vm which is difficult to detect. However, I believe this should handle roughly 99% of
|
|
|
|
|
realworld vm id cases, except for some commercial stuff that will require more data.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 25 Oct 2016 12:17:46 -0700
|
|
|
|
|
|
2016-10-24 04:28:40 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.2
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-10-23
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
version number unchanged, just added a vm possible id, will impact few users, if you care, update.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 23 Oct 2016 21:27:23 -0700
|
|
|
|
|
|
New feature, new tarball, new version number.
Now -M shows device type, like desktop, laptop, notebook, server, blade, vm (and tries to get vm type).
vm detection will take more work, for now I'm just going for the main ones used, but it will certainly
miss some because it's hard to detect them in some cases unless you use root features. Also note, in
most cases a container I believe will display as a vm, which is fine for now.
For BSDs, and older linux, there is a dmidecode fallback detection as well.
2016-10-21 01:36:24 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.2
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-10-20
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New feature, new tarball, new version number.
|
|
|
|
|
|
|
|
|
|
Now -M shows device type, like desktop, laptop, notebook, server, blade, vm (and tries to get vm type).
|
|
|
|
|
|
|
|
|
|
vm detection will take more work, for now I'm just going for the main ones used, but it will certainly
|
|
|
|
|
miss some because it's hard to detect them in some cases unless you use root features. Also note, in
|
|
|
|
|
most cases a container I believe will display as a vm, which is fine for now.
|
|
|
|
|
|
|
|
|
|
For BSDs, and older linux, there is a dmidecode fallback detection as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 20 Oct 2016 18:03:54 -0700
|
|
|
|
|
|
2016-09-09 21:54:14 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.1
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-08-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Fixed typo in man page, no new version, just a fixed man page.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 09 Sep 2016 14:53:24 -0700
|
|
|
|
|
|
2016-08-26 02:18:30 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.1
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-08-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page.
|
|
|
|
|
|
|
|
|
|
Basic support added for Budgie desktop detection. This is waiting more data, so the support will be
|
|
|
|
|
missing the version information. Go Budgie!!
|
|
|
|
|
|
|
|
|
|
Added /var/tmp and /var/log and /opt to basic partition data: -P
|
|
|
|
|
This will probably not impact more than a handful of people in the world, but that's fine.
|
|
|
|
|
|
|
|
|
|
Modified the static BIOS in -M to now show UEFI for actually UEFI booted systems, and, ideally,
|
|
|
|
|
UEFI [Legacy] for UEFI booting in bios legacy mode, and BIOS for all others. Hopefully this will
|
|
|
|
|
work ok, we'll see.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 25 Aug 2016 19:09:52 -0700
|
|
|
|
|
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.3.0
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-04-18
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
|
|
|
|
|
-B option now shows, if available, battery data. Quite good data for systems
|
|
|
|
|
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
|
|
|
|
|
dmidecode has no current voltage/charge/current supported capacity.
|
|
|
|
|
|
|
|
|
|
Main row shows charge and condition. Condition shows you have much capacity the
|
|
|
|
|
battery currently has vs its design capacity. Charge shows the Wh/percent of
|
|
|
|
|
current capacity of battery (NOT the rated design capacity).
|
|
|
|
|
|
|
|
|
|
-x adds battery vendor/model info, and battery status (like, charging, discharging,
|
|
|
|
|
full).
|
|
|
|
|
|
|
|
|
|
-xx adds battery serial number and voltage information. Note that voltage information
|
|
|
|
|
is presented as Current Voltage / Designed minimum voltage.
|
|
|
|
|
|
|
|
|
|
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
|
|
|
|
|
that makes the cycle count always be 0, I don't know if that's in the batteries,
|
|
|
|
|
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
|
|
|
|
|
my datasets so far.
|
|
|
|
|
|
|
|
|
|
For dmidecode output, the location of the batter is also shown in -xxx
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 18 Apr 2016 16:55:12 -0700
|
|
|
|
|
|
2016-03-31 22:12:51 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.38
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-03-31
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
URGENT BUG FIX! This fixes a bug introduced in 2.2.36 2016-03-21. New version, new tarball.
|
|
|
|
|
|
|
|
|
|
A sloppy unescaped / triggered a failure I didn't notice in partition info.
|
|
|
|
|
|
|
|
|
|
Please update your inxi packages immediately if your version is 2016-03-21 or newer.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 31 Mar 2016 15:08:54 -0700
|
|
|
|
|
|
2016-03-30 20:32:04 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.37
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-03-30
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Tiny fix in distro detection, will now default in sequence
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
on /etc/issue step to first test for os release and not mint, then lsb verison and
|
2016-03-30 20:32:04 +00:00
|
|
|
not mint, then /etc/issue. This should keep the mint detection working well, as long
|
|
|
|
|
as they keep mint string in the /etc/issue file, that is, but that's out of our control.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 30 Mar 2016 13:28:40 -0700
|
|
|
|
|
|
2016-03-21 23:12:08 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.36
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-03-21
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. A tiny bug fix for kfreebsd, I know, right, nobody uses that.
|
|
|
|
|
|
|
|
|
|
Also added in some more script color options however, which might be of use. These are
|
|
|
|
|
aimed more at light terminal backgrounds.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 21 Mar 2016 16:04:33 -0700
|
|
|
|
|
|
2016-02-29 20:23:22 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.35
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-02-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. A tiny, but meaningful, fix. inxi had not been updated to
|
|
|
|
|
test for the non deprecated battery test, /sys/class/power_supply/BAT0 existence.
|
|
|
|
|
|
|
|
|
|
This resulted in failure to indicate 'portable' where applicable.
|
|
|
|
|
|
|
|
|
|
I may also now add battery information where applicable since that's easy to get from
|
|
|
|
|
/sys
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 29 Feb 2016 12:21:09 -0800
|
|
|
|
|
|
2016-02-21 19:32:57 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.34
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-02-21
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This closes two issues:
|
|
|
|
|
|
|
|
|
|
1. Add amdgpu to possible xorg drivers list (and gpu sensors data)
|
|
|
|
|
|
|
|
|
|
2. switch to default dig command to get WAN ip. This is usually but not always faster than
|
|
|
|
|
the http method. Because the IP source is not truly trustworthy (run by cisco), I'm keeping a
|
|
|
|
|
fallback mode on 1 second time out failure of the previous http based methods. Added dig
|
|
|
|
|
to recommended tools list.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 21 Feb 2016 11:18:54 -0800
|
|
|
|
|
|
2016-02-09 19:22:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.33
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2016-01-30
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, new tarball. Someone spotted a small glitch in -W help menu.
|
|
|
|
|
|
|
|
|
|
Says latitude/longtitude instead of latitude,longtitude
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 09 Feb 2016 11:20:03 -0800
|
|
|
|
|
|
2016-01-03 22:09:57 +00:00
|
|
|
=====================================================================================
|
2016-01-31 01:13:25 +00:00
|
|
|
Version: 2.2.33
|
2016-01-03 22:09:57 +00:00
|
|
|
Patch Version: 00
|
2016-01-31 01:13:25 +00:00
|
|
|
Script Date: 2016-01-30
|
2016-01-03 22:09:57 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2016-01-31 01:13:25 +00:00
|
|
|
New version, new tarball. Bug fix: added basic support for NVMe M2 disk storage type.
|
|
|
|
|
|
|
|
|
|
NOTE: missing product name/serial info, because it's not being treated by linux kernel
|
|
|
|
|
as a standard disk. Could not find that data anywhere in the system debugger dump.
|
|
|
|
|
|
|
|
|
|
If you know how to find the model name/number and or serial, let me know.
|
|
|
|
|
|
|
|
|
|
Also small fix, as noted: ip: should be ip-v4 to match with ip-v6, thanks mikaela.
|
|
|
|
|
|
|
|
|
|
Also some debugger fixes and updates.
|
|
|
|
|
|
2016-01-03 22:09:57 +00:00
|
|
|
-----------------------------------
|
2016-01-31 01:13:25 +00:00
|
|
|
-- Harald Hope - Sat, 30 Jan 2016 17:07:42 -0800
|
|
|
|
|
|
2016-01-03 22:09:57 +00:00
|
|
|
|
2015-12-30 21:12:45 +00:00
|
|
|
=====================================================================================
|
2016-01-31 01:13:25 +00:00
|
|
|
Version: 2.2.32
|
2015-12-30 21:12:45 +00:00
|
|
|
Patch Version: 00
|
2016-01-31 01:13:25 +00:00
|
|
|
Script Date: 2016-01-03
|
2015-12-30 21:12:45 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2016-01-31 01:13:25 +00:00
|
|
|
New version, new tarball. Finalized the * expansion fix for arrays. This is a significant
|
|
|
|
|
bug fix, so while the bug almost never appears, if it does, the inxi output can get completely
|
|
|
|
|
corrupted.
|
2015-12-30 21:12:45 +00:00
|
|
|
-----------------------------------
|
2016-01-31 01:13:25 +00:00
|
|
|
-- Harald Hope - Sun, 03 Jan 2016 14:08:04 -0800
|
2015-12-30 21:12:45 +00:00
|
|
|
|
2015-12-29 22:06:45 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.31
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-12-29
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, new tarball.
|
|
|
|
|
|
|
|
|
|
Cleaned up some logging glitches.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 29 Dec 2015 14:01:07 -0800
|
|
|
|
|
|
2015-11-16 01:26:19 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.31
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-11-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
New version, new tarball. Try 2 at mmcblk support. I had mmcblock, thats not how it's
|
2015-11-16 01:26:19 +00:00
|
|
|
reported to the system.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 15 Nov 2015 17:25:10 -0800
|
|
|
|
|
|
2015-11-10 03:03:46 +00:00
|
|
|
=====================================================================================
|
2015-11-13 20:00:16 +00:00
|
|
|
Version: 2.2.30
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-11-13
|
|
|
|
|
-----------------------------------
|
2015-12-29 22:06:45 +00:00
|
|
|
Changes:
|
2015-11-13 20:00:16 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Added tentative support for /dev/blcmmc0p12 type partitions
|
|
|
|
|
and drive identifiers. This will probably require more fixes.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 13 Nov 2015 11:58:17 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2015-11-10 03:03:46 +00:00
|
|
|
Version: 2.2.29
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-11-09
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. A subtle issue pointed out by a user, inxi is limited to
|
|
|
|
|
26 drives, and fails to handle the linux > 26 options:
|
|
|
|
|
|
|
|
|
|
https://rwmj.wordpress.com/2011/01/09/how-are-linux-drives-named-beyond-drive-26-devsdz/
|
|
|
|
|
|
|
|
|
|
That article explains the failing well.
|
|
|
|
|
|
|
|
|
|
Note that because I have neither user data sets or > 26 hdd systems available, I cannot
|
|
|
|
|
verify that my fix works. It may work, that's all I can say.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 09 Nov 2015 19:00:08 -0800
|
|
|
|
|
|
2015-08-28 19:45:53 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.28
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-08-20
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, new tarball. Man page link fixes, that's all.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 28 Aug 2015 12:44:43 -0700
|
|
|
|
|
|
New version, new tarball:
Changes: updated inxi updaters to use github locations.
I will do this commit once for googlecode, and once for github, after that,
all commits will go only to github.
inxi moves to github, despite my dislike of for profit source repos, and git,
I decided that I just don't have the time or energy to do it right, so I'm going
to use github.
The project is already moved, though I have left inxi up for the time being on
code.google.com/p/inxi until I move the wiki to http://smxi.org
Everything is pretty much the same, the project url is:
https://github.com/smxi/inxi
The direct download link for the gz is:
https://github.com/smxi/inxi/raw/master/inxi.tar.gz
git pull is:
git pull https://github.com/smxi/inxi master
svn checkout url:
https://github.com/smxi/inxi
And that's about it.
2015-08-20 23:32:57 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.28
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-08-20
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball:
|
|
|
|
|
Changes: updated inxi updaters to use github locations.
|
|
|
|
|
|
|
|
|
|
I will do this commit once for googlecode, and once for github, after that,
|
|
|
|
|
all commits will go only to github.
|
|
|
|
|
|
|
|
|
|
inxi moves to github, despite my dislike of for profit source repos, and git,
|
|
|
|
|
I decided that I just don't have the time or energy to do it right, so I'm going
|
|
|
|
|
to use github.
|
|
|
|
|
|
|
|
|
|
The project is already moved, though I have left inxi up for the time being on
|
|
|
|
|
code.google.com/p/inxi until I move the wiki to http://smxi.org
|
|
|
|
|
|
|
|
|
|
Everything is pretty much the same, the project url is:
|
|
|
|
|
|
|
|
|
|
https://github.com/smxi/inxi
|
|
|
|
|
|
|
|
|
|
The direct download link for the gz is:
|
|
|
|
|
|
|
|
|
|
https://github.com/smxi/inxi/raw/master/inxi.tar.gz
|
|
|
|
|
|
|
|
|
|
git pull is:
|
|
|
|
|
|
|
|
|
|
git pull https://github.com/smxi/inxi master
|
|
|
|
|
|
|
|
|
|
svn checkout url:
|
|
|
|
|
|
|
|
|
|
https://github.com/smxi/inxi
|
|
|
|
|
|
|
|
|
|
And that's about it.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 20 Aug 2015 16:01:32 -0700
|
|
|
|
|
|
2015-08-02 21:21:04 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.27
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-08-02
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Trivial wget/curl change, nothing else. No need to upgrade packages.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 02 Aug 2015 14:18:45 -0700
|
|
|
|
|
|
2015-07-06 22:53:44 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.26
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-07-06
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes a bug with the last fix for KDE Plasma version. It was
|
|
|
|
|
showing Frameworks version, which is apparently NOT the same as the plasma version.
|
|
|
|
|
|
|
|
|
|
Also added debugger kde versioning to make this stuff less of an ordeal for data collection.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 06 Jul 2015 15:51:51 -0700
|
|
|
|
|
|
|
|
|
|
|
2015-06-16 01:02:06 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.25
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-06-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Same version, new tarball, I'm tossing this in with the other release, changing for kde >= 4,
|
|
|
|
|
changing simple KDE to KDE Plasma, which keeps it clear and simple.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 15 Jun 2015 18:00:42 -0700
|
|
|
|
|
|
2015-06-16 00:51:45 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.25
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-06-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Got a good fix for the kde version issue from the lads at
|
|
|
|
|
#kde-devel, now using kf5-config --version which gives similar output to kded4 --version
|
|
|
|
|
|
|
|
|
|
I use this for both 4 and 5, but since 4 has worked fine for years, I'll just use this for 5
|
|
|
|
|
and later.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 15 Jun 2015 17:49:56 -0700
|
|
|
|
|
|
new version, new tarball. Adapted to deal with yet another silly pointless change from
normal, in this case, sddm decided that using a .pid or .lock file in /run was too easy
so they changed to some session id type string in the /run/sddm/ directory.
Speaking for myself, I find such pointless changes from anything resembling normal behaviors
to the reason that gnu freedesktop systems will never achieve significant desktop use globally.
Also, in the same vein, added debuggers to try to figure out what plasma5/kde 5 is using
internally to give command line version information. Again, something pointless internally
was changed, thus breaking something that had faintly resembled an api, which is of course
why desktop gnu linux will never actually take off, developers in the real world have no
interest in chasing after such pointless and never ending churn in even the most trivial
areas of the OS, let alone the core.
inxi remains however as a log of this ongoing churn and lack of discipline, and so remains
an interesting process of observation, and a way for users to try to avoid the constant
changes in simple system queries that should really never change, so I can see a reason
to keep it going since it's obvious that the actual foss ecosystem itself will not and apparently
cannot grasp that it is the lack of stable apis, methods, etc, that has kept desktop gnu linux
from achieving any actual real world success or popularity, and that is the actual problem
that should be fixed, not some pointless internal change to something.
On the source repo front, maintainers, I still can't find an acceptable alternative to the
impending shutdown of googlecode. github is a for profit venture that people who seem totally
void of any sense of history believe is actually going to be around longer than say, sourceforge,
or googlecode, as a legitimate source hosting site.
I'd welcome any suggestions. So far all the options are bad that I can find.
Top preference is svn, but if git is the absolute only other choice for an otherwise good option,
I'd consider git, but it's a horrible option for inxi because of how inxi development and debugging
works, vs how git works. ie, svn branches are perfect, git branches are totally wrong.
I may end up just hosting the svn on my own servers to avoid having to move yet again when the next
for profit flakey site decides to close up or monetize the source hosting.
The original idea of googlecode was for google to 'pay its dues to the foss community', but apparently
they got bored with that idea, plus of course, the ongoing total failure of google to deal with
automated spam, which has always been a huge bug in the core google corporate culture. But googlecode
was by far the best option I've come across, it was done by a deep pocketed corporation not for profit
for pretty good reasons, and was never intended to be a profit center, which is the closest I could
see for a non free option.
Setting up svn gui stuff however is a royal pain and requires ongoing maintainance for the life of
the software, which is NOT fun, nor will I sign up for that obligation.
I may end up moving to github anyway, even though git truly sucks for inxi and myself, but it's an
idea I find fairly vile, apparently free software (sic) authors seem to have no grasp of the concept
of fredom when it comes to source code hosting, judging by the absurd popularity of github as the
default go to source repo. Their website is pathetic as well, which isn't very promising.
So we'll see where it goes, I think I have until august to decide what to do for source hosting.
Since I'm old enough to have seen sourceforge and now googlecode do the same thing, along with a lot
of other options, to say github won't do this too is delusional, what you can almost certainly say is it
will do it, the only question is when. But, just as Linus did with his non free linux kernel version
control, people will stick with the non free stuff until you realize you can't use it anymore, because
it is non free. Free software hosted on non free source repos is to me one of the most absurd and
stupid things I've ever heard of to be honest.
2015-06-15 22:38:06 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.24
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-06-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, new tarball. Adapted to deal with yet another silly pointless change from
|
|
|
|
|
normal, in this case, sddm decided that using a .pid or .lock file in /run was too easy
|
|
|
|
|
so they changed to some session id type string in the /run/sddm/ directory.
|
|
|
|
|
|
|
|
|
|
Speaking for myself, I find such pointless changes from anything resembling normal behaviors
|
|
|
|
|
to the reason that gnu freedesktop systems will never achieve significant desktop use globally.
|
|
|
|
|
|
|
|
|
|
Also, in the same vein, added debuggers to try to figure out what plasma5/kde 5 is using
|
|
|
|
|
internally to give command line version information. Again, something pointless internally
|
|
|
|
|
was changed, thus breaking something that had faintly resembled an api, which is of course
|
|
|
|
|
why desktop gnu linux will never actually take off, developers in the real world have no
|
|
|
|
|
interest in chasing after such pointless and never ending churn in even the most trivial
|
|
|
|
|
areas of the OS, let alone the core.
|
|
|
|
|
|
|
|
|
|
inxi remains however as a log of this ongoing churn and lack of discipline, and so remains
|
|
|
|
|
an interesting process of observation, and a way for users to try to avoid the constant
|
|
|
|
|
changes in simple system queries that should really never change, so I can see a reason
|
|
|
|
|
to keep it going since it's obvious that the actual foss ecosystem itself will not and apparently
|
|
|
|
|
cannot grasp that it is the lack of stable apis, methods, etc, that has kept desktop gnu linux
|
|
|
|
|
from achieving any actual real world success or popularity, and that is the actual problem
|
|
|
|
|
that should be fixed, not some pointless internal change to something.
|
|
|
|
|
|
|
|
|
|
On the source repo front, maintainers, I still can't find an acceptable alternative to the
|
|
|
|
|
impending shutdown of googlecode. github is a for profit venture that people who seem totally
|
|
|
|
|
void of any sense of history believe is actually going to be around longer than say, sourceforge,
|
|
|
|
|
or googlecode, as a legitimate source hosting site.
|
|
|
|
|
|
|
|
|
|
I'd welcome any suggestions. So far all the options are bad that I can find.
|
|
|
|
|
|
|
|
|
|
Top preference is svn, but if git is the absolute only other choice for an otherwise good option,
|
|
|
|
|
I'd consider git, but it's a horrible option for inxi because of how inxi development and debugging
|
|
|
|
|
works, vs how git works. ie, svn branches are perfect, git branches are totally wrong.
|
|
|
|
|
|
|
|
|
|
I may end up just hosting the svn on my own servers to avoid having to move yet again when the next
|
|
|
|
|
for profit flakey site decides to close up or monetize the source hosting.
|
|
|
|
|
|
|
|
|
|
The original idea of googlecode was for google to 'pay its dues to the foss community', but apparently
|
|
|
|
|
they got bored with that idea, plus of course, the ongoing total failure of google to deal with
|
|
|
|
|
automated spam, which has always been a huge bug in the core google corporate culture. But googlecode
|
|
|
|
|
was by far the best option I've come across, it was done by a deep pocketed corporation not for profit
|
|
|
|
|
for pretty good reasons, and was never intended to be a profit center, which is the closest I could
|
|
|
|
|
see for a non free option.
|
|
|
|
|
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
Setting up svn gui stuff however is a royal pain and requires ongoing maintainance for the life of
|
new version, new tarball. Adapted to deal with yet another silly pointless change from
normal, in this case, sddm decided that using a .pid or .lock file in /run was too easy
so they changed to some session id type string in the /run/sddm/ directory.
Speaking for myself, I find such pointless changes from anything resembling normal behaviors
to the reason that gnu freedesktop systems will never achieve significant desktop use globally.
Also, in the same vein, added debuggers to try to figure out what plasma5/kde 5 is using
internally to give command line version information. Again, something pointless internally
was changed, thus breaking something that had faintly resembled an api, which is of course
why desktop gnu linux will never actually take off, developers in the real world have no
interest in chasing after such pointless and never ending churn in even the most trivial
areas of the OS, let alone the core.
inxi remains however as a log of this ongoing churn and lack of discipline, and so remains
an interesting process of observation, and a way for users to try to avoid the constant
changes in simple system queries that should really never change, so I can see a reason
to keep it going since it's obvious that the actual foss ecosystem itself will not and apparently
cannot grasp that it is the lack of stable apis, methods, etc, that has kept desktop gnu linux
from achieving any actual real world success or popularity, and that is the actual problem
that should be fixed, not some pointless internal change to something.
On the source repo front, maintainers, I still can't find an acceptable alternative to the
impending shutdown of googlecode. github is a for profit venture that people who seem totally
void of any sense of history believe is actually going to be around longer than say, sourceforge,
or googlecode, as a legitimate source hosting site.
I'd welcome any suggestions. So far all the options are bad that I can find.
Top preference is svn, but if git is the absolute only other choice for an otherwise good option,
I'd consider git, but it's a horrible option for inxi because of how inxi development and debugging
works, vs how git works. ie, svn branches are perfect, git branches are totally wrong.
I may end up just hosting the svn on my own servers to avoid having to move yet again when the next
for profit flakey site decides to close up or monetize the source hosting.
The original idea of googlecode was for google to 'pay its dues to the foss community', but apparently
they got bored with that idea, plus of course, the ongoing total failure of google to deal with
automated spam, which has always been a huge bug in the core google corporate culture. But googlecode
was by far the best option I've come across, it was done by a deep pocketed corporation not for profit
for pretty good reasons, and was never intended to be a profit center, which is the closest I could
see for a non free option.
Setting up svn gui stuff however is a royal pain and requires ongoing maintainance for the life of
the software, which is NOT fun, nor will I sign up for that obligation.
I may end up moving to github anyway, even though git truly sucks for inxi and myself, but it's an
idea I find fairly vile, apparently free software (sic) authors seem to have no grasp of the concept
of fredom when it comes to source code hosting, judging by the absurd popularity of github as the
default go to source repo. Their website is pathetic as well, which isn't very promising.
So we'll see where it goes, I think I have until august to decide what to do for source hosting.
Since I'm old enough to have seen sourceforge and now googlecode do the same thing, along with a lot
of other options, to say github won't do this too is delusional, what you can almost certainly say is it
will do it, the only question is when. But, just as Linus did with his non free linux kernel version
control, people will stick with the non free stuff until you realize you can't use it anymore, because
it is non free. Free software hosted on non free source repos is to me one of the most absurd and
stupid things I've ever heard of to be honest.
2015-06-15 22:38:06 +00:00
|
|
|
the software, which is NOT fun, nor will I sign up for that obligation.
|
|
|
|
|
|
|
|
|
|
I may end up moving to github anyway, even though git truly sucks for inxi and myself, but it's an
|
|
|
|
|
idea I find fairly vile, apparently free software (sic) authors seem to have no grasp of the concept
|
|
|
|
|
of fredom when it comes to source code hosting, judging by the absurd popularity of github as the
|
|
|
|
|
default go to source repo. Their website is pathetic as well, which isn't very promising.
|
|
|
|
|
|
|
|
|
|
So we'll see where it goes, I think I have until august to decide what to do for source hosting.
|
|
|
|
|
|
|
|
|
|
Since I'm old enough to have seen sourceforge and now googlecode do the same thing, along with a lot
|
|
|
|
|
of other options, to say github won't do this too is delusional, what you can almost certainly say is it
|
|
|
|
|
will do it, the only question is when. But, just as Linus did with his non free linux kernel version
|
|
|
|
|
control, people will stick with the non free stuff until you realize you can't use it anymore, because
|
|
|
|
|
it is non free. Free software hosted on non free source repos is to me one of the most absurd and
|
|
|
|
|
stupid things I've ever heard of to be honest.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 15 Jun 2015 15:19:02 -0700
|
|
|
|
|
|
2015-06-08 22:47:29 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.23
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-06-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Tiny change. Added /etc/devuan_version file to distro id to handle
|
|
|
|
|
the switched file name. Kudos to anyone out there fighting to create a working alternative
|
|
|
|
|
to the unreliable and buggy and windows emulating systemd, I wish devuan luck. Maybe between
|
|
|
|
|
devuan and gentoo and slackware we can save the free software core systems before it's too late.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 08 Jun 2015 15:43:52 -0700
|
|
|
|
|
|
New version, new man page, new tarball. Modified slightly -tc and -tm output to fix a
pet peeve of mine. Now, if -I, -b, -F, or anything that can trigger the memory: used/total
in Information line is not used, -tm will always show the system used/total ram data on the
first line of the Memory item of -t output.
Also, if -xtc (trigger ram data in cpu output) is used, and -I is not triggered, and -tm is
not triggered, will also show system used/total ram data on the cpu first line.
I'd found it odd that this data did not appear when -tcm or -tm or -xtc were used, so this is
now fixed. I used the -t option a fair amount to find memory/cpu use issues, and usually I
don't use the option with other options, so the lack of total system ram data was odd.
2015-05-30 18:55:54 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.22
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-05-30
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new man page, new tarball. Modified slightly -tc and -tm output to fix a
|
|
|
|
|
pet peeve of mine. Now, if -I, -b, -F, or anything that can trigger the memory: used/total
|
|
|
|
|
in Information line is not used, -tm will always show the system used/total ram data on the
|
|
|
|
|
first line of the Memory item of -t output.
|
|
|
|
|
|
|
|
|
|
Also, if -xtc (trigger ram data in cpu output) is used, and -I is not triggered, and -tm is
|
|
|
|
|
not triggered, will also show system used/total ram data on the cpu first line.
|
|
|
|
|
|
|
|
|
|
I'd found it odd that this data did not appear when -tcm or -tm or -xtc were used, so this is
|
|
|
|
|
now fixed. I used the -t option a fair amount to find memory/cpu use issues, and usually I
|
|
|
|
|
don't use the option with other options, so the lack of total system ram data was odd.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 30 May 2015 11:50:56 -0700
|
|
|
|
|
|
2015-05-13 20:18:38 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.21
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-05-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. A desktop id fix, Mate id failed, mate moved to a more
|
|
|
|
|
long term solution to identify itself, so the hack I had in place fails on new MATE.
|
|
|
|
|
|
|
|
|
|
We'll see if this does it for various glitches, now quassel and mate latest should
|
|
|
|
|
again be working.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 13 May 2015 13:15:59 -0700
|
|
|
|
|
|
2015-05-11 22:10:38 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.20
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-05-11
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This fixes a qt5 glitch with Quassel id, hopefully anyway.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 11 May 2015 15:08:30 -0700
|
|
|
|
|
|
2015-02-16 03:14:12 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.19
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-02-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, new tarball. Fixed the repo error message to be more accurate, since
|
|
|
|
|
a system could be supported but have no repo data, like on some livecds etc. Also made it
|
|
|
|
|
better for BSD or GNU/linux.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 15 Feb 2015 19:13:25 -0800
|
|
|
|
|
|
2015-02-16 02:17:58 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.19
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-02-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, updated man page, new tarball. Updated -r to for portage gentoo sources. This should work
|
|
|
|
|
fine for all derived distros like Sabayon as well. The test looks for:
|
|
|
|
|
/etc/portage/repos.conf/ and type -p emerge
|
|
|
|
|
if found will then grab the repos from the source files found.
|
|
|
|
|
|
|
|
|
|
Note that the logic for this was almost identical to that used for rpm so it was an
|
|
|
|
|
easy addon. Please let us know if you have an issue and provide data samples of relevant
|
|
|
|
|
files.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 15 Feb 2015 18:02:16 -0800
|
|
|
|
|
|
2015-01-24 18:51:56 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.18
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-01-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Two great bug report, issues.
|
|
|
|
|
|
|
|
|
|
1. Tightened runit init detection to use proc, note that if runit works on BSDs inxi will
|
|
|
|
|
require more data to properly detect it on BSDs..
|
|
|
|
|
2. Use openrc runlevel tests natively if openrc detected.
|
|
|
|
|
3. Fixed subtle issue with alias to inxi file and paths.
|
|
|
|
|
4. Added rc-status data collection for debugger, improved debugger data collector handling
|
|
|
|
|
of bsd and other tests to note absent if not there in file names.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 24 Jan 2015 10:25:43 -0800
|
|
|
|
|
|
2015-01-14 20:41:55 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.17
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2015-01-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New Version, new tarball.
|
|
|
|
|
|
|
|
|
|
Fixed bugs in Epoch init system detection, caused false positives in systems booted on
|
|
|
|
|
SysVinit, but with Epoch installed. Epoch turns out to be in PID 1 == epoch (/proc/1/comm)
|
|
|
|
|
so that's easy to fix.
|
|
|
|
|
|
|
|
|
|
Also fixed spacing isxue with OpenRC output in -I line.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 14 Jan 2015 12:28:00 -0800
|
|
|
|
|
|
New version, tarball. Very small update, added sddm id to dm detecfion. Because Arch linux,
at least on the system I got data from, is not using .pid/.lock extensions, but other systems
are, I'm adding sddm AND sddm.pid detection. This required changing the id to use explicit -f
for test, not the previous -e, which will force only files, not directories, to trigger yes case.
No other changes, but it's worth updating to this because distros may start using sddm in the not so
distant future, it's beta currently though.
2014-11-04 03:29:21 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.16
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-11-03
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Very small update, added sddm id to dm detecfion. Because Arch linux,
|
|
|
|
|
at least on the system I got data from, is not using .pid/.lock extensions, but other systems
|
|
|
|
|
are, I'm adding sddm AND sddm.pid detection. This required changing the id to use explicit -f
|
|
|
|
|
for test, not the previous -e, which will force only files, not directories, to trigger yes case.
|
|
|
|
|
|
|
|
|
|
No other changes, but it's worth updating to this because distros may start using sddm in the not so
|
|
|
|
|
distant future, it's beta currently though.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 03 Nov 2014 19:26:22 -0800
|
|
|
|
|
|
2014-10-12 19:11:42 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.15
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-10-12
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Debian has for some reason broken procps / uptime support, for
|
|
|
|
|
as of yet unknown reasons, so rather than wait to see the bug resolved, I'm just removing
|
|
|
|
|
uptime as a depenendency, though this is a short term hack only because we don't know
|
|
|
|
|
why it was removed from procps or if that was just a mistake, or if other things as well might
|
|
|
|
|
be vanishing from procps. Am leaving in however uname as dependency because inxi cannot
|
|
|
|
|
determine what platform it is when it starts without that.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 12 Oct 2014 12:07:03 -0700
|
|
|
|
|
|
2014-09-27 07:11:11 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-26
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Bug fix for regression introduced in last versions. Double
|
|
|
|
|
output for apt repos. Also refactored duplicated code into a function, no other changes.
|
|
|
|
|
|
|
|
|
|
Note that this version features the repo debugger tool as well, which is very helpful in
|
|
|
|
|
particularly non apt systems to fix issues with its handling of repo formats etc.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 27 Sep 2014 00:09:07 -0700
|
|
|
|
|
|
2014-09-26 04:40:26 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.13
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Added slackpkgplus support, added freebsd pkg servers,
|
|
|
|
|
added netbsd pkg servers, all to -r.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 25 Sep 2014 21:39:07 -0700
|
|
|
|
|
|
2014-09-25 07:54:37 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. For some weird reason rpm query didn't work with gawk all
|
|
|
|
|
on one line, moved to separate lines. Who knows why? This only impacts rpm distros.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 25 Sep 2014 00:19:06 -0700
|
|
|
|
|
|
2014-09-24 20:21:28 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.11
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes broken slackpkg handling in -r, and, using the same fix,
|
|
|
|
|
fixes a single scenario with apt, where there is only sources.list, no .d/*.list files.
|
|
|
|
|
I was assuming that the file name would print out in the output of single file grep,
|
|
|
|
|
but that only happens with multiple files.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 24 Sep 2014 13:18:41 -0700
|
|
|
|
|
|
2014-09-24 17:35:05 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.10
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Added slackpkg support -R; added rpm support for gtk version (-Sx).
|
|
|
|
|
|
|
|
|
|
bsds: removed dragonly specific used mem hack, now will work for any bsd, if avm in vmstat is 0
|
|
|
|
|
adds a flag to value, and removes it when used.
|
|
|
|
|
|
|
|
|
|
Nothing else of note.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 24 Sep 2014 10:23:31 -0700
|
|
|
|
|
|
2014-09-22 23:11:36 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.9
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-22
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This is only for bsds. Added hack to get dragonfly used ram,
|
|
|
|
|
added dragonfly/freebsd repos full support.
|
|
|
|
|
|
|
|
|
|
Added sort of drives order to get around gawk pseudo array hash issues.
|
|
|
|
|
|
|
|
|
|
And that's that.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 22 Sep 2014 16:06:00 -0700
|
|
|
|
|
|
2014-09-22 00:39:26 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.8
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-21
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Added lxqt desktop id that is not dependent on openbox detection.
|
|
|
|
|
|
|
|
|
|
Fixed some bugs. Added a pciconf class for audio. Added support for bsds running lspci, which
|
|
|
|
|
lets openbsd show card info for -A,-G,-N
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 21 Sep 2014 17:37:23 -0700
|
|
|
|
|
|
2014-09-18 04:27:05 +00:00
|
|
|
=====================================================================================
|
2014-09-20 02:55:26 +00:00
|
|
|
Version: 2.2.7
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-19
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Mostly bsd fixes, a few for linux disk info.
|
|
|
|
|
|
|
|
|
|
Added support, basic, for bsd hard disks, and optical disks.
|
|
|
|
|
|
|
|
|
|
Added hard disk total/percent used for BSDs, sort of.
|
|
|
|
|
|
|
|
|
|
These are mostly just hacks since the data isn't easily available from system
|
|
|
|
|
standard tools, though I could on freebsd use gpart I guess but that's another tool
|
|
|
|
|
needed, and another method, too much work imo for small results.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 19 Sep 2014 19:52:10 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-09-18 04:27:05 +00:00
|
|
|
Version: 2.2.6
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-17
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Cleaned up and made more consistent the cpu max/min output.
|
|
|
|
|
|
|
|
|
|
Now the short form, the -b/-v1 form, and the -C forms are all similar.
|
|
|
|
|
|
|
|
|
|
Also, added a few hacks to try to extract cpu max speed from cpu model string in
|
|
|
|
|
either sysctl -a OR /var/run/dmesg.boot data in freebsd/openbsd. Sometimes it may
|
|
|
|
|
work if that data was in the model string. It's a hack, but will do until we get
|
|
|
|
|
better data sources or they update their sources to list more data.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 17 Sep 2014 21:24:41 -0700
|
|
|
|
|
|
2014-09-17 04:36:03 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.5
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-16
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New tarball, same version. This adds UP support for -Cxx, showing min cpu speed as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 16 Sep 2014 21:35:06 -0700
|
|
|
|
|
|
New version, new tarball. This fixes a long standing weakness with min/max cpu speed
handling. Or rather, non handling, since that data only showed in rare cases on short form
(inxi no args) output. Now it uses /sys query to determine min/max speed of cpu, and uses
that data to override any other min/max data discovered.
Still uses /proc/cpuinfo for actual speeds per core. The assumption in this is that all
cares will have the same min/max speeds, which is generally going to be a safe assumption.
Now in short form, inxi, output, it will show actual speed then (max speed) or just (max)
if actual speed matches max speed. Same for -b short CPU output.
For long, -C output, shows max speed before the actual cpu core speeds per core.
With -xx, and in multi cpu/core systems only, shows if available min/max speeds.
Note that not all /sys have this data, so it doesn't show any N/A if it's missing.
2014-09-17 03:41:21 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.5
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-16
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes a long standing weakness with min/max cpu speed
|
|
|
|
|
handling. Or rather, non handling, since that data only showed in rare cases on short form
|
|
|
|
|
(inxi no args) output. Now it uses /sys query to determine min/max speed of cpu, and uses
|
|
|
|
|
that data to override any other min/max data discovered.
|
|
|
|
|
|
|
|
|
|
Still uses /proc/cpuinfo for actual speeds per core. The assumption in this is that all
|
|
|
|
|
cares will have the same min/max speeds, which is generally going to be a safe assumption.
|
|
|
|
|
|
|
|
|
|
Now in short form, inxi, output, it will show actual speed then (max speed) or just (max)
|
|
|
|
|
if actual speed matches max speed. Same for -b short CPU output.
|
|
|
|
|
|
|
|
|
|
For long, -C output, shows max speed before the actual cpu core speeds per core.
|
|
|
|
|
|
|
|
|
|
With -xx, and in multi cpu/core systems only, shows if available min/max speeds.
|
|
|
|
|
|
|
|
|
|
Note that not all /sys have this data, so it doesn't show any N/A if it's missing.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 16 Sep 2014 20:26:19 -0700
|
|
|
|
|
|
2014-09-12 01:21:55 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.4
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-10
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Mostly bsd changes, except for downloader options, which now
|
|
|
|
|
permit wget/curl/(openbsd ftp)/(bsd fetch) interchangeably.
|
|
|
|
|
|
|
|
|
|
This lets more standard downloader defaults in bsds, as well as curl on gnu/linux systems
|
|
|
|
|
without triggering an error of missing wget.
|
|
|
|
|
|
|
|
|
|
1. Fixed cpu core issues on bsds, now shows core count + if > 1, cpus total.
|
|
|
|
|
|
|
|
|
|
2. Now shows OS instead of Distro on short/long output, since each bsd is an OS.
|
|
|
|
|
|
|
|
|
|
3. fixed vmstat issues for used memory outputs
|
|
|
|
|
|
|
|
|
|
Also fixed potential failures with cpu core count array by making it a ',' separated array.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 11 Sep 2014 18:15:10 -0700
|
|
|
|
|
|
New version, new tarball. Contains a major bug fix for a regression introduced in 2.2.2
-m/-M would always show requires root for dmidecode no matter what. Also improved dmidecode
error messages/handling.
Also, a fix for no display card data, now shows as expected no card data
Most other fixes are for bsd, mostly openbsd.
1. Added a class for network devices in freebsd pciconf
2. Added -r support for openbsd
3. Fixed some cpu issues for openbsd
4. Fixed an issue in openbsd/freebsd where client version data failed to get cleaned
5. Changed inxi short form output for bsds to show OS data instead of kernel data.
6. BSDs, maybe all, different syntax in xorg.0.log made unloaded gfx drivers not show,
that is fixed now.
-p fixed file system type in -p/-P for openbsd, now shows.
-I / inxi short - fixed used memory, did not show in openbsd, now does.
-f fixed cpu flags in openbsd, now works
-C corrected corrupted cpu data outputs, in openbsd at least, maybe also freebsd
-C added an openbsd hack to sometimes show cpu L2 cache
-m/-M fixed/improved dmidecode error handling for all systems
Modified handling of dmesg.boot data, synched so gawk can parse better.
2014-09-03 19:10:11 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.3
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-03
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Contains a major bug fix for a regression introduced in 2.2.2
|
|
|
|
|
|
|
|
|
|
-m/-M would always show requires root for dmidecode no matter what. Also improved dmidecode
|
|
|
|
|
error messages/handling.
|
|
|
|
|
|
|
|
|
|
Also, a fix for no display card data, now shows as expected no card data
|
|
|
|
|
|
|
|
|
|
Most other fixes are for bsd, mostly openbsd.
|
|
|
|
|
|
|
|
|
|
1. Added a class for network devices in freebsd pciconf
|
|
|
|
|
|
|
|
|
|
2. Added -r support for openbsd
|
|
|
|
|
|
|
|
|
|
3. Fixed some cpu issues for openbsd
|
|
|
|
|
|
|
|
|
|
4. Fixed an issue in openbsd/freebsd where client version data failed to get cleaned
|
|
|
|
|
|
|
|
|
|
5. Changed inxi short form output for bsds to show OS data instead of kernel data.
|
|
|
|
|
|
|
|
|
|
6. BSDs, maybe all, different syntax in xorg.0.log made unloaded gfx drivers not show,
|
|
|
|
|
that is fixed now.
|
|
|
|
|
|
|
|
|
|
-p fixed file system type in -p/-P for openbsd, now shows.
|
|
|
|
|
|
|
|
|
|
-I / inxi short - fixed used memory, did not show in openbsd, now does.
|
|
|
|
|
|
|
|
|
|
-f fixed cpu flags in openbsd, now works
|
|
|
|
|
|
|
|
|
|
-C corrected corrupted cpu data outputs, in openbsd at least, maybe also freebsd
|
|
|
|
|
|
|
|
|
|
-C added an openbsd hack to sometimes show cpu L2 cache
|
|
|
|
|
|
|
|
|
|
-m/-M fixed/improved dmidecode error handling for all systems
|
|
|
|
|
|
|
|
|
|
modified handling of dmesg.boot data, synched so gawk can parse better.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 03 Sep 2014 12:00:04 -0700
|
|
|
|
|
|
2014-09-01 23:11:41 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.2
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-09-01
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This version fixes an issue with a white space at the end of lines.
|
|
|
|
|
|
|
|
|
|
Now all lines are stripped of ending whitespaces automatically.
|
|
|
|
|
|
|
|
|
|
Also a dmidecode error handler correction, that was not working right in bsd systems.
|
|
|
|
|
|
|
|
|
|
Added some debuggers for bsd systems.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 01 Sep 2014 16:09:23 -0700
|
|
|
|
|
|
2014-08-21 02:46:20 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.1
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-20
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Some systems are showing a new xfce syntax in the xrop -root
|
|
|
|
|
output, like so, instead of the old quotes "XFCE4" it shows like this:
|
|
|
|
|
|
|
|
|
|
XFCE_DESKTOP_WINDOW(WINDOW): window id # 0x1000003
|
|
|
|
|
|
|
|
|
|
Updated and added a much less strict fallback test case.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 20 Aug 2014 19:43:59 -0700
|
|
|
|
|
|
New version, tarball, man page. Maintainers, this is the official release of -m feature.
I have collected enough datasamples to allow for reasonably fine grained corrections, estimates,
warnings about unreliable capacity now, and have fixed all major failures.
Also, because this stuff is filled out by people somewhere, or not, some fields often are just
empty, or contain the default values, ie, they are worthless. inxi shows N/A for those situations,
it means there is really no actual data to show you.
This feature, sadly, well never be totally reliable, because dmi data is frankly junk, especially
dmi type 5 and 16, which is what is supposed to tell you total capacity of memory array, and the
maximum module size (type 5). However, this data is totally random, often it is right, sometimes
it is wrong. Sometimes type 5 is right and type 16 is wrong, sometimes the other way. And since
type 5 is only present in some systems, it's not reliable anyway.
What is reliable and always right is the actually installed memory per device, ie, sticks. I have
not seen any errors in that, so that seems to be actually coming from the system itself. type 5 / 16
sadly are clearly entered in manually by some poorly paid engineers out there in the world, and are
often total fictions, either far too small, or far too big, or whatever.
inxi will attempt to correct all clear logic errors, and whenever it changes the listed data from
type 5/16, it notes either (est) or (check). (est) means it is a good guess, one I am comfortable making,
(check) means it is either an unreliable guess, or that what the system is reporting is so unlikely that
even though inxi is showing it, it doubts it could actually be true, or at least, it thinks you
should check this yourself.
-m has 3 extra data options, -x prints the part number, if found, and the max module size, if type 5
is present. inxi does NOT attempt to guess at max module size based on what is installed, it only will
correct a listed max module size if installed modules are > than listed max size. Usually part numbers,
if present, are all you need to order a new stick.
-xx shows serial number, manufacturer (often empty, or just random alphanumeric identifiers, but sometimes
they list the actual company name, which is helpful. It also shows, if type 5 data is present, single/double
bank.
-xxx as usual shows largely useless data that may be of interest to soemone, like if ram type is synchronous,
memory bus width data, and module voltage (type 5 data).
This feature will never be reliable I am sad to say because the source data itself is random and much
has been filled out, or not filled out, by engineering drones somewhere out there in the underpaid
world. The ranges of errors are so wide that inxi just has to check what is possible, reasonable, unlikely,
etc, to generate its numbers. In other words, this is NOT just parsing dmidecode output, that is the raw
material only, sad to say.
So this is it, for better or worse. All bug / issue reports with this MUST come with a full:
inxi -xx@14
hardware data upload, run as root.
Also, much to my annoyance, this feature requires root, since /dev/mem needs root to be read, and I assume
the dmi table, so that is a departure from normal inxi standards, as is the low quality input, and thus,
output, data, though I can guarantee that what inxi tells you is in most cases on average more accurate than
what dmidecode tells you, since dmidecode simply prints out what it finds in the dmi table, and nothing else,
in whatever order it finds it, from what I can see, ie, you also cannot trust the order of dmidecode output.
I had been hoping that /sys would start to contain memory data like it does mobo/system data, but it never
happened so I finally decided to just do the ram thing, require dmidecode, require root/sudo, and that's
that.
There will be issue reports, you can help them by looking up the mobo stats/specs yourself and listing them
in the issue, so I don't have to do it. I use the tool at crucial.com which is very accurate and also very
complete in terms of all possible hardware out there.
I would trust that tool before trusting the companies that have the least reliable data, like ASUS.
Much thanks to everyone who is contributing datasets, and the distros, particularly siduction, that really
were very helpful in this process, by finding more and more failure cases that helped me start to tighten
the logic, and make it more and more robust. Special thanks to Mikaela, of #smxi irc.oftc.net, who came up
with two systems that both required a full redo of the logic, and thus who helped a lot in this process.
2014-08-18 22:26:25 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.2.00
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-18
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, man page. Maintainers, this is the official release of -m feature.
|
|
|
|
|
|
|
|
|
|
I have collected enough datasamples to allow for reasonably fine grained corrections, estimates,
|
|
|
|
|
warnings about unreliable capacity now, and have fixed all major failures.
|
|
|
|
|
|
|
|
|
|
Also, because this stuff is filled out by people somewhere, or not, some fields often are just
|
|
|
|
|
empty, or contain the default values, ie, they are worthless. inxi shows N/A for those situations,
|
|
|
|
|
it means there is really no actual data to show you.
|
|
|
|
|
|
|
|
|
|
This feature, sadly, well never be totally reliable, because dmi data is frankly junk, especially
|
|
|
|
|
dmi type 5 and 16, which is what is supposed to tell you total capacity of memory array, and the
|
|
|
|
|
maximum module size (type 5). However, this data is totally random, often it is right, sometimes
|
|
|
|
|
it is wrong. Sometimes type 5 is right and type 16 is wrong, sometimes the other way. And since
|
|
|
|
|
type 5 is only present in some systems, it's not reliable anyway.
|
|
|
|
|
|
|
|
|
|
What is reliable and always right is the actually installed memory per device, ie, sticks. I have
|
|
|
|
|
not seen any errors in that, so that seems to be actually coming from the system itself. type 5 / 16
|
|
|
|
|
sadly are clearly entered in manually by some poorly paid engineers out there in the world, and are
|
|
|
|
|
often total fictions, either far too small, or far too big, or whatever.
|
|
|
|
|
|
|
|
|
|
inxi will attempt to correct all clear logic errors, and whenever it changes the listed data from
|
|
|
|
|
type 5/16, it notes either (est) or (check). (est) means it is a good guess, one I am comfortable making,
|
|
|
|
|
(check) means it is either an unreliable guess, or that what the system is reporting is so unlikely that
|
|
|
|
|
even though inxi is showing it, it doubts it could actually be true, or at least, it thinks you
|
|
|
|
|
should check this yourself.
|
|
|
|
|
|
|
|
|
|
-m has 3 extra data options, -x prints the part number, if found, and the max module size, if type 5
|
|
|
|
|
is present. inxi does NOT attempt to guess at max module size based on what is installed, it only will
|
|
|
|
|
correct a listed max module size if installed modules are > than listed max size. Usually part numbers,
|
|
|
|
|
if present, are all you need to order a new stick.
|
|
|
|
|
|
|
|
|
|
-xx shows serial number, manufacturer (often empty, or just random alphanumeric identifiers, but sometimes
|
|
|
|
|
they list the actual company name, which is helpful. It also shows, if type 5 data is present, single/double
|
|
|
|
|
bank.
|
|
|
|
|
|
|
|
|
|
-xxx as usual shows largely useless data that may be of interest to soemone, like if ram type is synchronous,
|
|
|
|
|
memory bus width data, and module voltage (type 5 data).
|
|
|
|
|
|
|
|
|
|
This feature will never be reliable I am sad to say because the source data itself is random and much
|
|
|
|
|
has been filled out, or not filled out, by engineering drones somewhere out there in the underpaid
|
|
|
|
|
world. The ranges of errors are so wide that inxi just has to check what is possible, reasonable, unlikely,
|
|
|
|
|
etc, to generate its numbers. In other words, this is NOT just parsing dmidecode output, that is the raw
|
|
|
|
|
material only, sad to say.
|
|
|
|
|
|
|
|
|
|
So this is it, for better or worse. All bug / issue reports with this MUST come with a full:
|
|
|
|
|
inxi -xx@14
|
|
|
|
|
hardware data upload, run as root.
|
|
|
|
|
|
|
|
|
|
Also, much to my annoyance, this feature requires root, since /dev/mem needs root to be read, and I assume
|
|
|
|
|
the dmi table, so that is a departure from normal inxi standards, as is the low quality input, and thus,
|
|
|
|
|
output, data, though I can guarantee that what inxi tells you is in most cases on average more accurate than
|
|
|
|
|
what dmidecode tells you, since dmidecode simply prints out what it finds in the dmi table, and nothing else,
|
|
|
|
|
in whatever order it finds it, from what I can see, ie, you also cannot trust the order of dmidecode output.
|
|
|
|
|
|
|
|
|
|
I had been hoping that /sys would start to contain memory data like it does mobo/system data, but it never
|
|
|
|
|
happened so I finally decided to just do the ram thing, require dmidecode, require root/sudo, and that's
|
|
|
|
|
that.
|
|
|
|
|
|
|
|
|
|
There will be issue reports, you can help them by looking up the mobo stats/specs yourself and listing them
|
|
|
|
|
in the issue, so I don't have to do it. I use the tool at crucial.com which is very accurate and also very
|
|
|
|
|
complete in terms of all possible hardware out there.
|
|
|
|
|
|
|
|
|
|
I would trust that tool before trusting the companies that have the least reliable data, like ASUS.
|
|
|
|
|
|
|
|
|
|
Much thanks to everyone who is contributing datasets, and the distros, particularly siduction, that really
|
|
|
|
|
were very helpful in this process, by finding more and more failure cases that helped me start to tighten
|
|
|
|
|
the logic, and make it more and more robust. Special thanks to Mikaela, of #smxi irc.oftc.net, who came up
|
|
|
|
|
with two systems that both required a full redo of the logic, and thus who helped a lot in this process.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 18 Aug 2014 15:07:36 -0700
|
|
|
|
|
|
2014-08-18 02:42:43 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.98
|
|
|
|
|
Patch Version: 01
|
|
|
|
|
Script Date: 2014-08-17
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New patch version, new tarball. Another error case dataset, wrong cap, wrong max mod
|
|
|
|
|
size, derived mod size 2gb, listed cap 8, but 2 slots, ie, 2gb x 2 == 4. Made this
|
|
|
|
|
retain the listed size, but adds (check) to it because either max mod size is wrong
|
|
|
|
|
or cap is wrong.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 17 Aug 2014 19:40:46 -0700
|
|
|
|
|
|
2014-08-16 23:24:08 +00:00
|
|
|
=====================================================================================
|
2014-08-17 19:04:20 +00:00
|
|
|
Version: 2.1.98
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-17
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixed bad assumption, DMI type 0 is not always before other
|
|
|
|
|
types, in at least one case, it is last, so can't use that as trigger to start loop.
|
|
|
|
|
|
|
|
|
|
Now using: Table at .. which is always at start of dmi output.
|
|
|
|
|
|
|
|
|
|
Also, changed size output per module to be in MB GB TB instead of all mB, since modules
|
|
|
|
|
are sold by GB or MB, the data should show that as well. Also shortens output.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 17 Aug 2014 12:01:38 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-08-16 23:24:08 +00:00
|
|
|
Version: 2.1.97
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-16
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Another logic redo to handle a fringe case (dmidecode places
|
|
|
|
|
type 17 in front of type 16), now each array is created as a multidimenstional, 2x array,
|
|
|
|
|
and each device is a 3 dimensional array. This seems to clean up the problems with bad
|
|
|
|
|
ordering of dmidecode data.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 16 Aug 2014 16:22:17 -0700
|
|
|
|
|
|
2014-08-15 23:55:27 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.96
|
|
|
|
|
Patch Version: 02
|
|
|
|
|
Script Date: 2014-08-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
forgot to remove debugger on switch
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 15 Aug 2014 16:55:04 -0700
|
|
|
|
|
|
2014-08-15 23:44:32 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.96
|
|
|
|
|
Patch Version: 01
|
|
|
|
|
Script Date: 2014-08-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Small change, forgot to add -m to the debugger inxi output.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 15 Aug 2014 16:43:47 -0700
|
|
|
|
|
|
New version, new tarball, new man page. This version hopefully brings inxi closer to
at least making good guesses when the data is bad for ram, and hopefully will not break
too many cases where it was actually right but seemed wrong.
Unfortunately, dmidecode data simply cannot be relied on, and is FAR inferior to the type
of data inxi tries in general to present users, ie, taken directly from the system, and,
ideally, more accurate than most other tools. But in this case, there is just no way to get
the data truly accurate no matter how many hacks I add.
But if you have bad data, then submit: inxi -xx@ 14 so I can take a look at the system,
and see if I can modify the hacks to improve that data.
2014-08-15 00:44:47 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.96
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. This version hopefully brings inxi closer to
|
|
|
|
|
at least making good guesses when the data is bad for ram, and hopefully will not break
|
|
|
|
|
too many cases where it was actually right but seemed wrong.
|
|
|
|
|
|
|
|
|
|
Unfortunately, dmidecode data simply cannot be relied on, and is FAR inferior to the type
|
|
|
|
|
of data inxi tries in general to present users, ie, taken directly from the system, and,
|
|
|
|
|
ideally, more accurate than most other tools. But in this case, there is just no way to get
|
|
|
|
|
the data truly accurate no matter how many hacks I add.
|
|
|
|
|
|
|
|
|
|
But if you have bad data, then submit: inxi -xx@ 14 so I can take a look at the system,
|
|
|
|
|
and see if I can modify the hacks to improve that data.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 14 Aug 2014 17:41:42 -0700
|
|
|
|
|
|
2014-08-14 19:24:51 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.95
|
|
|
|
|
Patch Version: 04
|
|
|
|
|
Script Date: 2014-08-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New patch version, tarball. Fixed a few small oversights, more debugging added.
|
|
|
|
|
|
|
|
|
|
Will next try to handle the remaining corner cases if possible.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 14 Aug 2014 12:23:38 -0700
|
|
|
|
|
|
2014-08-14 04:30:22 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.95
|
|
|
|
|
Patch Version: 01
|
|
|
|
|
Script Date: 2014-08-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
patch version, trying to fix a small glitch with gawk wanting to change integers to strings.
|
|
|
|
|
|
|
|
|
|
forcing int() on relevant items.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 13 Aug 2014 21:28:46 -0700
|
|
|
|
|
|
2014-08-14 03:45:14 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.95
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Attempting to handle bad extra data for max module size, sometimes
|
|
|
|
|
it is too big, and sometimes too small. Changed data gathering to use arrays, then print/process
|
|
|
|
|
the arrays once they are assembled.
|
|
|
|
|
|
|
|
|
|
Now it will get rid of any max module size if it's greater than the calculated capacity, and it
|
|
|
|
|
will generate an estimated capacity/max module size if they are clearly wrong because actual
|
|
|
|
|
module sizes are greater than listed max size, or capacity is less than greatest module sizes times
|
|
|
|
|
number of devices.
|
|
|
|
|
|
|
|
|
|
Not perfect, but it never is, this covers more cases now correctly than before.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 13 Aug 2014 20:42:00 -0700
|
|
|
|
|
|
2014-08-13 21:05:21 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.94
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new man page, new tarball. Realized that I can on some systems also add
|
|
|
|
|
maximum supported module size, and module voltage. Most systems do not have this data,
|
|
|
|
|
but some do. It's Type 5 item in dmidecode.
|
|
|
|
|
|
|
|
|
|
Getting the type 6 data however is too hard, and even using type 5 assumes that the
|
|
|
|
|
system only has one physical memory array, but that's fine given how few systems
|
|
|
|
|
probably will have this information in the first place.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 13 Aug 2014 14:03:03 -0700
|
|
|
|
|
|
2014-08-13 03:19:55 +00:00
|
|
|
=====================================================================================
|
New version, new man page. Fixed man page errors, improved man page explanations of -m
features. Changed output syntax to be more consistent, now each main array line starts with:
Array-X capacity: (where X is an integer, counting from 1)
and each device line starts with:
Device-X: (where X is an integer incremented by 1 for each device, and starting at 1
for each array. I have no data sets that contain > 1 physical memory array, if one appears,
I may need to patch the output to link the array handles with the device handles explicitly.
Made memory bus width output more clear, and added in a hack to correct dmidecode output errors,
sometimes total width > data width, and sometimes data width is > total width, so using always
greatest value for total if not equal to other width.
I think this will be close to it barring any user feedback or bugs, if nothing comes to
mind within a few days, I'll move the number to the new major version, 2.2.0
2014-08-13 19:17:21 +00:00
|
|
|
Version: 2.1.93
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new man page. Fixed man page errors, improved man page explanations of -m
|
|
|
|
|
features. Changed output syntax to be more consistent, now each main array line starts with:
|
|
|
|
|
|
|
|
|
|
Array-X capacity: (where X is an integer, counting from 1)
|
|
|
|
|
|
|
|
|
|
and each device line starts with:
|
|
|
|
|
Device-X: (where X is an integer incremented by 1 for each device, and starting at 1
|
|
|
|
|
for each array. I have no data sets that contain > 1 physical memory array, if one appears,
|
|
|
|
|
I may need to patch the output to link the array handles with the device handles explicitly.
|
|
|
|
|
|
|
|
|
|
Made memory bus width output more clear, and added in a hack to correct dmidecode output errors,
|
|
|
|
|
sometimes total width > data width, and sometimes data width is > total width, so using always
|
|
|
|
|
greatest value for total if not equal to other width.
|
|
|
|
|
|
|
|
|
|
I think this will be close to it barring any user feedback or bugs, if nothing comes to
|
|
|
|
|
mind within a few days, I'll move the number to the new major version, 2.2.0
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 13 Aug 2014 12:12:23 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-08-13 03:19:55 +00:00
|
|
|
Version: 2.1.92
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-12
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This is closer to final release. Removed Bank/Slot separate
|
|
|
|
|
items and am now just generating one: Locator item, usually from Slot/DIMM locator info,
|
|
|
|
|
but sometimes from Bank Locator info when it is more reliable based on my data samples.
|
|
|
|
|
|
|
|
|
|
Updated help menu, updated man page, now shows working -x -xx -xxx extra data. This may
|
|
|
|
|
change slightly over time.
|
|
|
|
|
|
|
|
|
|
Also removed speed output when No Module Installed is returned for device size. This
|
|
|
|
|
also wills switch off width if both total/data are empty.
|
|
|
|
|
|
|
|
|
|
This is much closer now to live 2.2.0, but I'll leave a few more tests before putting
|
|
|
|
|
it at 2.2.0.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 12 Aug 2014 20:16:04 -0700
|
|
|
|
|
|
2014-08-13 01:13:10 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.91
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-12
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This is a transitional version, most -x/-xx/-xxx data is now
|
|
|
|
|
working, but help/man does not have that yet, until I finalize the order.
|
|
|
|
|
|
|
|
|
|
Fixed dmidecode issues, showing extra data types for -m, added line length handling
|
|
|
|
|
so -m is properly integrated with rest of inxi re max line lengths.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 12 Aug 2014 18:11:29 -0700
|
|
|
|
|
|
New version, new tarball, new man page. Finally, after all these years, initial memory/ram
support. This feature requires dmidecode, and usually that needs to be run as root.
Significantly improved dmidecode error handling and output, and have as 2.1.90 testing/initial
release basic ram data.
In subsequent releases, extra info for -x and -xx and -xxx will be added as well to the output.
For those who want to jump on board early for ram data, update your repos, for those who want to
wait for the full featured version, with -x type data, wait for 2.2.0
And that's that.
2014-08-12 05:26:35 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.90
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-11
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. Finally, after all these years, initial memory/ram
|
|
|
|
|
support. This feature requires dmidecode, and usually that needs to be run as root.
|
|
|
|
|
|
|
|
|
|
Significantly improved dmidecode error handling and output, and have as 2.1.90 testing/initial
|
|
|
|
|
release basic ram data.
|
|
|
|
|
|
|
|
|
|
In subsequent releases, extra info for -x and -xx and -xxx will be added as well to the output.
|
|
|
|
|
|
|
|
|
|
For those who want to jump on board early for ram data, update your repos, for those who want to
|
|
|
|
|
wait for the full featured version, with -x type data, wait for 2.2.0
|
|
|
|
|
|
|
|
|
|
And that's that.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 11 Aug 2014 22:23:18 -0700
|
|
|
|
|
|
2014-08-08 17:20:55 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.29
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-08
|
2014-08-11 23:11:40 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change, this only will impact ancient systems, cleans up a data error message
|
|
|
|
|
and restores N/A to IF id in networking. No functional change, and won't be seen on any
|
|
|
|
|
non ancient systems.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 11 Aug 2014 16:10:03 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.29
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-08-08
|
2014-08-08 17:20:55 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Big update/fix to -n/-i/-N. Now supports infiniband devices, which
|
|
|
|
|
have the odd feature in our test data of having > 1 IF id, like ib0 ib1 per pcibusid.
|
|
|
|
|
|
|
|
|
|
Added support for virtual nics as well. This required refactoring the networking functions
|
|
|
|
|
significantly, so hopefully nothing breaks for existing systems. It should in theory be more
|
|
|
|
|
robust now than it was before, with more accurate output, particularly with multiple port
|
|
|
|
|
devices, like two port nics etc.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 08 Aug 2014 10:17:52 -0700
|
|
|
|
|
|
2014-05-05 19:13:08 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.28
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-05-05
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, new tarball. Adding tentative desktop id for LXQt, but I don't think
|
|
|
|
|
that this method will be super long lived, I expect LXDE to change how it shows itself
|
|
|
|
|
to the system when the gtk variant goes away. Good for lxde by the way in dumping gtk.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 05 May 2014 12:11:27 -0700
|
|
|
|
|
|
2014-05-01 20:34:08 +00:00
|
|
|
=====================================================================================
|
New version, new tarball. Should be almost no changes for linux platforms, though I
added in an abstracted kernel_compiler method, not just gcc, that may work on freebsd,
and in the future, it may also work if distros or kernel people start using either
clang or LLVM-GCC or LLVM for compiling linux kernels. I'd need some data sets to
show that however before adding that full linux kernel support, but the framework
is now there.
That continues the abstraction of certain features, like kernel compiler, init system,
display server. Display server still needs full data sets from mir/wayland, at least
wayland, and the bsd display servers as well, I have no idea how to get that data
at this point, but the starting framework is present anyway for that time I get
those datasets.
Almost all these changes are for darwin osx, and that is about all I will do for that
junky broken platform, they have no tools, they have no discipline when it comes to
following unix like conventions, they even use spaces in program names, like windows.
Given it has no native lspci or pciconf tool that I am aware of, or dmesg.boot,
there's little point in putting more time into it. dmidecode does not run on darwin,
so there's nothing to learn there either, you can get a silly 3rd party program to
generate a dmidecode.bin data file that dmidecode can then read, but since that
requires not one, but two third party programs be installed, that's not going to
happen.
Next time an osx user calls this system 'unix' I will laugh.
2014-05-02 19:51:59 +00:00
|
|
|
Version: 2.1.27
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-05-02
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Should be almost no changes for linux platforms, though I
|
|
|
|
|
added in an abstracted kernel_compiler method, not just gcc, that may work on freebsd,
|
|
|
|
|
and in the future, it may also work if distros or kernel people start using either
|
|
|
|
|
clang or LLVM-GCC or LLVM for compiling linux kernels. I'd need some data sets to
|
|
|
|
|
show that however before adding that full linux kernel support, but the framework
|
|
|
|
|
is now there.
|
|
|
|
|
|
|
|
|
|
That continues the abstraction of certain features, like kernel compiler, init system,
|
|
|
|
|
display server. Display server still needs full data sets from mir/wayland, at least
|
|
|
|
|
wayland, and the bsd display servers as well, I have no idea how to get that data
|
|
|
|
|
at this point, but the starting framework is present anyway for that time I get
|
|
|
|
|
those datasets.
|
|
|
|
|
|
|
|
|
|
Almost all these changes are for darwin osx, and that is about all I will do for that
|
|
|
|
|
junky broken platform, they have no tools, they have no discipline when it comes to
|
|
|
|
|
following unix like conventions, they even use spaces in program names, like windows.
|
|
|
|
|
|
|
|
|
|
Given it has no native lspci or pciconf tool that I am aware of, or dmesg.boot,
|
|
|
|
|
there's little point in putting more time into it. dmidecode does not run on darwin,
|
|
|
|
|
so there's nothing to learn there either, you can get a silly 3rd party program to
|
|
|
|
|
generate a dmidecode.bin data file that dmidecode can then read, but since that
|
|
|
|
|
requires not one, but two third party programs be installed, that's not going to
|
|
|
|
|
happen.
|
|
|
|
|
|
|
|
|
|
Next time an osx user calls this system 'unix' I will laugh.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 02 May 2014 12:44:38 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-05-01 20:34:08 +00:00
|
|
|
Version: 2.1.26
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-05-01
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Maintainer: this is only for bsd darwin (aka osx, it's an
|
|
|
|
|
experiment, just to get it running, so you can all ignore this release.
|
|
|
|
|
|
|
|
|
|
Added in darwin cpu, init, distro version support, and updated inxi to support
|
|
|
|
|
darwin/osx without exiting.
|
|
|
|
|
|
|
|
|
|
No linux changes.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 01 May 2014 13:32:21 -0700
|
|
|
|
|
|
2014-04-28 21:48:32 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.25
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
no version change, new tarball. On consideration, I'm not using temp3, that is simply
|
|
|
|
|
not reliable enough and leads I think to more false readings than right ones.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Apr 2014 14:47:41 -0700
|
|
|
|
|
|
2014-04-28 21:25:22 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.25
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This fixes a possible bug with using --total to calculate disk
|
|
|
|
|
used percentage, there are too many possible remote file systems to safely exclude, so
|
|
|
|
|
sticking with using the test that partition is /dev mounted.
|
|
|
|
|
|
|
|
|
|
Howeve, did add excludes of nfs/smbfs types, as well as future bsd excludes of those.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Apr 2014 14:23:39 -0700
|
|
|
|
|
|
2014-04-28 21:14:08 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.24
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Quick fix, new tarball, no new version. This fixes a -D size used error, if nfs, nfs4, smbfs
|
|
|
|
|
are mounted, inxi included those in the disk space used, creating insane used errors.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Apr 2014 14:12:50 -0700
|
|
|
|
|
|
2014-04-28 20:37:20 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.24
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-28
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This is an attempt to make -s accurate more of the time,
|
|
|
|
|
particularly with fringe or broken sensors outputs. See inxi issue 58 for details.
|
|
|
|
|
http://code.google.com/p/inxi/issues/detail?id=58
|
|
|
|
|
|
|
|
|
|
Added temp3, and an override to capture cases where temp3 is the actual cpu temp.
|
|
|
|
|
|
|
|
|
|
Added PECI overrides for cases like msi/asus mobos have defective CPUTIN return data.
|
|
|
|
|
|
|
|
|
|
Added core0 overrides as well, for cases where the temp returned is too low.
|
|
|
|
|
|
|
|
|
|
It is absolutely 100% guaranteed that these changes will break some outputs that were
|
|
|
|
|
working, but it's also certain that I believe that more wrong outputs will be corrected.
|
|
|
|
|
|
|
|
|
|
With sensors, really the only way you can get reliable sensors is to use the lm-sensors
|
|
|
|
|
config files for your motherboard, then set: CPU: temp and MB: temp explicitly.
|
|
|
|
|
|
|
|
|
|
inxi will always use CPU: or MB: to override anything found.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Apr 2014 13:17:53 -0700
|
|
|
|
|
|
2014-04-27 22:57:24 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.23
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-27
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man. Found a pesky bug with false disk used results.
|
|
|
|
|
|
|
|
|
|
It turns out I'd neglected to include /dev/disk partitions, oops, in the df data.
|
|
|
|
|
|
|
|
|
|
Since this is a long time bug, it warrants a new release even though I just did
|
|
|
|
|
2.1.22.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 27 Apr 2014 15:55:20 -0700
|
|
|
|
|
|
2014-04-27 21:42:30 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.22
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-27
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Quick update to -D, now inxi uses the total partition swap space to calculate the
|
|
|
|
|
disk used percentage as well. Since swap space is not available as disk space, it
|
|
|
|
|
makes sense to me to count it as used. -P/-p show the percent of swap used as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 27 Apr 2014 14:41:06 -0700
|
|
|
|
|
|
New version, new tarball. A bug fix for btrfs, which does not internally use /dev/sdx[number]
to identify a partition, but rather the basic /dev/sdc for example.
This made -D show wrong disk used percentage.
Also, I added --total for df that have that supported, there is however an oddity which you
can see here:
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
awk 'BEGIN {total=0} !/total/ {total = total + $4 }END {print total}'
result:
614562236
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
awk 'BEGIN {total=0} /^total/ {total = total + $4 }END {print total}'
result:
614562228
df -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
awk 'BEGIN {total=0} {total = total + $4 }END {print total}'
result:
614562236
In my tests, using --total gives a greater disk user percentage than adding the results
up manually, as inxi did before, and still does for systems without --total for df.
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs \
--exclude-type=procfs --exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs \
--exclude-type=unionfs
Filesystem Type 1024-blocks Used Available Capacity Mounted on
/dev/disk/by-label/root-data ext3 12479556 12015624 335816 98% /
/dev/sdc9 ext3 20410156 18013360 1979432 91% /home
/dev/sdc7 ext3 4904448 3785460 1016672 79% /media/sdb2
/dev/sdc5 ext3 30382896 27467220 2295720 93% /var/www/m
/dev/sdc8 ext3 61294356 41849300 18196972 70% /home/me/1
/dev/sdb1 ext3 307532728 285159432 20810456 94% /home/me/2
/dev/sdd1 ext3 26789720 18153076 7542620 71% /home/me/3
/dev/sdd2 ext3 213310776 206932912 2040960 100% /home/me/4
/dev/sda7 ext3 10138204 1185772 8434348 13% /home/me/5
total - 687242840 614562156 62652996 91% -
Strange, no? the data is in blocks, and it should of course in theory add up to exactly the
same thing. However, because --total lets df do the math, I'm going to use that for now,
unless someone can show it's not good.
inxi still falls back for bsds and older df to the standard method.
2014-04-27 20:01:35 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.22
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-27
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. A bug fix for btrfs, which does not internally use /dev/sdx[number]
|
|
|
|
|
to identify a partition, but rather the basic /dev/sdc for example.
|
|
|
|
|
|
|
|
|
|
This made -D show wrong disk used percentage.
|
|
|
|
|
|
|
|
|
|
Also, I added --total for df that have that supported, there is however an oddity which you
|
|
|
|
|
can see here:
|
|
|
|
|
|
|
|
|
|
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
|
|
|
|
|
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
|
|
|
|
|
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
|
|
|
|
|
awk 'BEGIN {total=0} !/total/ {total = total + $4 }END {print total}'
|
|
|
|
|
result:
|
|
|
|
|
614562236
|
|
|
|
|
|
|
|
|
|
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
|
|
|
|
|
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
|
|
|
|
|
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
|
|
|
|
|
awk 'BEGIN {total=0} /^total/ {total = total + $4 }END {print total}'
|
|
|
|
|
|
|
|
|
|
result:
|
|
|
|
|
614562228
|
|
|
|
|
|
|
|
|
|
df -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
|
|
|
|
|
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs --exclude-type=procfs \
|
|
|
|
|
--exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs --exclude-type=unionfs | \
|
|
|
|
|
awk 'BEGIN {total=0} {total = total + $4 }END {print total}'
|
|
|
|
|
|
|
|
|
|
result:
|
|
|
|
|
614562236
|
|
|
|
|
|
|
|
|
|
In my tests, using --total gives a greater disk user percentage than adding the results
|
|
|
|
|
up manually, as inxi did before, and still does for systems without --total for df.
|
|
|
|
|
|
|
|
|
|
df --total -P -T --exclude-type=aufs --exclude-type=devfs --exclude-type=devtmpfs \
|
|
|
|
|
--exclude-type=fdescfs --exclude-type=iso9660 --exclude-type=linprocfs \
|
|
|
|
|
--exclude-type=procfs --exclude-type=squashfs --exclude-type=sysfs --exclude-type=tmpfs \
|
|
|
|
|
--exclude-type=unionfs
|
|
|
|
|
|
|
|
|
|
Filesystem Type 1024-blocks Used Available Capacity Mounted on
|
|
|
|
|
/dev/disk/by-label/root-data ext3 12479556 12015624 335816 98% /
|
|
|
|
|
/dev/sdc9 ext3 20410156 18013360 1979432 91% /home
|
|
|
|
|
/dev/sdc7 ext3 4904448 3785460 1016672 79% /media/sdb2
|
|
|
|
|
/dev/sdc5 ext3 30382896 27467220 2295720 93% /var/www/m
|
|
|
|
|
/dev/sdc8 ext3 61294356 41849300 18196972 70% /home/me/1
|
|
|
|
|
/dev/sdb1 ext3 307532728 285159432 20810456 94% /home/me/2
|
|
|
|
|
/dev/sdd1 ext3 26789720 18153076 7542620 71% /home/me/3
|
|
|
|
|
/dev/sdd2 ext3 213310776 206932912 2040960 100% /home/me/4
|
|
|
|
|
/dev/sda7 ext3 10138204 1185772 8434348 13% /home/me/5
|
|
|
|
|
total - 687242840 614562156 62652996 91% -
|
|
|
|
|
|
|
|
|
|
Strange, no? the data is in blocks, and it should of course in theory add up to exactly the
|
|
|
|
|
same thing. However, because --total lets df do the math, I'm going to use that for now,
|
|
|
|
|
unless someone can show it's not good.
|
|
|
|
|
|
|
|
|
|
inxi still falls back for bsds and older df to the standard method.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 27 Apr 2014 12:49:06 -0700
|
|
|
|
|
|
2014-04-24 20:24:12 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.21
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New tarball, small update, added hopefully firewire support to drive type id.
|
|
|
|
|
|
|
|
|
|
That's searching for ieee1394- hopefully that will do it.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 24 Apr 2014 13:22:51 -0700
|
|
|
|
|
|
2014-04-24 18:56:23 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.21
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This fixes one small oversight, placing USB in front of ID-[x]
|
|
|
|
|
of disk drive lists. Was showing USB ID-1: /dev/sde now shows: ID-1: USB /dev/sde
|
|
|
|
|
that is more intuitive and keeps the columns in alignment more or less, easier
|
|
|
|
|
to read.
|
|
|
|
|
|
|
|
|
|
Second, fixes a bug with some file systems / usb drives
|
|
|
|
|
where they do not use usb- in the /dev/disk/by-id line but only wwn-
|
|
|
|
|
https://access.redhat.com/site/documentation/en
|
|
|
|
|
-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/persistent_naming.html
|
|
|
|
|
explains it somewhat.
|
|
|
|
|
|
|
|
|
|
the fix is adding a second if null test of the device /dev/sdx in by-path, that seems
|
|
|
|
|
to fix the issue. by-path does have the usb- item, though it does not have the name
|
|
|
|
|
so it's not as reliable in absolute terms, but it's fine as a second step fallback
|
|
|
|
|
option.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 24 Apr 2014 11:47:08 -0700
|
|
|
|
|
|
While this release has some new features, they are all intended for development use
for the next major feature, -m / memory, so there is no particular reason to package
this release. There is a new development option, -! 33, which lets me override /sys
data use for -M, which is useful to debug dmidecode output for -m and other features.
No new version, new man. There may be a few more of these releases, but functionally
there is no particular reason to make a new package if you are a maintainer, so there
is no new version number. This release is a preparation for some branches/one/inxi
tests that will be run in the future.
The man/help document -! 33 just to have it there, but it should make no difference
to anyone but me at this stage.
2014-04-14 20:35:38 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.20
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
While this release has some new features, they are all intended for development use
|
|
|
|
|
for the next major feature, -m / memory, so there is no particular reason to package
|
|
|
|
|
this release. There is a new development option, -! 33, which lets me override /sys
|
|
|
|
|
data use for -M, which is useful to debug dmidecode output for -m and other features.
|
|
|
|
|
|
|
|
|
|
No new version, new man. There may be a few more of these releases, but functionally
|
|
|
|
|
there is no particular reason to make a new package if you are a maintainer, so there
|
|
|
|
|
is no new version number. This release is a preparation for some branches/one/inxi
|
|
|
|
|
tests that will be run in the future.
|
|
|
|
|
|
|
|
|
|
The man/help document -! 33 just to have it there, but it should make no difference
|
|
|
|
|
to anyone but me at this stage.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 14 Apr 2014 13:31:24 -0700
|
|
|
|
|
|
2014-04-09 00:17:54 +00:00
|
|
|
=====================================================================================
|
2014-04-09 07:11:43 +00:00
|
|
|
Version: 2.1.20
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
A few fixes to 2.1.20, bmips broke in some cases, that's fixed now. Also changed the
|
|
|
|
|
way to handle bad ARM data, when bogomips are too low, < 50, we try to get the data
|
|
|
|
|
from /sys, but now this runs on all the cores, so it may work as well on the multicore
|
|
|
|
|
arm if the /proc/cpuinfo has bogomip that is too low and no cpu frequency.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 09 Apr 2014 00:09:49 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-04-09 00:17:54 +00:00
|
|
|
Version: 2.1.20
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-08
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, ARM cpu /proc/cpuinfo has broken the bogomips output, since this
|
|
|
|
|
is an upstream bug, I'm adding in a quick hack that will work maybe for single core
|
|
|
|
|
ARM cpus, but NOT for multicores that have the same issue.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 08 Apr 2014 17:15:41 -0700
|
|
|
|
|
|
New version/tarball. This completes, I think, the line wrap update. -o is now handled,
unmounted drives.
IMPORTANT: some distros use inxi for detecting partitions, the syntax on the following
have changed slightly:
HDD: per drive changes from: 1: id: to ID-1:
Partitions: per partition changes from ID: to ID-1:
Unmounted partitions: per unmounted changes from ID: to ID-1
You see the pattern, they are all the same now, and they are all numbered. I think this
is easier to read when scanning long lines of drives/partitions, or even short ones.
Also fixed a long standing oddity, not a bug, but for some weird reason, -p did not
include the location, like /dev/sda1, unless -l or -u were used. That makes no sense
so I have moved the dev/remote location output to standard -p/-P
Except for bug fixes, this completes the overally line wrap update, all lines wrap,
you can set widths with -y now, and the old issue of not fitting nicely into 80 column
wide widths is solved. Note that in some areas, p/P for example, at times if the mount
point or remote location is very long the line may still wrap, but making this perfect
is too convoluted so I'm calling it good enough now, all lines are handled reasonably well,
certainly radically better than before 2.1.0.
2014-04-04 18:16:45 +00:00
|
|
|
=====================================================================================
|
2014-04-06 21:35:15 +00:00
|
|
|
Version: 2.1.19
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-06
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball, correction of loop counts for -p/-P ID-<number>, this requires
|
|
|
|
|
a third counter to get all the stuff right. Sorry about the extra release, that's life.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 06 Apr 2014 14:33:46 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
New version/tarball. This completes, I think, the line wrap update. -o is now handled,
unmounted drives.
IMPORTANT: some distros use inxi for detecting partitions, the syntax on the following
have changed slightly:
HDD: per drive changes from: 1: id: to ID-1:
Partitions: per partition changes from ID: to ID-1:
Unmounted partitions: per unmounted changes from ID: to ID-1
You see the pattern, they are all the same now, and they are all numbered. I think this
is easier to read when scanning long lines of drives/partitions, or even short ones.
Also fixed a long standing oddity, not a bug, but for some weird reason, -p did not
include the location, like /dev/sda1, unless -l or -u were used. That makes no sense
so I have moved the dev/remote location output to standard -p/-P
Except for bug fixes, this completes the overally line wrap update, all lines wrap,
you can set widths with -y now, and the old issue of not fitting nicely into 80 column
wide widths is solved. Note that in some areas, p/P for example, at times if the mount
point or remote location is very long the line may still wrap, but making this perfect
is too convoluted so I'm calling it good enough now, all lines are handled reasonably well,
certainly radically better than before 2.1.0.
2014-04-04 18:16:45 +00:00
|
|
|
Version: 2.1.18
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-04
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version/tarball. This completes, I think, the line wrap update. -o is now handled,
|
|
|
|
|
unmounted drives.
|
|
|
|
|
|
|
|
|
|
IMPORTANT: some distros use inxi for detecting partitions, the syntax on the following
|
|
|
|
|
have changed slightly:
|
|
|
|
|
|
|
|
|
|
HDD: per drive changes from: 1: id: to ID-1:
|
|
|
|
|
Partitions: per partition changes from ID: to ID-1:
|
|
|
|
|
Unmounted partitions: per unmounted changes from ID: to ID-1
|
|
|
|
|
|
|
|
|
|
You see the pattern, they are all the same now, and they are all numbered. I think this
|
|
|
|
|
is easier to read when scanning long lines of drives/partitions, or even short ones.
|
|
|
|
|
|
|
|
|
|
Also fixed a long standing oddity, not a bug, but for some weird reason, -p did not
|
|
|
|
|
include the location, like /dev/sda1, unless -l or -u were used. That makes no sense
|
|
|
|
|
so I have moved the dev/remote location output to standard -p/-P
|
|
|
|
|
|
|
|
|
|
Except for bug fixes, this completes the overally line wrap update, all lines wrap,
|
|
|
|
|
you can set widths with -y now, and the old issue of not fitting nicely into 80 column
|
|
|
|
|
wide widths is solved. Note that in some areas, p/P for example, at times if the mount
|
|
|
|
|
point or remote location is very long the line may still wrap, but making this perfect
|
|
|
|
|
is too convoluted so I'm calling it good enough now, all lines are handled reasonably well,
|
|
|
|
|
certainly radically better than before 2.1.0.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 04 Apr 2014 11:08:25 -0700
|
|
|
|
|
|
2014-04-03 17:46:31 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.17
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-03
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new man page, new tarball. Added -y [integer >= 80] option. This allows for absolute override
|
|
|
|
|
of width settings. This overrides any dynamically detected widths, as well as the globals:
|
|
|
|
|
COLS_MAX_CONSOLE='115'
|
|
|
|
|
COLS_MAX_IRC='105'
|
|
|
|
|
Now that inxi widths are largely dynamic in terminal, with a few lingering exceptions, it made sense
|
|
|
|
|
to also allow for overrides of this. This is useful in cases where for example you want to output
|
|
|
|
|
inxi to text file or for other purposes, or if you just want to test the widths, as in my case.
|
|
|
|
|
|
|
|
|
|
-y cannot be used with --recommends, but otherwise it works fine, with --help/-c 94-99 you have to
|
|
|
|
|
put -y first in the list of options.
|
|
|
|
|
|
|
|
|
|
Example: inxi -v7 -y150 > inxi.txt will ignore the terminal settings and output the lines at basically
|
|
|
|
|
max length.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 03 Apr 2014 10:41:07 -0700
|
|
|
|
|
|
2014-04-03 04:30:30 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.16
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-02
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. This fix only impacts bsd sed, but it fixes the line length failure
|
|
|
|
|
issue because bsd sed doesn't work with \x1b, but it does when you do:
|
|
|
|
|
ESC=$(echo | tr '\n' '\033' )
|
|
|
|
|
I found this trick on:
|
|
|
|
|
http://unix.stackexchange.com/questions/42321/how-can-i-instruct-bsd-sed-to-interpret-escape-sequences-like-n-and-t
|
|
|
|
|
|
|
|
|
|
No other changes. Non bsd users, you can ignore this.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 02 Apr 2014 21:24:52 -0700
|
|
|
|
|
|
2014-04-01 01:11:08 +00:00
|
|
|
=====================================================================================
|
2014-04-01 21:02:47 +00:00
|
|
|
Version: 2.1.15
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-04-01
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version/tarball. This corrects some subtle issues with line wraps:
|
|
|
|
|
|
|
|
|
|
Audio -A - now wrap is fully dynamic down to 80 characters, and also the expansion of ALSA
|
|
|
|
|
to Advanced Linux Sound System only happens if that fits in the display width.
|
|
|
|
|
|
|
|
|
|
-N/-n/-i - Most networking/ip address stuff wraps now.
|
|
|
|
|
|
|
|
|
|
-d - optical drive data wraps better now too.
|
|
|
|
|
|
|
|
|
|
This more or less completes the line wrap redo.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 01 Apr 2014 12:39:44 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-04-01 01:11:08 +00:00
|
|
|
Version: 2.1.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-31
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Forgot, added slitaz-release to distros derived. that's as slackware derived one.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 31 Mar 2014 18:10:02 -0700
|
|
|
|
|
|
new version/tarball. Tiny fix in debugger, it turns out that in some systems, the command:
strings --version used in the debugger results in a hang, which you can duplicate with:
strings
alone, without any argument or info, that will hang too, so I assume if the system doesn't
have the --version parameter, strings ignores that, and basically just does what it would do
with no option, hang.
Thanks for user ypharis persistence in tracking down this issue. So far only appeared on slackware
based distros, but since the debugger should 'just work', removing the version test.
2014-04-01 00:52:57 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-31
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version/tarball. Tiny fix in debugger, it turns out that in some systems, the command:
|
|
|
|
|
strings --version used in the debugger results in a hang, which you can duplicate with:
|
|
|
|
|
strings
|
|
|
|
|
alone, without any argument or info, that will hang too, so I assume if the system doesn't
|
|
|
|
|
have the --version parameter, strings ignores that, and basically just does what it would do
|
|
|
|
|
with no option, hang.
|
|
|
|
|
|
|
|
|
|
Thanks for user ypharis persistence in tracking down this issue. So far only appeared on slackware
|
|
|
|
|
based distros, but since the debugger should 'just work', removing the version test.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 31 Mar 2014 17:49:48 -0700
|
|
|
|
|
|
2014-03-30 18:55:38 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.13
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-30
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, only relevant to Porteus distro, a slackware derived distro, should now id it
|
|
|
|
|
correctly. No other changes.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 30 Mar 2014 11:54:12 -0700
|
|
|
|
|
|
2014-03-27 22:35:17 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-27
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, fixed zfs raid failure to report raid devices on some systems. Added wrapping
|
|
|
|
|
for -D disk option. Note that -d is not correctly wrapping because the lines are too long with
|
|
|
|
|
extra data, but it's ok for now.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 27 Mar 2014 15:33:33 -0700
|
|
|
|
|
|
2014-03-26 22:29:44 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.11
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-26
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Ignore change 2.1.12, the speed data was too inconsistent, using >>> since it's cleaner
|
|
|
|
|
and seems to be faster on some cpus, slower on others.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 26 Mar 2014 15:28:08 -0700
|
|
|
|
|
|
2014-03-26 21:57:03 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-26
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version: this is only an optimization release, testing some slightly more efficient
|
|
|
|
|
methods:
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
something <<< $variable is signficantly slower than: echo $variable | something
|
2014-03-26 21:57:03 +00:00
|
|
|
so I replaced almost all instances of <<< with echo ...|
|
|
|
|
|
|
|
|
|
|
I've seen speed differences of up to 10% but it's not consistent, so this is just
|
|
|
|
|
something to boost performance slightly on older systems I'd guess.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 26 Mar 2014 14:54:39 -0700
|
|
|
|
|
|
2014-03-26 19:46:58 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.11
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-26
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version: fixed an old bug, with -c 0, no colors, RED and NORMAL color codes were
|
|
|
|
|
not set to null, which results in some cases with red output, along with turning
|
|
|
|
|
terminal/console font color red.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 26 Mar 2014 12:44:53 -0700
|
|
|
|
|
|
2014-03-25 20:56:58 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.10
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-25
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version; added supybot/limnoria/gribble support. This only works when the supybot
|
|
|
|
|
'SHELL' command is used, 'CALL' gives the user irc client data, and supybot etc are
|
|
|
|
|
not detectable.
|
|
|
|
|
|
|
|
|
|
Fine tuned some error message lengths so they fit into 80 columns or so.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 25 Mar 2014 13:55:13 -0700
|
|
|
|
|
|
2014-03-25 01:43:30 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.9
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, fixed cpu core speed wrapping, improved -p and -P wrapping, though some lines
|
|
|
|
|
will still be too long, but not as many.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 24 Mar 2014 18:42:06 -0700
|
|
|
|
|
|
2014-03-25 00:01:20 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.8
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-24
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version. Added dynamic wrapping to -G, and also am now wrapping -C per cpu cores speeds,
|
|
|
|
|
for systems with a lot of them, that will clean up the output.
|
|
|
|
|
|
|
|
|
|
Added dynamic wrapping to --recommends and -c 94-99.
|
|
|
|
|
|
|
|
|
|
These are the main things, there's a few smaller issues with -xx output on -N/-n/-i but
|
|
|
|
|
those will noly really show with full output and it takes a while to get this stuff stable
|
|
|
|
|
so maybe some other time, but it's ok for now.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 24 Mar 2014 16:58:33 -0700
|
|
|
|
|
|
new version, attempt 2 at detecting all possible syntaxes for cards. Now using
the bus id itself to determine if the
VGA compatible controller
3D controller
Display Controller
refer to separate chips or the same one.
Bus id gives the data needed, because the video chip, the real card, that is,
is on for example 00:05.0 the trailing .0 is the key, that's the actual card.
The audio or display controller for the same card would be for example: 00:05.1
I don't know if this is fully reliable, but it will have to do, either some cards
as is get missed, or some cards get double id'ed, unless I use a hack like this.
There's nothing else I can find but the bus id to determine that it's the same
physical device or not.
2014-03-19 04:31:40 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.7
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-18
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, attempt 2 at detecting all possible syntaxes for cards. Now using
|
|
|
|
|
the bus id itself to determine if the
|
|
|
|
|
VGA compatible controller
|
|
|
|
|
3D controller
|
|
|
|
|
Display Controller
|
|
|
|
|
refer to separate chips or the same one.
|
|
|
|
|
|
|
|
|
|
Bus id gives the data needed, because the video chip, the real card, that is,
|
|
|
|
|
is on for example 00:05.0 the trailing .0 is the key, that's the actual card.
|
|
|
|
|
|
|
|
|
|
The audio or display controller for the same card would be for example: 00:05.1
|
|
|
|
|
|
|
|
|
|
I don't know if this is fully reliable, but it will have to do, either some cards
|
|
|
|
|
as is get missed, or some cards get double id'ed, unless I use a hack like this.
|
|
|
|
|
|
|
|
|
|
There's nothing else I can find but the bus id to determine that it's the same
|
|
|
|
|
physical device or not.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 18 Mar 2014 21:18:27 -0700
|
|
|
|
|
|
2014-03-19 02:19:31 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.6
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-18
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, bug fix, adding 3D controller to output causes doubled card id in some cases.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 18 Mar 2014 19:17:55 -0700
|
|
|
|
|
|
2014-03-18 08:32:31 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.5
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-17
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, serious bug fix, do NOT use 2.1.4, it will fail to start. Bad copy/paste.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 18 Mar 2014 01:30:53 -0700
|
|
|
|
|
|
2014-03-16 22:55:01 +00:00
|
|
|
=====================================================================================
|
2014-03-18 02:26:26 +00:00
|
|
|
Version: 2.1.4
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-17
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version. Some BSD fixes, and a more important fix, added 'display controller'
|
|
|
|
|
to graphics card detection, that's a new one on me. Dual card systems might use this.
|
|
|
|
|
|
|
|
|
|
00:02.0 Display controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
|
|
|
|
|
|
|
|
|
|
01:00.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1)
|
|
|
|
|
|
|
|
|
|
Some more switches to bash native methods as well.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 17 Mar 2014 19:23:42 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-03-16 22:55:01 +00:00
|
|
|
Version: 2.1.3
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-15
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version. Big set of changes: changed all ver: and version: to v:; changed all bash
|
|
|
|
|
${var} to $var where appropriate to avoid extra overhead of ${..}; removed 'basename'
|
|
|
|
|
and replaced with ${path##*/} which avoids unnessary subshells.
|
|
|
|
|
|
|
|
|
|
Fixed dynamic line wraps on -I and -S lines, now those in most cases will work well
|
|
|
|
|
down to 80 cols.
|
|
|
|
|
|
|
|
|
|
Fixed bug in optical drives, at some point in the last few years, the kernel in /sys
|
|
|
|
|
changed the path to the optical drive data, added in /ata8/ (example) so both methods
|
|
|
|
|
are now handled. This should fix a lot of failures to show optical drive brand name etc.
|
|
|
|
|
|
|
|
|
|
Added weechat detection, trying also supybot/limnoria detection in irc client version.
|
|
|
|
|
There was weechat-curses, but I guess they finally dropped the -curses. Limnoria is
|
|
|
|
|
a fork of supybot but still uses the supybot program name, but added in limnoria too
|
|
|
|
|
if they get around to changing that.
|
|
|
|
|
|
|
|
|
|
More dynamic sizing tweaks, more optimization of code. Discovered that dipping into gawk
|
|
|
|
|
is almost 250x more expensive in terms of execution time than using bash variable.
|
|
|
|
|
Will change to use bash directly as time goes along where it's safe and accurate.
|
|
|
|
|
|
|
|
|
|
Added handling to support /run paths using directories, like /run/gdm/gdm.pid for dm data.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 16 Mar 2014 15:09:40 -0700
|
|
|
|
|
|
2014-03-15 03:41:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.2
|
|
|
|
|
Patch Version: 00
|
2014-03-15 17:56:51 +00:00
|
|
|
Script Date: 2014-03-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
no version change, just added wrapper around tput cols so only use it if in terminal
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 15 Mar 2014 10:53:17 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.1.2
|
|
|
|
|
Patch Version: 00
|
2014-03-15 03:41:16 +00:00
|
|
|
Script Date: 2014-03-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version. Updated dynamic sizing, fixed some glitches in cpu flags, fixed bugs in
|
|
|
|
|
cpu main. Cleaned up a few more variable and width issues. Used a few more ${#var} for
|
|
|
|
|
counting.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 14 Mar 2014 20:39:13 -0700
|
|
|
|
|
|
2014-03-14 02:28:40 +00:00
|
|
|
=====================================================================================
|
2014-03-14 20:21:10 +00:00
|
|
|
Version: 2.1.1
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-14
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New Version, new man. This continues the dyanamic line sizing, I'm doing these one at a
|
|
|
|
|
time to make it easier to test stuff one by one.
|
|
|
|
|
|
|
|
|
|
Full refactoring/reordering of top global variables, moved user/maintainer set variables
|
|
|
|
|
to top, and clearly identify all globals.
|
|
|
|
|
|
|
|
|
|
Changed LINE_MAX to COL_MAX but all user configuration files will stay working since
|
|
|
|
|
inxi now will check for that and translate them to the new variable names.
|
|
|
|
|
|
|
|
|
|
New lines fixed, -C cpu and -f cpu plus full flags. Flags output is now fully dynamic to
|
|
|
|
|
display screen in terminal/console. Moved cpu short flags to -x because it's not that
|
|
|
|
|
important in general and just clutters things up in my opinion.
|
|
|
|
|
|
|
|
|
|
Print flags/bogomips on separate line if line greater than display width.
|
|
|
|
|
|
|
|
|
|
The rest of the lines will get a similar treatment, but it takes a bit of trial and error
|
|
|
|
|
for each line to get it working right.
|
|
|
|
|
|
|
|
|
|
Note that IRC line lengths are NOT dyanamic unless I can find a way to determine the column
|
|
|
|
|
width of irc clients, but that won't be accurate since fonts vary in widths for each character.
|
|
|
|
|
|
|
|
|
|
CPU was the worst offender in my opinion in terms of regular output wrapping to new line messily,
|
|
|
|
|
next will be the things with ports/chip id/card id.
|
|
|
|
|
|
|
|
|
|
Tightened up a bit more the dyanamic help / version output handler.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 14 Mar 2014 13:14:51 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2014-03-14 02:28:40 +00:00
|
|
|
Version: 2.1.0
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new man page. Finally, after all these years, dynamically resized to terminal
|
|
|
|
|
window column width help/version outputs. There is a significant slowdown to achieve this,
|
|
|
|
|
but I've optimized it as much as I could so it should be acceptable for most users now.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 13 Mar 2014 19:26:32 -0700
|
|
|
|
|
|
2014-03-13 00:18:26 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 2.0.0
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-12
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New feature, not new line option though. Now shows init type with -x (also shows rc
|
|
|
|
|
type if openrc). -xx shows init / rc version number. Change runlevel to target if
|
|
|
|
|
systemd and if non numeric runlevel given. Should support systemd/upstart/epoch/runit
|
|
|
|
|
sysvinit. Supports openrc as extra data if it's present. Rearranged -I line a bit but
|
|
|
|
|
really just exchanged Runlevel: for Init: v: Runlevel: default:
|
|
|
|
|
|
|
|
|
|
This is the first step, some of the init system ID methods are weak and non robust
|
|
|
|
|
and this may need to be revised, but it should for now identify systemd/upstart quite
|
|
|
|
|
accurately, and in most cases sysvinit. Note that to get sysvinit version number requires
|
|
|
|
|
tool: strings which in debian/ubuntu is in package binutils. I don't know the package names
|
|
|
|
|
for arch/fedora/etc for the recommends check tool in inxi yet.
|
|
|
|
|
|
|
|
|
|
I believe this will be good enough for a first draft version, but over time we'll get it
|
|
|
|
|
more fine tuned, but as it is now, it should cover at least 99% of users, which isn't bad.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 12 Mar 2014 17:12:11 -0700
|
|
|
|
|
|
2014-03-03 23:31:47 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.19
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-03-03
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version; updated man page. Changed slightly the output for x server, in preparation
|
|
|
|
|
for adding alternate display servers, like Wayland or Mir. Rather than release all the
|
|
|
|
|
stuff at once I'm going to do it bit by bit. Currently I have not found a wayland iso
|
|
|
|
|
test cd that boots in virtual box so I will have to wait to really add support there.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 03 Mar 2014 15:27:05 -0800
|
|
|
|
|
|
2014-01-13 23:01:03 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.18
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2014-01-13
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version; new tarball; new man page. Added Unity desktop support; added -xx feature
|
|
|
|
|
to show default runlevel, using systemd/upstart/sysvinit type default tests.
|
|
|
|
|
|
|
|
|
|
Fixed gtk library version detections, now will support dpkg/pacman version tests, which
|
|
|
|
|
should give more data to more people than previously, where the old tests usually would
|
|
|
|
|
return null unless gtk dev packages were installed on the system.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 13 Jan 2014 14:57:38 -0800
|
|
|
|
|
|
New version, new tarball. Fixed new gnome change, they, of course, removed gnome-about
and so version numbers failed. Now first trying gnome-session to get version number.
Also, there's a bug in at least gtk detection in opensuse, not sure what it is, they could
be using a different syntax for the test:
pkg-config --modversion gtk+-3.0
returns no such package on gnome 3.10 installs, but I have no idea what package name to
test for there in this case.
So leaving gtk version bugs unhandled due to no user information or feedback, if you want
it fixed or if it works for your distro, let me know and also if it does not work, tell
me the correct commmand, with its output, to get gtk version.
That's for inxi -Sx output that is.
2013-12-02 22:09:25 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.17
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: 2013-12-02
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixed new gnome change, they, of course, removed gnome-about
|
|
|
|
|
and so version numbers failed. Now first trying gnome-session to get version number.
|
|
|
|
|
|
|
|
|
|
Also, there's a bug in at least gtk detection in opensuse, not sure what it is, they could
|
|
|
|
|
be using a different syntax for the test:
|
|
|
|
|
pkg-config --modversion gtk+-3.0
|
|
|
|
|
|
|
|
|
|
returns no such package on gnome 3.10 installs, but I have no idea what package name to
|
|
|
|
|
test for there in this case.
|
|
|
|
|
|
|
|
|
|
So leaving gtk version bugs unhandled due to no user information or feedback, if you want
|
|
|
|
|
it fixed or if it works for your distro, let me know and also if it does not work, tell
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
me the correct commmand, with its output, to get gtk version.
|
New version, new tarball. Fixed new gnome change, they, of course, removed gnome-about
and so version numbers failed. Now first trying gnome-session to get version number.
Also, there's a bug in at least gtk detection in opensuse, not sure what it is, they could
be using a different syntax for the test:
pkg-config --modversion gtk+-3.0
returns no such package on gnome 3.10 installs, but I have no idea what package name to
test for there in this case.
So leaving gtk version bugs unhandled due to no user information or feedback, if you want
it fixed or if it works for your distro, let me know and also if it does not work, tell
me the correct commmand, with its output, to get gtk version.
That's for inxi -Sx output that is.
2013-12-02 22:09:25 +00:00
|
|
|
|
|
|
|
|
That's for inxi -Sx output that is.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 02 Dec 2013 13:48:35 -0800
|
|
|
|
|
|
2013-10-06 18:10:04 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.16
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: October 6 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Only for uprmq distros, small update to add support for another
|
|
|
|
|
repo type output, the initial listing was not complete of possible syntaxes. Now handles:
|
|
|
|
|
|
|
|
|
|
Nonfree Updates (Local19) /mnt/data/mirrors/mageia/distrib/cauldron/x86_64/media/nonfree/updates
|
|
|
|
|
|
|
|
|
|
as well, apparently that is a possible output format in certain cases with urpmq.
|
|
|
|
|
|
|
|
|
|
Non urpmq distros ignore this update, there are no other actual changes.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 06 Oct 2013 11:06:36 -0700
|
|
|
|
|
|
2013-10-05 01:40:00 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.15
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: October 4 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Added urpmq for -r.
|
|
|
|
|
|
|
|
|
|
Other distros than Mandriva, Mageia, no other changes so no need to update unless you want to.
|
|
|
|
|
|
|
|
|
|
This adds support for Mandriva, Mageia. urpmq parsing is similar but not identical to pisi.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 04 Oct 2013 18:24:55 -0700
|
|
|
|
|
|
2013-08-20 19:28:02 +00:00
|
|
|
=====================================================================================
|
2013-09-10 17:51:12 +00:00
|
|
|
Version: 1.9.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: September 10 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
This does not have a new version number (there is a new date), and is only for solusos,
|
|
|
|
|
so all other distro maintainer can ignore this update. New tarball. Adds support for
|
|
|
|
|
solusos-release distro file in /etc/.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 10 Sep 2013 10:49:29 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2013-08-20 19:28:02 +00:00
|
|
|
Version: 1.9.14
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: August 20 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixed a bug / issue with failed usb nic detection, amazingly, the regex
|
|
|
|
|
in inxi failed to check for Ethernet.*Adapter, heh. Most usb nics are wifi, so I guess ethernet just
|
|
|
|
|
escaped me.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 20 Aug 2013 12:26:10 -0700
|
|
|
|
|
|
New version, new tarball. Fixed a bug in Xorg where it shows drivers as unloaded when they
are actually loaded. Since we can't fix xorg, inxi will try to work around this bug by validating
one step further in the Xorg.0.log data, to confirm that drivers noted as loaded/unloaded/failed are
actually running the display(s) of the system.
There is a possible case of error that might happen due to this change in the case of a system with
a complex xorg that uses two drivers/modules to run two different displays, ie, nvidia on one, and amd
on the other, for example, or intel/nvidia, etc. However, if that bug appears, we'll get that data set
of debugging output and fix it at that point.
This fix repairs an existing xorg bug that is unlikely to get fixed any time soon (the call to load the
detected drivers, eg, vesa, intel, is repeated, causing a failure of driver already loaded on the second
occurance.
2013-08-12 23:25:45 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.13
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: August 12 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixed a bug in Xorg where it shows drivers as unloaded when they
|
|
|
|
|
are actually loaded. Since we can't fix xorg, inxi will try to work around this bug by validating
|
|
|
|
|
one step further in the Xorg.0.log data, to confirm that drivers noted as loaded/unloaded/failed are
|
|
|
|
|
actually running the display(s) of the system.
|
|
|
|
|
|
|
|
|
|
There is a possible case of error that might happen due to this change in the case of a system with
|
|
|
|
|
a complex xorg that uses two drivers/modules to run two different displays, ie, nvidia on one, and amd
|
|
|
|
|
on the other, for example, or intel/nvidia, etc. However, if that bug appears, we'll get that data set
|
|
|
|
|
of debugging output and fix it at that point.
|
|
|
|
|
|
|
|
|
|
This fix repairs an existing xorg bug that is unlikely to get fixed any time soon (the call to load the
|
|
|
|
|
detected drivers, eg, vesa, intel, is repeated, causing a failure of driver already loaded on the second
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
occurance.
|
New version, new tarball. Fixed a bug in Xorg where it shows drivers as unloaded when they
are actually loaded. Since we can't fix xorg, inxi will try to work around this bug by validating
one step further in the Xorg.0.log data, to confirm that drivers noted as loaded/unloaded/failed are
actually running the display(s) of the system.
There is a possible case of error that might happen due to this change in the case of a system with
a complex xorg that uses two drivers/modules to run two different displays, ie, nvidia on one, and amd
on the other, for example, or intel/nvidia, etc. However, if that bug appears, we'll get that data set
of debugging output and fix it at that point.
This fix repairs an existing xorg bug that is unlikely to get fixed any time soon (the call to load the
detected drivers, eg, vesa, intel, is repeated, causing a failure of driver already loaded on the second
occurance.
2013-08-12 23:25:45 +00:00
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 12 Aug 2013 16:20:51 -0700
|
|
|
|
|
|
2013-07-13 18:49:23 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: July 2 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Tiny change, no new version, removed a stray 's' line 4306 that may have made certain distro
|
|
|
|
|
ids get slightly corrupted, but this is so trivial just fixing it, new tarball.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 13 Jul 2013 11:47:48 -0700
|
|
|
|
|
|
2013-07-01 22:15:51 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.12
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: July 2 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Two new desktop/window managers added: spectrwm (similar to scrotwm) and
|
|
|
|
|
herbstluftwm. Both tested and working, thanks anticap from Antix for doing the testing/issue report on this.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 01 Jul 2013 15:13:24 -0700
|
|
|
|
|
|
2013-06-20 02:18:56 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.11
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: June 19 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. The recent bug fixes reminded me to check for ARM working, that had some bugs too,
|
|
|
|
|
so I've updated that. -f for ARM now shows features instead of flags, and the -C regular cpu output does not
|
New version, man page, tarball. ARM cpu core count bug fix. First attempt to add Wayland
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
2017-06-07 02:05:14 +00:00
|
|
|
show cache/flags for arm cpus becuase they don't have those features.
|
2013-06-20 02:18:56 +00:00
|
|
|
|
|
|
|
|
Added some flags passed to various cpu functions and better detections of ARM cpu to handle dual core and other
|
|
|
|
|
issues that were not handled before as well, or at all.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 19 Jun 2013 19:14:10 -0700
|
|
|
|
|
|
New version, new tarball. Some subtle bug fixes, a kvm virtual machine uses disk id in
/proc/partitions of 253, which made the disk totals fail to show up at all. Added that in.
Moved sourcing of configuration files to right after initialize_data so that some variables
can be forced to different values before the next set of system/app checks.
This is to allow specifically turning off, for some headless servers where $DISPLAY is not
null due to a bash configuration bug, these:
B_SHOW_X_DATA='false'
B_RUNNING_IN_X='false'
Setting those two to false in inxi.conf will turn off all the X checks etc even if the $DISPLAY
is set to non null.
Added in support for ksplice kernel version, requires installed uptrack-uname, if that is
present and if uptrack-name kernel version is different from uname then it will add (ksplice)
to kernel version string, and use ksplice kernel version. Also created a single function
get_kernel_version for use by short form/long form inxi output.
For intel xeon cpus, trying a work around for a bug in /proc/cpuinfo which fails to show core_id
or physical_id for cpus, using siblings / 2 for xeons with no actual core counts.
Fixed a bug that made fixes for multimounted partitions fail for disk used. Added in support
for also excluding single partitions mounted to different places.
2013-06-14 23:08:38 +00:00
|
|
|
=====================================================================================
|
New version, new tarball. Another stab at finally fixing the cpu / core count failures on fringe
cases. This required fixing some core logic assumptions that are not currently correct, particularly
on two cases, some xeon cpus fail to show core id for each core, showing 0 for all of them, second,
vm cpus do not show physical ids at all for at least intel, nor do they show core id.
While we can't get HT totally reliable, particularly for vm xeon, since inxi has no way to know in
that case if a core is attached to a physical core or a virtual one, all of them being virtual in that
case, but still inxi is now reporting the correct number of cores, or threads in vm xeons, and is not
showing multicore cpus as single core, which was the main issue.
This required redoing the counter logic for the cpu/core/physical arrays, now they are set independently,
and can handle any of the others not being set, without creating an error or failure condition.
Also added in last check for a certain intel case where core id is 0 but > 1 physical cores exist, that
now also shows the correct cpu / core count.
While this is tested on many data sets of proc cpuinfo, it's still possible there is a fringe case I have
not seen that will trigger yet another unexpected behavior.
2013-06-20 00:29:19 +00:00
|
|
|
Version: 1.9.10
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: June 19 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Another stab at finally fixing the cpu / core count failures on fringe
|
|
|
|
|
cases. This required fixing some core logic assumptions that are not currently correct, particularly
|
|
|
|
|
on two cases, some xeon cpus fail to show core id for each core, showing 0 for all of them, second,
|
|
|
|
|
vm cpus do not show physical ids at all for at least intel, nor do they show core id.
|
|
|
|
|
|
|
|
|
|
While we can't get HT totally reliable, particularly for vm xeon, since inxi has no way to know in
|
|
|
|
|
that case if a core is attached to a physical core or a virtual one, all of them being virtual in that
|
|
|
|
|
case, but still inxi is now reporting the correct number of cores, or threads in vm xeons, and is not
|
|
|
|
|
showing multicore cpus as single core, which was the main issue.
|
|
|
|
|
|
|
|
|
|
This required redoing the counter logic for the cpu/core/physical arrays, now they are set independently,
|
|
|
|
|
and can handle any of the others not being set, without creating an error or failure condition.
|
|
|
|
|
|
|
|
|
|
Also added in last check for a certain intel case where core id is 0 but > 1 physical cores exist, that
|
|
|
|
|
now also shows the correct cpu / core count.
|
|
|
|
|
|
|
|
|
|
While this is tested on many data sets of proc cpuinfo, it's still possible there is a fringe case I have
|
|
|
|
|
not seen that will trigger yet another unexpected behavior.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 19 Jun 2013 17:22:42 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
new version, new tarball. Added support for openSUSE repo syntax/location, as long as it's
zypp or yum it will work. If it's both then it will show only one I believe, if that's a possible scenario, no idea.
Added one more fix for those pesky intel vm cpu core errors, now if /proc/cpuinfo shows no siblings at all,
and no core_id, but does have physical id, it will use the count for physical id as a default for core count.
Not perfect, but better than calling a dual core cpu a single core.
There's still a lot of mysteries with vm versions of kvm cpus, for example, if you see a dual core xeon, is
that actually one core with ht, or two cores? There is no way to find that information out that I can see that is
reliable.
2013-06-16 20:59:53 +00:00
|
|
|
Version: 1.9.9
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: June 16 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, new tarball. Added support for openSUSE repo syntax/location, as long as it's
|
|
|
|
|
zypp or yum it will work. If it's both then it will show only one I believe, if that's a possible scenario, no idea.
|
|
|
|
|
|
|
|
|
|
Added one more fix for those pesky intel vm cpu core errors, now if /proc/cpuinfo shows no siblings at all,
|
|
|
|
|
and no core_id, but does have physical id, it will use the count for physical id as a default for core count.
|
|
|
|
|
|
|
|
|
|
Not perfect, but better than calling a dual core cpu a single core.
|
|
|
|
|
|
|
|
|
|
There's still a lot of mysteries with vm versions of kvm cpus, for example, if you see a dual core xeon, is
|
|
|
|
|
that actually one core with ht, or two cores? There is no way to find that information out that I can see that is
|
|
|
|
|
reliable.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 16 Jun 2013 13:56:28 -0700
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
New version, new tarball. Some subtle bug fixes, a kvm virtual machine uses disk id in
/proc/partitions of 253, which made the disk totals fail to show up at all. Added that in.
Moved sourcing of configuration files to right after initialize_data so that some variables
can be forced to different values before the next set of system/app checks.
This is to allow specifically turning off, for some headless servers where $DISPLAY is not
null due to a bash configuration bug, these:
B_SHOW_X_DATA='false'
B_RUNNING_IN_X='false'
Setting those two to false in inxi.conf will turn off all the X checks etc even if the $DISPLAY
is set to non null.
Added in support for ksplice kernel version, requires installed uptrack-uname, if that is
present and if uptrack-name kernel version is different from uname then it will add (ksplice)
to kernel version string, and use ksplice kernel version. Also created a single function
get_kernel_version for use by short form/long form inxi output.
For intel xeon cpus, trying a work around for a bug in /proc/cpuinfo which fails to show core_id
or physical_id for cpus, using siblings / 2 for xeons with no actual core counts.
Fixed a bug that made fixes for multimounted partitions fail for disk used. Added in support
for also excluding single partitions mounted to different places.
2013-06-14 23:08:38 +00:00
|
|
|
Version: 1.9.8
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: June 14 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Some subtle bug fixes, a kvm virtual machine uses disk id in
|
|
|
|
|
/proc/partitions of 253, which made the disk totals fail to show up at all. Added that in.
|
|
|
|
|
|
|
|
|
|
Moved sourcing of configuration files to right after initialize_data so that some variables
|
|
|
|
|
can be forced to different values before the next set of system/app checks.
|
|
|
|
|
|
|
|
|
|
This is to allow specifically turning off, for some headless servers where $DISPLAY is not
|
|
|
|
|
null due to a bash configuration bug, these:
|
|
|
|
|
B_SHOW_X_DATA='false'
|
|
|
|
|
B_RUNNING_IN_X='false'
|
|
|
|
|
|
|
|
|
|
Setting those two to false in inxi.conf will turn off all the X checks etc even if the $DISPLAY
|
|
|
|
|
is set to non null.
|
|
|
|
|
|
|
|
|
|
Added in support for ksplice kernel version, requires installed uptrack-uname, if that is
|
|
|
|
|
present and if uptrack-name kernel version is different from uname then it will add (ksplice)
|
|
|
|
|
to kernel version string, and use ksplice kernel version. Also created a single function
|
|
|
|
|
get_kernel_version for use by short form/long form inxi output.
|
|
|
|
|
|
|
|
|
|
For intel xeon cpus, trying a work around for a bug in /proc/cpuinfo which fails to show core_id
|
|
|
|
|
or physical_id for cpus, using siblings / 2 for xeons with no actual core counts.
|
|
|
|
|
|
|
|
|
|
Fixed a bug that made fixes for multimounted partitions fail for disk used. Added in support
|
|
|
|
|
for also excluding single partitions mounted to different places.
|
|
|
|
|
|
2013-06-14 23:22:07 +00:00
|
|
|
Also fixed grsec kernel different handling of partitions in /proc/partition and df -hTP, doesn't use
|
|
|
|
|
standard partition numbering. This can't be perfect because inxi cannot know what the actual
|
|
|
|
|
disk sizes are, but it's an ok guess. example: /dev/xvdac (uses 'c' instead of '3' for partition,
|
|
|
|
|
and does not show anything for disk itself.
|
|
|
|
|
|
New version, new tarball. Some subtle bug fixes, a kvm virtual machine uses disk id in
/proc/partitions of 253, which made the disk totals fail to show up at all. Added that in.
Moved sourcing of configuration files to right after initialize_data so that some variables
can be forced to different values before the next set of system/app checks.
This is to allow specifically turning off, for some headless servers where $DISPLAY is not
null due to a bash configuration bug, these:
B_SHOW_X_DATA='false'
B_RUNNING_IN_X='false'
Setting those two to false in inxi.conf will turn off all the X checks etc even if the $DISPLAY
is set to non null.
Added in support for ksplice kernel version, requires installed uptrack-uname, if that is
present and if uptrack-name kernel version is different from uname then it will add (ksplice)
to kernel version string, and use ksplice kernel version. Also created a single function
get_kernel_version for use by short form/long form inxi output.
For intel xeon cpus, trying a work around for a bug in /proc/cpuinfo which fails to show core_id
or physical_id for cpus, using siblings / 2 for xeons with no actual core counts.
Fixed a bug that made fixes for multimounted partitions fail for disk used. Added in support
for also excluding single partitions mounted to different places.
2013-06-14 23:08:38 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 14 Jun 2013 12:36:57 -0700
|
|
|
|
|
|
2013-05-26 03:19:38 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.7
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 25 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New tarball, version, man page. Improved remote weather, now it uses -W, and deprecated -! location=..
|
|
|
|
|
|
|
|
|
|
That was too hard to type and too hard to remember. Also do more dyanamic reordering of weather
|
|
|
|
|
output, depending on how much data is present, and how many x options are used.
|
|
|
|
|
|
|
|
|
|
Added error handling for generic deprecated options, and for options that do not have the correct
|
|
|
|
|
syntax for OPTARG, like with -W.
|
|
|
|
|
|
|
|
|
|
This should about do it for the weather option for now unless I missed something somewhere.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 25 May 2013 20:16:01 -0700
|
|
|
|
|
|
2013-05-20 03:08:05 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.6
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 19 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, tarball. Bug fix, overly loose regex removed na from country/state/city strings,
|
|
|
|
|
like nashville.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sun, 19 May 2013 20:06:44 -0700
|
|
|
|
|
|
2013-05-18 17:52:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.5
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 18 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Fixed some lintian issues in man page, changed man/help for
|
|
|
|
|
-! location= option, to indicate that users must replace space with + themselves.
|
|
|
|
|
|
|
|
|
|
Because of how bash handles these options, inxi cannot add in + signs itself automatically.
|
|
|
|
|
|
|
|
|
|
This should be closer to cleanup of this new feature.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 18 May 2013 10:50:06 -0700
|
|
|
|
|
|
2013-05-18 05:37:29 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.04
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 17 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, tarball. Fixed issue with spaces in names for cities/states/countries, added
|
|
|
|
|
man and help instructions to remove spaces and examples.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 17 May 2013 22:35:59 -0700
|
|
|
|
|
|
2013-05-18 05:14:27 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.03
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 17 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new tarball, version, bug fixes on weather, also optimized speed for slow isps, and added
|
|
|
|
|
a global that can be set in user / system configs to make a longer wget time out. Default
|
|
|
|
|
is 8 seconds.
|
|
|
|
|
|
|
|
|
|
This should take care of the failure from slow load issue reported.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 17 May 2013 22:07:29 -0700
|
|
|
|
|
|
2013-05-18 04:11:18 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.02
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 17 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
|
|
|
|
|
new version, new tarball, bug fix for weather
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 17 May 2013 21:10:21 -0700
|
|
|
|
|
|
2013-05-18 03:27:05 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.01
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 17 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new tarball, version. Bug fix on -! location=, forgot to have it pack its own location
|
|
|
|
|
array, that's now correct.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 17 May 2013 20:17:32 -0700
|
|
|
|
|
|
New version, new tarball, new man page. Unless disabled by distribution maintainers, offers
weather -w option. With -x, -xx-, -xxx, shows more information. Basic line is just weather
and system time there. -x adds time zone, which is useful for servers, particurly web servers.
-x also adds wind speed. -xx adds humidity and barometric pressure. -xxx adds a possible new line,
if data is available, heat index, wind chill, and dew point.
-xxx also adds a line for location (blocked by irc/-z) / weather observation time.
-z filter applies as usual to location data, removes it in irc by default. -Z overrides override.
The api this uses is probably going to be dropped at some point, so this is just going to work
while it works, then it will need to be updated at some point, so don't get very attached to it.
Also adds option to, with -w: -! location=<location string>
This lets users send an alternate location using either <city,state> or <postal code>
or <latitude,longitude> (commas for city,state and latitude,longitude are not optional, and the order
must be as listed.
If There is a developer flag if distro maintainers do not want this enabled, simply set:
B_ALLOW_WEATHER='false'
before packaging and the weather feature will be disabled.
2013-05-18 02:04:29 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.9.00
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 17 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. Unless disabled by distribution maintainers, offers
|
|
|
|
|
weather -w option. With -x, -xx-, -xxx, shows more information. Basic line is just weather
|
|
|
|
|
and system time there. -x adds time zone, which is useful for servers, particurly web servers.
|
|
|
|
|
-x also adds wind speed. -xx adds humidity and barometric pressure. -xxx adds a possible new line,
|
|
|
|
|
if data is available, heat index, wind chill, and dew point.
|
|
|
|
|
-xxx also adds a line for location (blocked by irc/-z) / weather observation time.
|
|
|
|
|
|
|
|
|
|
-z filter applies as usual to location data, removes it in irc by default. -Z overrides override.
|
|
|
|
|
|
|
|
|
|
The api this uses is probably going to be dropped at some point, so this is just going to work
|
|
|
|
|
while it works, then it will need to be updated at some point, so don't get very attached to it.
|
|
|
|
|
|
|
|
|
|
Also adds option to, with -w: -! location=<location string>
|
|
|
|
|
This lets users send an alternate location using either <city,state> or <postal code>
|
|
|
|
|
or <latitude,longitude> (commas for city,state and latitude,longitude are not optional, and the order
|
|
|
|
|
must be as listed.
|
|
|
|
|
|
|
|
|
|
If There is a developer flag if distro maintainers do not want this enabled, simply set:
|
|
|
|
|
B_ALLOW_WEATHER='false'
|
|
|
|
|
before packaging and the weather feature will be disabled.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 17 May 2013 18:47:24 -0700
|
|
|
|
|
|
2013-05-03 22:45:16 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.47
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 3 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Made separators surround the partition id, that avoids any possible
|
|
|
|
|
errors with detections, also added in missing detection for separator.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 03 May 2013 15:41:26 -0700
|
|
|
|
|
|
New version, tarball. Fixed a small issue that would create a wrong reporting of disk
useage if bind mounts are used, ie, multiple binds to a single mount. Now inxi will
check a list of the previously used partitions before adding the size of the used space
to the total used, if the partition has already been used it will skip it. This was/is
a quick and dirty fix, but it's totally fine I believe and should resolve two separate
issues:
1. use of bind mount method, where multiple partition names are bound to the same partition
2. accidental dual mounting to the same partition.
partitions section will still show the same data, ie, if bind is used, it will show all
the bind mounts even when they are attached/bound to a partition that is already listed.
This seems useful information, though maybe we can get the key word 'bind' in there somehow,
but for now I won't worry about that issue, that's just a nice to have, not a bug.
2013-05-03 20:57:40 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.46
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: May 3 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. Fixed a small issue that would create a wrong reporting of disk
|
|
|
|
|
useage if bind mounts are used, ie, multiple binds to a single mount. Now inxi will
|
|
|
|
|
check a list of the previously used partitions before adding the size of the used space
|
|
|
|
|
to the total used, if the partition has already been used it will skip it. This was/is
|
|
|
|
|
a quick and dirty fix, but it's totally fine I believe and should resolve two separate
|
|
|
|
|
issues:
|
|
|
|
|
|
|
|
|
|
1. use of bind mount method, where multiple partition names are bound to the same partition
|
|
|
|
|
2. accidental dual mounting to the same partition.
|
|
|
|
|
|
|
|
|
|
partitions section will still show the same data, ie, if bind is used, it will show all
|
|
|
|
|
the bind mounts even when they are attached/bound to a partition that is already listed.
|
|
|
|
|
This seems useful information, though maybe we can get the key word 'bind' in there somehow,
|
|
|
|
|
but for now I won't worry about that issue, that's just a nice to have, not a bug.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 03 May 2013 13:52:44 -0700
|
|
|
|
|
|
2013-03-02 17:54:48 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.45
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: March 2 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, tarball. As always with fixes, one thing creates a bug in another. Fixed
|
|
|
|
|
linux driver version handling, now only trimming off number from bsd drivers.
|
|
|
|
|
|
|
|
|
|
Some linux drivers, like tg3 for broadcom ethernet, have numbers ending them. So this is
|
|
|
|
|
a bug fix for 1.8.44 release mainly.
|
|
|
|
|
|
|
|
|
|
Also includes openbsd initial fixes for some issues related to sysctl parsing for cpu and ram.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 02 Mar 2013 09:44:17 -0800
|
|
|
|
|
|
New version, new tarball. This version brings the -A, -G, -N, -n, -i pci data
to bsd. Using a pciconf parser to do most of the heavy lifting in this one.
Two functions do the main pci card processing for audio, graphics, and networking.
All seems to be shipshape and working, tested on freebsd 7.3, 9.0, and 9.1 and
the output is consistent.
2013-03-01 05:55:24 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.44
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 28 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-03-01 06:15:15 +00:00
|
|
|
no version change, just added 'chipset' to banlist to filter out.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 28 Feb 2013 22:14:33 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.44
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 28 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
New version, new tarball. This version brings the -A, -G, -N, -n, -i pci data
to bsd. Using a pciconf parser to do most of the heavy lifting in this one.
Two functions do the main pci card processing for audio, graphics, and networking.
All seems to be shipshape and working, tested on freebsd 7.3, 9.0, and 9.1 and
the output is consistent.
2013-03-01 05:55:24 +00:00
|
|
|
New version, new tarball. This version brings the -A, -G, -N, -n, -i pci data
|
|
|
|
|
to bsd. Using a pciconf parser to do most of the heavy lifting in this one.
|
|
|
|
|
|
|
|
|
|
Two functions do the main pci card processing for audio, graphics, and networking.
|
|
|
|
|
|
|
|
|
|
All seems to be shipshape and working, tested on freebsd 7.3, 9.0, and 9.1 and
|
|
|
|
|
the output is consistent.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 28 Feb 2013 21:50:57 -0800
|
|
|
|
|
|
New version, new tarball. Improved B_ALLOW_UPDATES handling, now if set to false,
turns off all -h and -H menu options for updating. Also triggers an error message
if you use -U or -! <10-16/http://>.
Distro maintainers, take note, if you used the B_ALLOW_UPDATES flag, you no longer
need to change the code anywhere, the error messages and blocking the -h output for
update features is automatic as soon as the flag is set to 'false'.
I needed to change the -! handling because -! is now also being used for extra features
like -! 31 and -! 32 and probably more stuff in the future, plus the -! 30 used by
things like the inxi gui tool being worked on by trash80.
Also included in this version are more bsd changes, including initial function for pciconf
data parsing, this will be used for -A, -G, and -N options for card data.
Further bsd improvements are better error/no data available messages for -D and -o.
2013-02-28 23:35:53 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.43
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 28 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Improved B_ALLOW_UPDATES handling, now if set to false,
|
|
|
|
|
turns off all -h and -H menu options for updating. Also triggers an error message
|
|
|
|
|
if you use -U or -! <10-16/http://>.
|
|
|
|
|
|
|
|
|
|
Distro maintainers, take note, if you used the B_ALLOW_UPDATES flag, you no longer
|
|
|
|
|
need to change the code anywhere, the error messages and blocking the -h output for
|
|
|
|
|
update features is automatic as soon as the flag is set to 'false'.
|
|
|
|
|
|
|
|
|
|
I needed to change the -! handling because -! is now also being used for extra features
|
|
|
|
|
like -! 31 and -! 32 and probably more stuff in the future, plus the -! 30 used by
|
|
|
|
|
things like the inxi gui tool being worked on by trash80.
|
|
|
|
|
|
|
|
|
|
Also included in this version are more bsd changes, including initial function for pciconf
|
|
|
|
|
data parsing, this will be used for -A, -G, and -N options for card data.
|
|
|
|
|
|
|
|
|
|
Further bsd improvements are better error/no data available messages for -D and -o.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 28 Feb 2013 15:30:07 -0800
|
|
|
|
|
|
2013-02-28 07:15:13 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.42
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 27 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, small bug fix, inxi failed to add in md raid partition size data to HDD used data.
|
|
|
|
|
|
|
|
|
|
The hdd used still fails to properly calculate the actual raid sizes but that's a bit too tricky
|
|
|
|
|
to do easily so will leave that for some other time.
|
|
|
|
|
|
|
|
|
|
Also added in more hdd used partition types for bsds, wd and ad type drivers for disks.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 27 Feb 2013 23:13:00 -0800
|
|
|
|
|
|
2013-02-28 06:12:04 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.41
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 27 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-02-28 06:36:25 +00:00
|
|
|
small change, new tarball, added some excludes items to unmounted list, scd, dvdrw, cdrw.
|
2013-02-28 06:27:40 +00:00
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 27 Feb 2013 22:26:32 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.41
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 27 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-02-28 06:12:04 +00:00
|
|
|
New version, updated man page. A bug fix for an old time bug: with mdraid, -o (unmounted
|
|
|
|
|
partitions) would show components of the md raid array as unmounted partitions.
|
|
|
|
|
|
|
|
|
|
This is of course incorrect, and is now fixed.
|
|
|
|
|
|
|
|
|
|
Small update of man page as well to note that -o will not show components of mdraid arrays.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 27 Feb 2013 22:09:32 -0800
|
|
|
|
|
|
2013-02-27 22:02:44 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.40
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 27 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, bug fix for mdraid, and cleaned up some errors and weak spots in component
|
|
|
|
|
output for mdraid. Certain conditions would trigger a false return for raid components, now
|
|
|
|
|
it shows more explicitly the online/spare/failed data so it's clear. Also shows 'none' for
|
|
|
|
|
online if none are detected.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 27 Feb 2013 14:00:46 -0800
|
|
|
|
|
|
2013-02-27 20:45:26 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.39
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 27 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, updated man page. Completed zfs raid support for bsds, now include component
|
|
|
|
|
status as with mdraid, will show offline/failed devices as well in standard output.
|
|
|
|
|
|
|
|
|
|
Updated help and man page to reflect the difference between -R, -Rx, and -Rxx output for
|
|
|
|
|
zfs / mdraid.
|
|
|
|
|
|
|
|
|
|
No linux inxi changes, this should not alter any behaviors in -R for mdraid, if it does, it's
|
|
|
|
|
a bug, please report it.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 27 Feb 2013 12:42:02 -0800
|
|
|
|
|
|
New version, updated man page, new tarball.
Fixed partition bug that could falsely identify a remote filesystem like nfs as /dev fs
Added two options:
-! 31 - Turns off Host section of System line. This is useful if you want to post output
from server without posting its name.
-! 32 - Turns on Host section if it has been disabled by user configuration file
B_SHOW_HOST='false'
Added missing CPU data message, fixed missing cpu cache/bogomips output, turned off
bogomips if null for bsd systems because bogomips is a linux kernel feature.
Added N/A for no memory report, this would mainly hit bsd systems where user has no
permissions to use sysctl or has no read rights for /var/run/dmesg.boot.
Many fixes for partitions, now for bsd, if available, uses gpart list to get uuid/label
Added support for raid file system syntax in bsd, now excludes main raid device name,
and adds a flag to raiddevice/partitionname type so output can identify it as a raid
slice/partition.
In man page, added -! 31 / -! 32 sections, and some other small edits.
Added bsd raid line error message, added bsd sensors line error message.
Many other small bug fixes that should make linux more robust in terms of missing
data, and better/cleaner output for bsd.
2013-02-18 20:33:05 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.38
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 18 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, updated man page, new tarball.
|
|
|
|
|
|
|
|
|
|
Fixed partition bug that could falsely identify a remote filesystem like nfs as /dev fs
|
|
|
|
|
|
|
|
|
|
Added two options:
|
|
|
|
|
-! 31 - Turns off Host section of System line. This is useful if you want to post output
|
|
|
|
|
from server without posting its name.
|
|
|
|
|
-! 32 - Turns on Host section if it has been disabled by user configuration file
|
|
|
|
|
B_SHOW_HOST='false'
|
|
|
|
|
|
|
|
|
|
Added missing CPU data message, fixed missing cpu cache/bogomips output, turned off
|
|
|
|
|
bogomips if null for bsd systems because bogomips is a linux kernel feature.
|
|
|
|
|
|
|
|
|
|
Added N/A for no memory report, this would mainly hit bsd systems where user has no
|
|
|
|
|
permissions to use sysctl or has no read rights for /var/run/dmesg.boot.
|
|
|
|
|
|
|
|
|
|
Many fixes for partitions, now for bsd, if available, uses gpart list to get uuid/label
|
|
|
|
|
Added support for raid file system syntax in bsd, now excludes main raid device name,
|
|
|
|
|
and adds a flag to raiddevice/partitionname type so output can identify it as a raid
|
|
|
|
|
slice/partition.
|
|
|
|
|
|
|
|
|
|
In man page, added -! 31 / -! 32 sections, and some other small edits.
|
|
|
|
|
|
|
|
|
|
Added bsd raid line error message, added bsd sensors line error message.
|
|
|
|
|
|
|
|
|
|
Many other small bug fixes that should make linux more robust in terms of missing
|
|
|
|
|
data, and better/cleaner output for bsd.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 18 Feb 2013 12:24:39 -0800
|
|
|
|
|
|
2013-02-12 17:57:17 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.37
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 11 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New tarball. Tiny fix for an obscure fringe case, leaving numbering as is.
|
|
|
|
|
|
|
|
|
|
In some cases, dmidecode returns the grammatically wrong message:
|
|
|
|
|
'No smbios nor dmi data' instead of 'No smbios or dmi data', corrected the search
|
|
|
|
|
to look for simpler: 'no smbios ' to avoid that random error.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 12 Feb 2013 09:54:51 -0800
|
|
|
|
|
|
New version, new tarball. This update fixes a recent bug report with ancient dmidecode versions, that do not
properly support the -s option. Now -M uses only one method for dmidecode, manual construction of the Machine
data from the raw dmidecode file. The file output is also parsed a bit to make it more consistently reliable
for inxi purposes.
This update also includes all recent bsd branch updates, including the new #!/usr/bin/env bash on top which
lets inxi run in any environment without changes. Also for bsd, sets sed -i/sed -i '' global value, which
means that now all the branches are the same, except the bsd branches will contain the most recent tests
and bsd handling.
As each step is reached, I'll release a new inxi that should be stable, this is the first one however that
can be used as is, no changes, for bsd, debian kfreebsd, and linux systems.
Pleasen note that most bsd features are either incomplete or missing completely at this point, but it's a
start.
Some initial changes as well to help options to show more correct linux or bsd terms. These will be updated
as time permits, it is a long process.
2013-02-12 05:01:07 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.37
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 11 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. This update fixes a recent bug report with ancient dmidecode versions, that do not
|
|
|
|
|
properly support the -s option. Now -M uses only one method for dmidecode, manual construction of the Machine
|
|
|
|
|
data from the raw dmidecode file. The file output is also parsed a bit to make it more consistently reliable
|
|
|
|
|
for inxi purposes.
|
|
|
|
|
|
|
|
|
|
This update also includes all recent bsd branch updates, including the new #!/usr/bin/env bash on top which
|
|
|
|
|
lets inxi run in any environment without changes. Also for bsd, sets sed -i/sed -i '' global value, which
|
|
|
|
|
means that now all the branches are the same, except the bsd branches will contain the most recent tests
|
|
|
|
|
and bsd handling.
|
|
|
|
|
|
|
|
|
|
As each step is reached, I'll release a new inxi that should be stable, this is the first one however that
|
|
|
|
|
can be used as is, no changes, for bsd, debian kfreebsd, and linux systems.
|
|
|
|
|
|
|
|
|
|
Pleasen note that most bsd features are either incomplete or missing completely at this point, but it's a
|
|
|
|
|
start.
|
|
|
|
|
|
|
|
|
|
Some initial changes as well to help options to show more correct linux or bsd terms. These will be updated
|
|
|
|
|
as time permits, it is a long process.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 11 Feb 2013 20:55:49 -0800
|
|
|
|
|
|
2013-02-09 04:52:57 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.36
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 8 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Cleaned up patch number sed cleanup that didn't work in bsd.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 08 Feb 2013 20:50:23 -0800
|
|
|
|
|
|
New version, new tarball. All bug fixes and cleanup preparing to support bsd systems, including
kfreebsd from Debian.
Cleaned up all sed and grep that will be used by bsds, added more granular flag for bsd types.
Cleaned up and corrected issues between bsd/linux, more escapes and tests added to drop error
counts in bsds.
Please note that you must use the inxi from branches/bsd for true bsds because sed has extra -i ''
added, and has the proper #!/usr/local/bin/bash
Added -! 16 for gnubsd download/update, that's for gnu bsd systems like gnu/kfreebsd from debian.
That retains the top #!/bin/bash path, and also uses gnu sed so no -i '' syntax.
Moved some grep -o to gawk or sed to avoid using gnu grep unnecessarily, leaving gnu grep where
it will be linux only, for example parsing a /proc file.
Fixed tty irc bugs for bsds and linux, now should show the right console size for both, ideally.
2013-02-09 04:43:18 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.36
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 8 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. All bug fixes and cleanup preparing to support bsd systems, including
|
|
|
|
|
kfreebsd from Debian.
|
|
|
|
|
|
|
|
|
|
Cleaned up all sed and grep that will be used by bsds, added more granular flag for bsd types.
|
|
|
|
|
|
|
|
|
|
Cleaned up and corrected issues between bsd/linux, more escapes and tests added to drop error
|
|
|
|
|
counts in bsds.
|
|
|
|
|
|
|
|
|
|
Please note that you must use the inxi from branches/bsd for true bsds because sed has extra -i ''
|
|
|
|
|
added, and has the proper #!/usr/local/bin/bash
|
|
|
|
|
|
|
|
|
|
Added -! 16 for gnubsd download/update, that's for gnu bsd systems like gnu/kfreebsd from debian.
|
|
|
|
|
|
|
|
|
|
That retains the top #!/bin/bash path, and also uses gnu sed so no -i '' syntax.
|
|
|
|
|
|
|
|
|
|
Moved some grep -o to gawk or sed to avoid using gnu grep unnecessarily, leaving gnu grep where
|
|
|
|
|
it will be linux only, for example parsing a /proc file.
|
|
|
|
|
|
|
|
|
|
Fixed tty irc bugs for bsds and linux, now should show the right console size for both, ideally.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Fri, 08 Feb 2013 20:36:02 -0800
|
|
|
|
|
|
2013-01-29 00:22:50 +00:00
|
|
|
=====================================================================================
|
2013-02-08 04:06:54 +00:00
|
|
|
Version: 1.8.35
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: February 7 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball. Note, this is a refactor release only, and features the core bsd
|
|
|
|
|
support built in, although inxi will not run in bsd unless the top: #!/bin/bash is changed
|
|
|
|
|
to #!/usr/local/bin/bash
|
|
|
|
|
|
|
|
|
|
The actual bsd branch can be grabbed from:
|
|
|
|
|
http://inxi.googlecode.com/svn/branches/bsd/inxi
|
|
|
|
|
then you can keep that version updated using: inxi -! 15
|
|
|
|
|
which will grab the latest bsd version from the svn server.
|
|
|
|
|
|
|
|
|
|
This release also fixes a lot of small bugs that testing for bsd support exposed, but functionally
|
|
|
|
|
most people should see no difference, I just want to get this version up because there are
|
|
|
|
|
so many small changes that it's worth having a release.
|
|
|
|
|
|
|
|
|
|
I was going to have the fixed dmidecode for old systems in 1.8.35 but that will have to wait til
|
|
|
|
|
1.8.36
|
|
|
|
|
|
|
|
|
|
Linux users should see no real changes, except maybe a thing or two will work in certain circumstances
|
|
|
|
|
when it didn't before, like showing MHz on ARM cpus on short inxi.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Thu, 07 Feb 2013 19:56:19 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2013-01-29 00:22:50 +00:00
|
|
|
Version: 1.8.34
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 28 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
new version, new tarball, new man page.
|
|
|
|
|
|
|
|
|
|
small change -Ixx will show running in tty if it's not in X, with tty number.
|
|
|
|
|
|
|
|
|
|
sort of redundant to System: console: data, but that's ok, we'll live for now.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Jan 2013 16:12:45 -0800
|
|
|
|
|
|
2013-01-29 00:03:06 +00:00
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.33
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 28 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
New version, new tarball, new man page. Fixed an old bug where if you start inxi with
|
|
|
|
|
an ssh command sometimes it will not show any client information, just the debugger
|
|
|
|
|
PPID output. Now it will test as a final check to see if it can detect any parent to
|
|
|
|
|
the process. Actually grandparent I believe. Seems to work, it's a fringe case but
|
|
|
|
|
why not handle it?
|
|
|
|
|
|
|
|
|
|
New -xx feature, for -I it will show, if inxi is not running in IRC client and if
|
|
|
|
|
is running in X, and if the grandparent is not 'login', will show the application
|
|
|
|
|
the shell is running in.
|
|
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
Info: Processes: 271 Uptime: 5:36 Memory: 3255.8/4048.5MB Runlevel: 3
|
|
|
|
|
Gcc sys: 4.7.2 alt: 4.0/4.2/4.4/4.5/4.6
|
|
|
|
|
Client: Shell (bash 4.2.37 - started in konsole) inxi: 1.8.33
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Mon, 28 Jan 2013 15:57:15 -0800
|
|
|
|
|
|
2013-01-27 02:40:38 +00:00
|
|
|
=====================================================================================
|
2013-01-27 02:49:42 +00:00
|
|
|
Version: 1.8.32
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 23 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Small changes to man page, updated copyright date, added a patch contributor.
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 26 Jan 2013 18:48:37 -0800
|
|
|
|
|
|
|
|
|
|
=====================================================================================
|
2013-01-27 02:40:38 +00:00
|
|
|
Version: 1.8.32
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 23 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
No version change. New tarball, updated man page.
|
|
|
|
|
|
|
|
|
|
Some lintian changes for man page, escaped required -x type to \-x
|
|
|
|
|
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Sat, 26 Jan 2013 18:39:03 -0800
|
|
|
|
|
|
2013-01-22 00:17:32 +00:00
|
|
|
=====================================================================================
|
2013-01-26 19:14:04 +00:00
|
|
|
Version: 1.8.32
|
2013-01-22 00:45:32 +00:00
|
|
|
Patch Version: 00
|
2013-01-26 19:14:04 +00:00
|
|
|
Script Date: January 23 2013
|
2013-01-22 00:45:32 +00:00
|
|
|
-----------------------------------
|
2013-01-22 00:17:32 +00:00
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
New version, new tarball. Disabled -U in irc clients, with an exit error message.
|
2013-01-22 00:17:32 +00:00
|
|
|
|
2013-01-22 00:26:25 +00:00
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
-- Harald Hope - Wed, 23 Jan 2013 14:45:38 -0800
|
2013-01-22 20:47:00 +00:00
|
|
|
|
|
|
|
|
=====================================================================================
|
2013-01-26 19:14:04 +00:00
|
|
|
Version: 1.8.31
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 23 2013
|
2013-01-22 20:47:00 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
New version, new tarball. Fixed overly verbose output for --version/-V in irc. Also updated
|
|
|
|
|
and made cleaner the version data in verbose mode, non irc.
|
2013-01-22 20:47:00 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Fixed instance where program location would only show a dot . or relative path to inxi. Now
|
|
|
|
|
in version full will show the full path, or should.
|
2013-01-22 20:47:00 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Basic version line now show: inxi 1.8.30-00 (January 22 2013)
|
2013-01-22 20:47:00 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
The verbose information/version shows the license information, website/irc support info, and
|
|
|
|
|
a few other changes.
|
2013-01-22 20:47:00 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Also fixed a small bug where the copyright shows current year, not the actual year of the inxi
|
|
|
|
|
copyright contained in the top comment header.
|
2013-01-23 03:29:36 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Wed, 23 Jan 2013 13:55:35 -0800
|
2013-01-23 03:29:36 +00:00
|
|
|
|
|
|
|
|
=====================================================================================
|
|
|
|
|
Version: 1.8.30
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 22 2013
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
|
|
|
|
Changing compression of inxi.1.gz to gzip -9 to fit lintian tests. This won't matter to anyone
|
|
|
|
|
at this point so no need to change anything.
|
|
|
|
|
-----------------------------------
|
|
|
|
|
-- Harald Hope - Tue, 22 Jan 2013 19:27:54 -0800
|
2013-01-23 22:05:47 +00:00
|
|
|
|
|
|
|
|
=====================================================================================
|
2013-01-26 19:14:04 +00:00
|
|
|
Version: 1.8.30
|
|
|
|
|
Patch Version: 00
|
|
|
|
|
Script Date: January 22 2013
|
2013-01-23 22:05:47 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
New Version, new tarball. Added inxi.changelog to tarball as well.
|
2013-01-23 22:05:47 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Continuing fixes for ARM cpus, it was noted that short form inxi failed to show cpu speed
|
|
|
|
|
derived from bogomips. That's because of the old min/max output that short form used.
|
2013-01-23 22:05:47 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Updated that section to now use N/A as flag, and if N/A for min/max speed, use the speed
|
|
|
|
|
given from first cpu array index, the one derived from bogomips for ARM/razberry pi.
|
2013-01-23 22:05:47 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
Note that there is still no other ARM /proc/cpuinfo available to see if the razberry pi
|
|
|
|
|
fixes work for all ARM cpus, but the fixes will stop hangs and endless loops at worst,
|
|
|
|
|
and may also show some type of cpu speeds for ARM cpus that are not in razpi devices.
|
2013-01-23 22:05:47 +00:00
|
|
|
|
|
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
-- Harald Hope - Tue, 22 Jan 2013 12:38:47 -0800
|
2013-01-23 22:46:54 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
====================================================================================
|
|
|
|
|
Script Version: 1.8.29
|
2013-01-23 22:46:54 +00:00
|
|
|
Patch Version: 00
|
2013-01-26 19:14:04 +00:00
|
|
|
Script Date: January 21 2012
|
2013-01-23 22:46:54 +00:00
|
|
|
-----------------------------------
|
|
|
|
|
Changes:
|
|
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
Bug fix, new version, new tarball.
|
|
|
|
|
|
|
|
|
|
quick work around fix for razberrie pi, get cpu data hung on arm /proc/cpuinfo because
|
|
|
|
|
it doesn't use the standard processor : [digit] format, but uses a string in the
|
|
|
|
|
processor : field, which then hangs inxi which was expecting an integer.
|
|
|
|
|
|
|
|
|
|
Corrected this with a work around, but it will require a lot more ARM /proc/cpuinfo samples
|
|
|
|
|
before the support for ARM can be considered stable.
|
2013-01-23 22:46:54 +00:00
|
|
|
|
2013-01-26 19:14:04 +00:00
|
|
|
For cpu speed, following wikipedia, used bogomips being equal to 1x cpu speed, to derive cpu speed.
|
|
|
|
|
|
|
|
|
|
Better than nothing I guess, but will be wrong in other cases, particularly with dual core arm.
|
2013-01-23 22:46:54 +00:00
|
|
|
-----------------------------------
|
2013-01-26 19:14:04 +00:00
|
|
|
-- Harald Hope - Mon, 21 Jan 2013 16:24:40 -0800
|