No real changes, this will probably be the very last Gawk->Bash inxi 2.3.x release.

Making sure tarball etc is up to date, so it can be stored in 'tarball's branch.

MAINTAINERS:
Pinxi 2.9.00-xxx-p (inxi-perl branch) is nearing completion of its beta test cycle,
and, barring any new issues or bugs (TEST IT NOW AND REPORT ISSUES NOW!), I expect
to release pinxi 2.9.00 as inxi 2.9.01 shortly after I complete the advanced
RAID feature, which should be this week.

If no real issues appear during the following week after the inxi 2.9.0 release, it
will be moved to inxi 3.0.0, as the first stable Perl inxi release.

There will be a new branch, inxi-legacy, that will have the Gawk->Bash inxi 2.3..56
files for historical purposes only. No further work will be done on inxi 2.3 from
now on.

README.txt

@@ -1,10 +1,10 @@
 README for inxi - a command line system information tool
 
-NOTE: there is a feature freeze on inxi 2.3.xx development, except 
+NOTE: there is a feature freeze on inxi 2.3.xx development. All 
-for bug fixes. All current development is on the 2.9.00-xxx-p branch
+current development is on the 2.9.00-xxx-p branch, which is nearing
-which is in alpha or beta states depending on the module being
+final release state (as of patch -0406-p). Once I view 2.9.00-xxx-p 
-worked on. Once I view 2.9.00-xxx-p as feature complete or better 
+as feature complete or better vs inxi 2.3.xx, it will become the 
-vs inxi 2.3.xx, it will become the current master branch of inxi.
+current master branch of inxi.
 
 =====================================================================
 If you do not want to get the full master with gz history data, which
@@ -29,9 +29,7 @@ The one page wiki on github is only a pointer to the real resources.
 
 HTML MAN PAGE: http://smxi.org/docs/inxi-man.htm 
 INXI OPTIONS: http://smxi.org/docs/inxi-options.htm 
-NOTE: both options and man html versions may and probably will lag behind
+NOTE: These may not always be up to date.
-current inxi because doing documentation is boring, and the man to html
-converter I tried is really bad, so it's hard to update the man page html.
 
 ISSUES: https://github.com/smxi/inxi/issues
 No issues accepted for non current inxi releases. See below for more on that.
@@ -44,22 +42,16 @@ DEVELOPER FORUMS: http://techpatterns.com/forums/forum-32.html
 
 SOURCE VERSION CONTROL: https://github.com/smxi/inxi
 MAIN BRANCH: master
-DEVELOPMENT BRANCHES: inxi-perl, one, two, three, android, bsd
+DEVELOPMENT BRANCHES: inxi-perl, one, two, three, android.
 Dev branches are rarely used, but that's where the really hard new features etc
 are debugged and worked out. inxi itself has the built in feature to be able
 to update itself from anywhere, including these branches, which is very useful
 for development and debugging on many user systems.
 
-PULL REQUESTS: inxi is VERY complicated and VERY hard to work on, so unless
+PULL REQUESTS: Please talk to me before starting to work on any patch, unless
-you have already talked to me about contributing, and, more important, shown 
+it's a trivial bug fix. Please: NEVER even think about looking at or using previous 
-that you can actually work with this type of logic, please do not spend time 
-trying to work on inxi, unless it's a trivial patch, to the current branch, 
-current version. Please: NEVER even think about looking at or using previous 
 inxi commits, previous to the current one, as a base for a patch. If you do, 
-your patch / pull request will be rejected immediately, without any discussion.
+your patch / pull request will be rejected.
-
-Note further: no core changes will be accepted until inxi 3.0.0 goes live, 
-since that's just more stuff I have to port over.
 
 inxi has one and only one release, and that is the current one (plus dev releases,
 of course, but those should never be packaged). All previous releases are 
@@ -97,64 +89,49 @@ widely for forum and IRC support, which is I believe it's most common function.
 If you are piping output to paste or post, then make sure to turn off the
 script colors with the -c 0 flag. Script colors in shell are characters.
 
-With some pain, inxi has gotten to the point where some of its hardware
+inxi should always show you your current system state, as far as possible, 
-tools are actually better, more accurate, and astoundingly, faster, than their 
+and should be more reliable than your own beliefs about what is in your system, 
-C version equivalents, but that's not because inxi is great, it's because 
+ideally. In other words, the goal in inxi is to have it be right more than it 
-those other tools just aren't well done in my opinion. inxi should ALWAYS
+is wrong about any system that it runs on. And not to rely on non current system
-show you your current system state, as far as possible, and should be more
-reliable than your own beliefs about what is in your system, ideally. In 
-other words, the goal in inxi is to have it be right more than it is wrong
-about any system that it runs on. And NEVER to rely on non current system
 state data if at all possible. Some things, like memory/ram data, rely on
 radically unreliable system self reporting based on OEM filling out data
 correctly, which doesn't often happen, so in those cases, you want to 
 confirm things like ram capacity with a reputable hardware source, like
 crucial.com, which has the best ram hardware tool I know of.
 
-Tthe absolute core mission of inxi is to always work on all systems all the 
+The core mission of inxi is to always work on all systems all the time. 
-time. Well, all linux systems with the core tools inxi requires to operate
+Well, all linux systems with the core tools inxi requires to operate
 installed. Ie, not android, yet. What this means is this: you can have a 10 
 year old box, or probably 15, not sure, and you can install today's inxi on 
 it, and it will run. It won't run fast, but it will run. I test inxi on a 
 200 MHz  laptop from about 1998 to keep it honest. That's also what was 
 used to optimize the code at some points, since differences appear as seconds,
-not 10ths of seconds.
+not 10ths or 100ths of seconds.
 
-Once inxi has moved to Perl 5.x, from Bash / Gawk, the commitment to always
-work on all hardware no matter how old the OS, with reason, is not changed.
 inxi is being written, and tested, on Perl as old as 5.08, and will work on
-any system that runs Perl 5.08 or later. Pre 3.0.0 inxi will also run on 
+any system that runs Perl 5.08 or later. Pre 3.0.0 Gawk/Bash inxi will also run 
-any system no matter how old, within reason, so there should be no difference.
+on any system no matter how old, within reason, so there should be no difference.
 
 =====================================================================
 BSD SUPPORT
 
-BSD support was, with great pain, added, though it's partial and incomplete.
+BSD support is not as complete as GNU/Linux support due to the fact some of
-BSDs are simply too hard to work with because of their extreme fragmentation, 
+the data simply is not available, or is structured in a way that makes it 
-ie, they don't even share one tool you take for granted on GNU/Linux, like
+unique to each BSD. This fragmentation makes supporting BSDs far more difficult
-lspci. Nor do they share common methods of reporting system hardware data.
+than it should be in the 21st century. The BSD support in inxi is an ongoing
-Nor does a single BSD, even within itself, like FreeBSD, even maintain standard
+process, with more features being added as new data sources and types are 
-methods across releases. So the BSD support in inxi is basically what it is, 
+discovered.
-if more is wanted, then BSD people have to step up and do the work, always'
-keeping in mind that all patches to inxi must not break existing functionality
-for existing supported platforms, be they BSD or GNU/Linux.
 
-I like real BSDs, like OpenBSD, NetBSD, FreeBSD, etc, and prefer that the tools
+I will always accept patches that are well done, if they do not break GNU/Linux, 
-in inxi that can be made to work on BSDs, do work, but their refusal to even 
+and extend BSD support, or add new BSD features. inxi sets initial internal 
-use the same tools or locations or syntaxes for system info simply makes it 
+flags to identify that it is a BSD system vs a GNU/Linux system, after that 
-too hard for me to do that work. I will always accept patches that are well 
+it tests for specific applications and resources.
-done however from competent people, if they do not break GNU/Linux, and extend
-BSD support. Keep in mind, all patches must be based on tool/file tests, not 
-BSD version tests. inxi sets initial internal flags to identify that it is a 
-BSD system vs a GNU/Linux system, after that it tests for specific 
-applications and resources.
 
 inxi will also start on Darwin, OSX's mutated version of a BSD, but my 
-conclusion about darwin is that it is Unix in name only, and I will not spend 
+conclusion about Darwin is that it is Unix in name only, and I will not spend 
 a second of my time adding any further support for that crippled broken 
-corporate pseudo-unix system. Don't ask.
+corporate pseudo-unix system. Don't ask, unless you are willing to pay my
-
+normal professional wages to get that support made.
-If you want to run unix, then OSX is not unix, in my opinion.
 
 =====================================================================
 INXI FEATURES AND FUNCTIONALITY

inxi.changelog

@@ -1,3 +1,42 @@
+=====================================================================================
+Version: 2.3.56
+Patch Version: 00
+Script Date: 2018-02-26
+-----------------------------------
+Changes:
+-----------------------------------
+No real changes, this will probably be the very last Gawk->Bash inxi 2.3.x release.
+
+Making sure tarball etc is up to date, so it can be stored in 'tarball's branch.
+
+MAINTAINERS:
+Pinxi 2.9.00-xxx-p (inxi-perl branch) is nearing completion of its beta test cycle, 
+and, barring any new issues or bugs (TEST IT NOW AND REPORT ISSUES NOW!), I expect 
+to release pinxi 2.9.00 as inxi 2.9.01 shortly after I complete the advanced 
+RAID feature, which should be this week.
+
+If no real issues appear during the following week after the inxi 2.9.0 release, it
+will be moved to inxi 3.0.0, as the first stable Perl inxi release.
+
+There will be a new branch, inxi-legacy, that will have the Gawk->Bash inxi 2.3..56
+files for historical purposes only. No further work will be done on inxi 2.3 from 
+now on.
+
+-----------------------------------
+-- Harald Hope - Tue, 13 Mar 2018 11:29:40 -0700
+
+=====================================================================================
+Version: 2.3.56
+Patch Version: 00
+Script Date: 2018-02-26
+-----------------------------------
+Changes:
+-----------------------------------
+
+
+-----------------------------------
+-- Harald Hope - Tue, 13 Mar 2018 11:29:37 -0700
+
 =====================================================================================
 Version: 2.3.56
 Patch Version: 00