# orderedItems[].object.content
Very exciting!! After years of existence, #acxi (another of my #Perl projects) is being packaged, by #slackware !! Should be in #slackbuilds.org in a day or so. Note that it was never my aim to get it packaged, since it's really a very specialized tool to meet very specialized needs, but if it is going to be packaged, I can think of no better place than #Slackware

# orderedItems[].object.contentMap.en
Very exciting!! After years of existence, #acxi (another of my #Perl projects) is being packaged, by #slackware !! Should be in #slackbuilds.org in a day or so. Note that it was never my aim to get it packaged, since it's really a very specialized tool to meet very specialized needs, but if it is going to be packaged, I can think of no better place than #Slackware

# orderedItems[].object.content
Looks like #acxi might get packaged, won't name the distro until it actually happens. It's not a newbie tool though, so that should make little real difference to acxi development.

# orderedItems[].object.contentMap.en
Looks like #acxi might get packaged, won't name the distro until it actually happens. It's not a newbie tool though, so that should make little real difference to acxi development.

# orderedItems[].object.content
Release early, release often!

Bug fix, 0 data #acxi 3.5.04 released.

You can see the release notes here:
https://github.com/smxi/acxi/blob/3.5. 04/acxi.changelog

and the HTML version here:
https://smxi.org/docs/acxi-changelog.h tm

acxi releases now also leverage the #inxi release tool iinxi-perl/tools/release.pl for the HTML documentation (man, options, changelog) updates, which makes it a breeze to do a new version.

Better living through #Perl

# orderedItems[].object.contentMap.en
Release early, release often!

Bug fix, 0 data #acxi 3.5.04 released.

You can see the release notes here:
https://github.com/smxi/acxi/blob/3.5. 04/acxi.changelog

and the HTML version here:
https://smxi.org/docs/acxi-changelog.h tm

acxi releases now also leverage the #inxi release tool iinxi-perl/tools/release.pl for the HTML documentation (man, options, changelog) updates, which makes it a breeze to do a new version.

Better living through #Perl

# orderedItems[].object.content
Rather than do a quick patch/fix, for the 0 sample content file issue in #acxi did a complete correction, along with small refactor to make logic easier to follow, and code easier to read. Now -Z analyze mode collects and shows all 0 size errors, along with < minimum value, and -Xq exits with error for both #metaflac and #ffprobe options.

Also added size print for < 1 KiB, for B, that wasn't supported so showed 0 if < 1 KiB, now shows B, a 0 sample #flac is 86 B, for example due to metadata.

# orderedItems[].object.contentMap.en
Rather than do a quick patch/fix, for the 0 sample content file issue in #acxi did a complete correction, along with small refactor to make logic easier to follow, and code easier to read. Now -Z analyze mode collects and shows all 0 size errors, along with < minimum value, and -Xq exits with error for both #metaflac and #ffprobe options.

Also added size print for < 1 KiB, for B, that wasn't supported so showed 0 if < 1 KiB, now shows B, a 0 sample #flac is 86 B, for example due to metadata.

# orderedItems[].object.content
Working on some audio, I found a little bug in #acxi, actually a bug and a weak spot in the logic: when analyze feature was run on a set of #FLAC files, and one of them was 0 bytes of data, it crashed acxi due to a divide by zero error, which was due to not validating the math values before using them. Since a 0 byte flac is a critical error, the only warning was a Perl exit error, it did not handle it gracefully with good error messages. Since analyze can run batch, needs 2 modes: exit or warn

# orderedItems[].object.contentMap.en
Working on some audio, I found a little bug in #acxi, actually a bug and a weak spot in the logic: when analyze feature was run on a set of #FLAC files, and one of them was 0 bytes of data, it crashed acxi due to a divide by zero error, which was due to not validating the math values before using them. Since a 0 byte flac is a critical error, the only warning was a Perl exit error, it did not handle it gracefully with good error messages. Since analyze can run batch, needs 2 modes: exit or warn

# orderedItems[].object.content
This type of bug is so hard to trigger that it's about as low priority as possible for #inxi, and just part of the ongoing code cleanup and bug trapping/fixing releases, which were sorely needed, for a few years now. I think the slowed down development pace is finally letting me cleanup and refactor and correct a lot of these very hard to find and fix issues.

# orderedItems[].object.contentMap.en
This type of bug is so hard to trigger that it's about as low priority as possible for #inxi, and just part of the ongoing code cleanup and bug trapping/fixing releases, which were sorely needed, for a few years now. I think the slowed down development pace is finally letting me cleanup and refactor and correct a lot of these very hard to find and fix issues.

# orderedItems[].object.content
Found a super subtle issue, actual cause unknown due to no debugger data, but an #EndeavorOS user posted something that tripped wrong #inxi graphics X Screen output. While searching for the cause, and adding in some debuggers, I discovered that the treatment of #xscreens had been slightly broken ever since the Monitors stuff was refactored a while ago.. This would almost never trigger since almost nobody uses > 1 X Screen anymore, but it was a bug, and is now, or should be, fixed in #pinxi.

# orderedItems[].object.contentMap.en
Found a super subtle issue, actual cause unknown due to no debugger data, but an #EndeavorOS user posted something that tripped wrong #inxi graphics X Screen output. While searching for the cause, and adding in some debuggers, I discovered that the treatment of #xscreens had been slightly broken ever since the Monitors stuff was refactored a while ago.. This would almost never trigger since almost nobody uses > 1 X Screen anymore, but it was a bug, and is now, or should be, fixed in #pinxi.

# orderedItems[].object.content
And for everyone asking, yes, sent #inxi 3.3.23 fresh package to #TinyCore. I'm the packager for inxi in that distro. If you've never checked out tinycore, give it a spin, it's really nifty.

This is going along with the just completed inxi 3.3.23 release to master branch, another fine release, with some ongoing docs and tools updates to make everything smoother.

There were some fixes I wanted to get out in this one, very nice stuff, corner cases, all kinds of things.

# orderedItems[].object.contentMap.en
And for everyone asking, yes, sent #inxi 3.3.23 fresh package to #TinyCore. I'm the packager for inxi in that distro. If you've never checked out tinycore, give it a spin, it's really nifty.

This is going along with the just completed inxi 3.3.23 release to master branch, another fine release, with some ongoing docs and tools updates to make everything smoother.

There were some fixes I wanted to get out in this one, very nice stuff, corner cases, all kinds of things.

# orderedItems[].object.content
Tidying up a few pre-release items in #pinxi, updated the docs for smxi.org/docs/inxi.htm and also expanded some of them. I'll probably do a new #inxi today or tomorrow I think.

I'm continuing to expand the docs, updated inxi-perl/docs/inxi-init.txt for new init stuff, and some new inxi-cpu.txt resources added.

As we mostly all know, doing docs is really tedious, but it pays off over time since this stuff is all so arcane it's impossible to remember it.

# orderedItems[].object.contentMap.en
Tidying up a few pre-release items in #pinxi, updated the docs for smxi.org/docs/inxi.htm and also expanded some of them. I'll probably do a new #inxi today or tomorrow I think.

I'm continuing to expand the docs, updated inxi-perl/docs/inxi-init.txt for new init stuff, and some new inxi-cpu.txt resources added.

As we mostly all know, doing docs is really tedious, but it pays off over time since this stuff is all so arcane it's impossible to remember it.

# orderedItems[].object.content
This is in #pinxi, soon to be next #inxi. The fixes are really adding up here, still seem able to follow my loose goal of fixing, refactoring, upgrading code while adding smaller fixes and enhancements.

Avoiding any new features, just cleaning up and updating existing ones while extending to add arcane niche stuff like #WSL.

And so it goes, goal of slowing down and digesting the last few years coding and work seems to be going well.

# orderedItems[].object.contentMap.en
This is in #pinxi, soon to be next #inxi. The fixes are really adding up here, still seem able to follow my loose goal of fixing, refactoring, upgrading code while adding smaller fixes and enhancements.

Avoiding any new features, just cleaning up and updating existing ones while extending to add arcane niche stuff like #WSL.

And so it goes, goal of slowing down and digesting the last few years coding and work seems to be going well.

# orderedItems[].object.content
Just when you think you have all the init systems handled, found more, #dinit (available to test in #Artix live cd), with #dinitctl, now fully handled. #Hummingbird, untested, but added in theory. #31init added in theory, that's a 31 line C init system!

Fixed some weaknesses with #OpenRC handling as well, was failing to detect it as owner of /proc/1/comm 'init' value, using readlink to test now for dinit as well.

Refactored the init section too, to fit with current internal coding style.

# orderedItems[].object.contentMap.en
Just when you think you have all the init systems handled, found more, #dinit (available to test in #Artix live cd), with #dinitctl, now fully handled. #Hummingbird, untested, but added in theory. #31init added in theory, that's a 31 line C init system!

Fixed some weaknesses with #OpenRC handling as well, was failing to detect it as owner of /proc/1/comm 'init' value, using readlink to test now for dinit as well.

Refactored the init section too, to fit with current internal coding style.

# orderedItems[].object.content
Someone actually ran #inxi in #WSL and found a small undefined string error in the screen resolution/frequency, the latter value is never undefined in normal environments, but it was in WSL wayland/Xwayland. Further data confirms that WSL is working like a docker image, and runs Weston wayland compositor.

A surprising amount of data works, and a few items can probably be upgraded to work. Note that technically I never do any non free os support, but since this is ubuntu, it's ok to fix stuff.

# orderedItems[].object.contentMap.en
Someone actually ran #inxi in #WSL and found a small undefined string error in the screen resolution/frequency, the latter value is never undefined in normal environments, but it was in WSL wayland/Xwayland. Further data confirms that WSL is working like a docker image, and runs Weston wayland compositor.

A surprising amount of data works, and a few items can probably be upgraded to work. Note that technically I never do any non free os support, but since this is ubuntu, it's ok to fix stuff.

# orderedItems[].object.content
A change made possible by recent line indentation and wrapping enhancements, and some wrapping bug fixes, now #inxi supports min width of 60 columns, down from 80. 80 was the previous minimum because the line wrap logic had some weak spots, that have been cleaned up and corrected in recent releases, enabling this change to 60.

It's surprising how well this is working. Columns here are too narrow to show it properly, update your #pinxi to current and check it out yourself!

# orderedItems[].object.contentMap.en
A change made possible by recent line indentation and wrapping enhancements, and some wrapping bug fixes, now #inxi supports min width of 60 columns, down from 80. 80 was the previous minimum because the line wrap logic had some weak spots, that have been cleaned up and corrected in recent releases, enabling this change to 60.

It's surprising how well this is working. Columns here are too narrow to show it properly, update your #pinxi to current and check it out yourself!

# orderedItems[].object.content
Got good #inxi bug report on github, a new use of /dev/disk/by-partuuid for zfs components, which inxi had never seen before. This is being used by ubuntu at least, maybe others, so it could have impacted a lot of people, though only I believe when ZFS devices were made out of partitions, not full disks. Subtle issue.

Always good to get issues like this reported from people doing something I never thought to test.

Made disk total used impossibly big, and raid components failed to show, N/A..

# orderedItems[].object.contentMap.en
Got good #inxi bug report on github, a new use of /dev/disk/by-partuuid for zfs components, which inxi had never seen before. This is being used by ubuntu at least, maybe others, so it could have impacted a lot of people, though only I believe when ZFS devices were made out of partitions, not full disks. Subtle issue.

Always good to get issues like this reported from people doing something I never thought to test.

Made disk total used impossibly big, and raid components failed to show, N/A..

# orderedItems[].object.content
(con'd) This now lets much more of the user info file remain as is, and preserves what is actually a better way to do that syntax, since it's less ambiguous.

Testing this now on real data, seems good after fixing a few initial glitches. Should be released soon, as they say, release early, release often! Well, not often, #acxi is actually very stable and only gets updates when I want to add a feature for some reason. Today that reason appeared, so I added the improved --prefill handlers.

# orderedItems[].object.contentMap.en
(con'd) This now lets much more of the user info file remain as is, and preserves what is actually a better way to do that syntax, since it's less ambiguous.

Testing this now on real data, seems good after fixing a few initial glitches. Should be released soon, as they say, release early, release often! Well, not often, #acxi is actually very stable and only gets updates when I want to add a feature for some reason. Today that reason appeared, so I added the improved --prefill handlers.

# orderedItems[].object.content
Adding a nice, and long thought about feature, to #acxi (which is a very specialized audio processing tool, which, if you want to do what it offers, you might like, but if not, move along, nothing to see there). Finally now the prefill feature (-E,--prefill) can handle field name syntax from info txt files to populate artist/location/date etc values, which is much more reliable than the previous automated version, which relied on the data being in a certain order on top block.

# orderedItems[].object.contentMap.en
Adding a nice, and long thought about feature, to #acxi (which is a very specialized audio processing tool, which, if you want to do what it offers, you might like, but if not, move along, nothing to see there). Finally now the prefill feature (-E,--prefill) can handle field name syntax from info txt files to populate artist/location/date etc values, which is much more reliable than the previous automated version, which relied on the data being in a certain order on top block.

# orderedItems[].object.content
Useful #inxi docs are:
* https://smxi.org/docs/inxi.htm - index of inxi docs
* https://smxi.org/docs/inxi-options.htm - [html version of the -h options
* https://smxi.org/docs/inxi-options.htm - html version of inxi man page
* https://smxi.org/docs/inxi-changelog.h tm - html version of the changelog. Which is very complete
* https://smxi.org/docs/inxi-core-missio n.htm - expanding doc on coding and core features
* https://github.com/smxi/inxi/tree/inxi-perl/docs - main real working docs for inxi data
* https://github.com/smxi/inxi/tree/inxi-perl/tools - inxi internal tools, standalone working versions.

# orderedItems[].object.contentMap.en
Useful #inxi docs are:
* https://smxi.org/docs/inxi.htm - index of inxi docs
* https://smxi.org/docs/inxi-options.htm - [html version of the -h options
* https://smxi.org/docs/inxi-options.htm - html version of inxi man page
* https://smxi.org/docs/inxi-changelog.h tm - html version of the changelog. Which is very complete
* https://smxi.org/docs/inxi-core-missio n.htm - expanding doc on coding and core features
* https://github.com/smxi/inxi/tree/inxi-perl/docs - main real working docs for inxi data
* https://github.com/smxi/inxi/tree/inxi-perl/tools - inxi internal tools, standalone working versions.

# orderedItems[].object.content
To clarify something that seems to cause people confusion, the way I have git setup works like this:

#inxi is master/inxi
#pinxi is inxi-perl/pinxi

pinxi is a standalone development version of inxi, and is never 'merged' in the git sense, nor is it a branch in the git sense, because git branchings and mergins are not compatible with how I think and do stuff, unlike svn directory based branches, which were.

pinxi has its own pinxi.conf file, and inxi has its inxi.conf file. I run both.

# orderedItems[].object.contentMap.en
To clarify something that seems to cause people confusion, the way I have git setup works like this:

#inxi is master/inxi
#pinxi is inxi-perl/pinxi

pinxi is a standalone development version of inxi, and is never 'merged' in the git sense, nor is it a branch in the git sense, because git branchings and mergins are not compatible with how I think and do stuff, unlike svn directory based branches, which were.

pinxi has its own pinxi.conf file, and inxi has its inxi.conf file. I run both.

# orderedItems[].object.content
Congratulations to the #OpenBSD team for another release! Time to upgrade to 7.2. Should be as rock solid as usual.

As an aside, after watching some presentations on #Pledge, and noting their comments about making Pledge easy to implement for developers, I decided to take them up on that claim and test it, so I added Pledge support for #inxi, which activates when the Pledge Perl module is available, which is currently only in OpenBSD. It was as clean and easy as they said it would be.

# orderedItems[].object.contentMap.en
Congratulations to the #OpenBSD team for another release! Time to upgrade to 7.2. Should be as rock solid as usual.

As an aside, after watching some presentations on #Pledge, and noting their comments about making Pledge easy to implement for developers, I decided to take them up on that claim and test it, so I added Pledge support for #inxi, which activates when the Pledge Perl module is available, which is currently only in OpenBSD. It was as clean and easy as they said it would be.

# orderedItems[].object.content
Since mastodon.technology is shutting down November 1, and closing December, I'm moving my posts from there to here, at least, some of them.

Where possible, I'll try to include the post dates, though often I used all the allowed character count.

I'm the author of #inxi, and that's what I will generally post about. Also #acxi, though that's not as well known.

# orderedItems[].object.contentMap.en
Since mastodon.technology is shutting down November 1, and closing December, I'm moving my posts from there to here, at least, some of them.

Where possible, I'll try to include the post dates, though often I used all the allowed character count.

I'm the author of #inxi, and that's what I will generally post about. Also #acxi, though that's not as well known.