{"id":13439294,"url":"https://github.com/smxi/inxi","last_synced_at":"2025-09-29T00:32:36.470Z","repository":{"id":36814757,"uuid":"41121631","full_name":"smxi/inxi","owner":"smxi","description":"inxi is a full featured CLI system information tool. It is available in most Linux distribution repositories, and does its best to support the BSDs. ","archived":true,"fork":false,"pushed_at":"2024-01-12T20:05:01.000Z","size":9794,"stargazers_count":1239,"open_issues_count":15,"forks_count":90,"subscribers_count":36,"default_branch":"master","last_synced_at":"2025-07-02T03:05:23.185Z","etag":null,"topics":["arm","bsd","cli-utilities","linux","perl","perl5","remote-admin-tool","support-tools","sysadmin-tool","sysinfo","system-administration"],"latest_commit_sha":null,"homepage":"http://smxi.org/docs/inxi.htm","language":"Perl","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/smxi.png","metadata":{"files":{"readme":"README.txt","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2015-08-20T22:24:50.000Z","updated_at":"2025-06-19T23:51:38.000Z","dependencies_parsed_at":"2023-12-18T23:33:48.722Z","dependency_job_id":"4c845029-fd6a-45cc-9587-7265a7885e5c","html_url":"https://github.com/smxi/inxi","commit_stats":{"total_commits":1997,"total_committers":13,"mean_commits":153.6153846153846,"dds":0.2949424136204306,"last_synced_commit":"15a55d0b948d4ddaffd5bfb266d4d12077b8fc39"},"previous_names":[],"tags_count":104,"template":false,"template_full_name":null,"purl":"pkg:github/smxi/inxi","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/smxi%2Finxi","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/smxi%2Finxi/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/smxi%2Finxi/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/smxi%2Finxi/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/smxi","download_url":"https://codeload.github.com/smxi/inxi/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/smxi%2Finxi/sbom","scorecard":{"id":834075,"data":{"date":"2025-08-11","repo":{"name":"github.com/smxi/inxi","commit":"15a55d0b948d4ddaffd5bfb266d4d12077b8fc39"},"scorecard":{"version":"v5.2.1-40-gf6ed084d","commit":"f6ed084d17c9236477efd66e5b258b9d4cc7b389"},"score":3,"checks":[{"name":"Token-Permissions","score":-1,"reason":"No tokens found","details":null,"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#token-permissions"}},{"name":"Maintained","score":0,"reason":"project is archived","details":["Warn: Repository is archived."],"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#maintained"}},{"name":"Packaging","score":-1,"reason":"packaging workflow not detected","details":["Warn: no GitHub/GitLab publishing workflow detected."],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#packaging"}},{"name":"Binary-Artifacts","score":10,"reason":"no binaries found in the repo","details":null,"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#binary-artifacts"}},{"name":"Code-Review","score":0,"reason":"Found 0/30 approved changesets -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#code-review"}},{"name":"Dangerous-Workflow","score":-1,"reason":"no workflows found","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#dangerous-workflow"}},{"name":"SAST","score":0,"reason":"no SAST tool detected","details":["Warn: no pull requests merged into dev branch"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#sast"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#cii-best-practices"}},{"name":"Pinned-Dependencies","score":-1,"reason":"no dependencies found","details":null,"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#pinned-dependencies"}},{"name":"Security-Policy","score":0,"reason":"security policy file not detected","details":["Warn: no security policy file detected","Warn: no security file to analyze","Warn: no security file to analyze","Warn: no security file to analyze"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#security-policy"}},{"name":"Vulnerabilities","score":10,"reason":"0 existing vulnerabilities detected","details":null,"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#vulnerabilities"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#fuzzing"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE.txt:0","Info: FSF or OSI recognized license: GNU General Public License v3.0: LICENSE.txt:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#license"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":0,"reason":"branch protection not enabled on development/release branches","details":["Warn: branch protection not enabled for branch 'master'"],"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#branch-protection"}}]},"last_synced_at":"2025-08-23T18:29:43.245Z","repository_id":36814757,"created_at":"2025-08-23T18:29:43.245Z","updated_at":"2025-08-23T18:29:43.245Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":277450939,"owners_count":25819971,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-28T02:00:08.834Z","response_time":79,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["arm","bsd","cli-utilities","linux","perl","perl5","remote-admin-tool","support-tools","sysadmin-tool","sysinfo","system-administration"],"created_at":"2024-07-31T03:01:12.732Z","updated_at":"2025-09-29T00:32:35.917Z","avatar_url":"https://github.com/smxi.png","language":"Perl","readme":"README for inxi - a command line system information tool\n\nThe new faster, more powerful Perl inxi is here! File all issue reports with the \nmaster branch. All support for versions prior to 3.0 is now ended, sorry. \n\nMake sure to update to the current inxi from the master branch before filing any \nissue reports. The code in pre 2.9 versions literally no longer exists in inxi \n3. Bugs from earlier versions cannot usually be solved in the new version since \nthe pre 2.9 and the 2.9 and later versions are completely different internally.\n\n--------------------------------------------------------------------------------\nCODEBERG SOURCE REPO\n--------------------------------------------------------------------------------\n\nPackagers: Make sure to change your package URLs and repos to use codeberg.org.\n\nThe previous inxi-perl, tarballs, and docs branches are now standalone repos\non codeberg.org:\n\ndocs      \u003e https://codeberg.org/smxi/inxi-docs master\ninxi-perl \u003e https://codeberg.org/smxi/pinxi master\nmaster    \u003e https://codeberg.org/smxi/inxi master\ntarballs  \u003e https://codeberg.org/smxi/inxi-tarballs master\n\ninxi-perl has been rebuilt and now only contains the pinxi, pinxi.1 files, plus\na minimal README.txt for github users. docs and tarballs have been deleted. The\ninxi-perl branch should not be used, and exists only so that current pinxi users \ncan update from there to get the new version with new URLs.\n\ninxi master and inxi-perl/pinxi will be mirrored until late 2023, then they will\nno longer get updates.\n\nThe inxi repo only contains master, plus the one, two branches, which are \nobsolete. \n\n--------------------------------------------------------------------------------\n\nPlease file issue reports or feature requests at:\n\nhttps://codeberg.org/smxi/inxi\n\nPlease take the time to read this helpful article from the Software Freedom\nConservancy:\n\nhttps://sfconservancy.org/GiveUpGitHub/\n\nAny use of this project's code by GitHub Copilot, past or present, is done \nwithout my permission. I do not consent to GitHub's use of this project's code \nin Copilot.\n\n--------------------------------------------------------------------------------\nDONATE\n--------------------------------------------------------------------------------\n\nHelp support the project with a one time or a sustaining donation.\n\nPaypal: https://www.paypal.com/donate/?hosted_button_id=77DQVM6A4L5E2\n\nLiberaPay (sustaining donations): https://liberapay.com/smxi/\n\n================================================================================\nDEVELOPMENT AND ISSUES\n--------------------------------------------------------------------------------\n\nMake inxi better! Expand supported hardware and OS data, fix broken items!\n\n--------------------------------------------------------------------------------\nHELP PROJECT DEVELOPMENT! SUBMIT A DEBUGGER DATASET\n--------------------------------------------------------------------------------\n\nThis is easy to do, and only takes a few seconds. These datasets really help the \nproject add and debug features. You will generally also be asked to provide this \ndata for non trivial issue reports.\n\nNote that the following options are present:\n\n1. Generate local gz'ed debugger dataset. Leaves gz on your system:\n inxi version \u003e= 3: inxi --debug 20 \n2. Generate, upload gz'ed debugger dataset. Leaves gz on your system:\n inxi version \u003e= 3: inxi --debug 21\n3. Generate, upload, delete gz'ed debugger dataset:\n inxi version \u003e= 3: inxi --debug 22\n\nYou can run these as regular user, or root/sudo, which will gather a bit more \ndata, like from dmidecode, and other tools that need superuser permissions to \nrun.\n\nARM (plus MIPS, SPARC, PowerPC) and BSD datasets are particularly appreciated \nbecause we simply do not have enough of those.\n\n--------------------------------------------------------------------------------\nFILE AN ISSUE IF YOU FIND SOMETHING MISSING, BROKEN, OR FOR AN ENHANCEMENT\n--------------------------------------------------------------------------------\n\ninxi strives to support the widest range of operating systems and hardware, from \nthe most simple consumer desktops, to the most advanced professional hardware \nand servers. \n\nThe issues you post help maintain or expand that support, and are always \nappreciated since user data and feedback is what keeps inxi working and \nsupporting the latest (or not so latest) hardware and operating systems. \n\nSee INXI VERSION/SUPPORT/ISSUES/BUGS INFORMATION for more about issues/support.\n\nSee BSD/UNIX below for qualifications re BSDs, and OSX in particular. \n\n================================================================================\nSOURCE VERSION CONTROL\n--------------------------------------------------------------------------------\n\ninxi:\nREPO: https://codeberg.org/smxi/inxi\nMAIN BRANCH: master\nDEVELOPMENT BRANCHES [not used]: one, two\n\npinxi [development version for inxi]:\nREPO: https://codeberg.org/smxi/pinxi\nMAIN BRANCH: master\n\npinxi is the standalone development version of inxi. inxi branches one, two are \nrarely if ever used. inxi has the built in feature to be able to update itself \nfrom anywhere, including these branches, which is very useful for development \nand debugging on various user systems.\n\nPlease: NEVER even think about looking at or using previous inxi commits, \nprevious to the current master version, as a base for a patch. If you do, your \npatch / pull request will probably be rejected.\n\nPULL REQUESTS: Please talk to me before starting to work on patches of any \nreasonable complexity. inxi is hard to work on, and you have to understand how \nit works before submitting patches, unless it's a trivial bug fix. Never work \nwith inxi master, always work with pinxi master, since it can be quite far ahead \nof inxi. inxi master has only one purpose, to get updated to next inxi when \npinxi is ready to be copied over to inxi. pinxi is always equal to or ahead of \nmaster branch inxi.\n\nMan page updates, doc pages updates, etc, of course, are easy and will probably \nbe accepted, as long as they are properly formatted and logically coherent. \n\nWhen under active development, pinxi releases early, and releases often. inxi\nis stable and is generally only updated when a new tagged version is completed.\n\nPACKAGERS: inxi has one and only one 'release', and that is the current tagged \nversion in the master branch (plus pinxi repo, of course, but pinxi should in \ngeneral not be packaged). \n\n--------------------------------------------------------------------------------\nMASTER BRANCH\n--------------------------------------------------------------------------------\n\nThis is the only supported branch, and the current latest commit/version is the \nonly supported 'release'. There are no 'releases' of inxi beyond the current \ncommit/version in master. All past versions are not supported. \n\ngit clone https://codeberg.org/smxi/inxi --branch master --single-branch\n\nOR direct fast and easy install:\n\nwget -O inxi https://codeberg.org/smxi/inxi/raw/master/inxi\n\nOR easy to remember shortcut (which redirects to codeberg.org):\n\nwget -O inxi https://smxi.org/inxi\nwget -O inxi smxi.org/inxi\n\nNOTE: There are no 'Releases' per se. There are only tagged commits, period. A \ntag is a pointer to a commit, and has no further meaning. A tagged commit \nhowever is the target for packagers.\n\nIf your distribution has blocked -U self updater and you want a newer version:\n\nOpen /etc/inxi.conf and change false to true: B_ALLOW_UPDATE=true\n\n--------------------------------------------------------------------------------\n\nSPECIAL NOTE FOR LEGACY OPERATING SYSTEMS WITH NO TLS 1.2 OR GREATER: Modern web \nservers are dropping support for TLS 1.0, 1.1, and so has smxi.org, this means \nto install inxi onto an older system with only TLS 1.0 or 1.1 available, you \nwill need to do this to install inxi onto the old system:\n\nwget -O /usr/local/bin/inxi ftp://ftp.smxi.org/outgoing/inxi\n\nthen update inxi/man pages after that with inxi -U 4, which uses FTP, not HTTP,\nto download the file.\n\nFor pinxi, just change inxi to pinxi above (add --man to get the man page), and \nit will work the same.\n\n--------------------------------------------------------------------------------\nDEVELOPMENT VERSION (in pinxi repo)\n--------------------------------------------------------------------------------\n\nAll active development is done in the pinxi repo master branch.:\n\ngit clone https://codeberg.org/smxi/pinxi\n\nOR direct fast and easy install:\n\nwget -O pinxi https://codeberg.org/smxi/pinxi/raw/master/pinxi\n\nOR easy to remember shortcut (which redirects to codeberg.org):\n\nwget -O pinxi https://smxi.org/pinxi\nwget -O pinxi smxi.org/pinxi\n\nOnce new features have been debugged, tested, and are reasonably stable, pinxi \nis copied to inxi in the inxi master branch.\n\nIt's a good idea to check with pinxi if you want to make sure your issue has not \nbeen corrected, since pinxi is always equal to or ahead of inxi.\n\nSee SPECIAL NOTE FOR LEGACY OPERATING SYSTEMS above to install pinxi on very old \noperating systems with out of date TLS version.\n\n--------------------------------------------------------------------------------\nLEGACY INXI (in inxi-legacy repo)\n--------------------------------------------------------------------------------\n\nIf you'd like to look at the Gawk/Bash version of inxi, you can find it in the \ninxi-legacy repo, as binxi in the /inxi-legacy directory:\n\nDirect fast and easy install:\n\nwget -O binxi https://codeberg.org/smxi/inxi-legacy/raw/master/binxi\n\nOR easy to remember shortcut (which redirects to codeberg.org):\n\nwget -O binxi https://smxi.org/binxi\n\nThis version will not be maintained, and it's unlikely that any time will be \nspent on it in the future, but it is there in case it's of use or interest to \nanyone.\n\nThis was kept for a long time as the inxi-legacy branch of inxi, but was moved \nto the inxi-legacy repo 2021-09-24.\n\n================================================================================\nSUPPORT INFO\n--------------------------------------------------------------------------------\n\nDo not ask for basic help that reading the inxi -h / --help menus, or man page \nwould show you, and do not ask for features to be added that inxi already has. \nAlso do not ask for support if your distro won't update its inxi version, some \nare bad about that.\n\n--------------------------------------------------------------------------------\nDOCUMENTATION\n--------------------------------------------------------------------------------\n\nhttps://smxi.org/docs/inxi.htm \n(smxi.org/docs/ is easier to remember, and is one click away from inxi.htm). The \none page wiki on codeberg.org is only a pointer to the real resources.\n\nhttps://codeberg.org/smxi/pinxi/src/branch/master/docs\n\nContains specific Perl inxi documentation, of interest mostly to developers. \nIncludes internal inxi tools, values, configuration items. Also has useful \ninformation about Perl version support, including the list of Core modules that \n_should_ be included in a distribution's core modules, but which are \nunfortunately sometimes removed. \n\nINXI CONFIGURATION: https://smxi.org/docs/inxi-configuration.htm \nHTML MAN PAGE: https://smxi.org/docs/inxi-man.htm \nINXI OPTIONS PAGE: https://smxi.org/docs/inxi-options.htm \n\nNOTE: Check the inxi version number on each doc page to see which version will \nsupport the options listed. The man and options page also link to a legacy \nversion, pre 2.9.\n\nhttps://codeberg.org/smxi/inxi/wiki\n\nThis is simply a page with links to actual inxi resources, which can be useful \nfor developers and people with technical questions. No attempt will be made to \nreproduce those external resources on codeberg.org. You'll find stuff like \nhow to export to json/xml there, and basic core philosophies, etc. \n\n--------------------------------------------------------------------------------\nIRC\n--------------------------------------------------------------------------------\n\nYou can go to: \n\nirc.oftc.net or irc.libera.chat channel #smxi \n\nbut be prepared to wait around for a while to get a response. Generally it's \nbetter to use codeberg.org issues.\n\n--------------------------------------------------------------------------------\nISSUES\n--------------------------------------------------------------------------------\n\nhttps://codeberg.org/smxi/inxi/issues\n\nNo issues accepted for non current inxi versions. See below for more on that. \nUnfortunately as of 2.9, no support or issues can be accepted for older inxi's \nbecause inxi 2.9 (Perl) and newer is a full rewrite, and legacy inxi is not \nbeing supported since our time here on earth is finite (plus of course, one \nreason for the rewrite was to never have to work with Gawk-\u003eBash again!).\n\nSys Admin type inxi users always get the first level of support. ie, convince us \nyou run real systems and networks, and your issue shoots to the top of the line. \nAs do any real bugs. \n\nFailure to supply requested debugger data will lead To a distinct lack of \ninterest on our part to help you with a bug. ie, saying, oh, it doesn't work, \ndoesn't cut it, unless it's obvious why. \n\n--------------------------------------------------------------------------------\nSUPPORT FORUMS\n--------------------------------------------------------------------------------\n\nhttps://techpatterns.com/forums/forum-33.html\nThis is the best place to place support issues that may be complicated.\n\nIf you are developer, use:\nDEVELOPER FORUMS: https://techpatterns.com/forums/forum-32.html\n\n================================================================================\nABOUT INXI\n--------------------------------------------------------------------------------\n\ninxi is a command line system information tool. It was forked from the ancient \nand mindbendingly perverse yet ingenius infobash, by locsmif. \n\nThat was a buggy, impossible to update or maintain piece of software, so the \nfork fixed those core issues, and made it flexible enough to expand the utility \nof the original ideas. Locmsif has given his thumbs up to inxi, so don't be \nfooled by legacy infobash stuff you may see out there.\n\ninxi is lower case, except when I create a text header here in a file like this, \nbut it's always lower case. Sometimes to follow convention I will use upper case \ninxi to start a sentence, but i find it a bad idea since invariably, someone \nwill repeat that and type it in as the command name, then someone will copy \nthat, and complain that the command: Inxi doesn't exist...\n\nThe primary purpose of inxi is for support, and sys admin use. inxi is used \nwidely for forum and IRC support, which is I believe it's most common function.\n\nIf you are piping output to paste or post (or writing to file), inxi now \nautomatically turns off color codes, so the inxi 2.3.xx and older suggestion to \nuse -c 0 to turn off colors is no longer required.\n\ninxi strives to be as accurate as possible, but some things, like memory/ram \ndata, depend on radically unreliable system self reporting based on OEM filling \nout data correctly, which doesn't often happen, so in those cases, you want to \nconfirm things like ram capacity with a reputable hardware source, like \ncrucial.com, which has the best ram hardware tool I know of.\n\n--------------------------------------------------------------------------------\nCOMMITMENT TO LONG TERM STABILITY\n--------------------------------------------------------------------------------\n\nThe core mission of inxi is to always work on all systems all the time. Well, \nall systems with the core tools inxi requires to operate installed. \n\nWhat this means is this: you can have a 10 year old box, or probably 15, not \nsure, and you can install today's inxi on it, and it will run. It won't run \nfast, but it will run. I test inxi on a 200 MHz laptop from about 1998 to keep \nit honest. That's also what was used to optimize the code at some points, since \ndifferences appear as seconds, not 10ths or 100ths of seconds on old systems \nlike that.\n\ninxi is being written, and tested, on Perl as old as 5.08, and will work on any \nsystem that runs Perl 5.08 or later. Pre 2.9.0 Gawk/Bash inxi will also run on \nany system no matter how old, within reason, so there should be no difference.\n\n--------------------------------------------------------------------------------\nFEATURES AND FUNCTIONALITY\n--------------------------------------------------------------------------------\n\ninxi's functionality continues to grow over time, but it's also important to \nunderstand that each core new feature usually requires about 30 days work to get \nit stable. So new features are not trivial things, nor is it acceptable to \nsubmit a patch that works only on your personal system. \n\nOne inxi feature (-s, sensors data), took about 2 hours to get working in the \nalpha test on the local dev system, but then to handle the massive chaos that is \nactual user sensors output and system variations, it took several rewrites and \nabout 30 days to get somewhat reliable for about 98% or so of inxi users. So if \nyour patch is rejected, it's likely because you have not thought it through \nadequately, have not done adequate testing cross system and platform, etc.\n\n--------------------------------------------------------------------------------\nSUPPORTED VERSIONS / DISTRO VERSIONS\n--------------------------------------------------------------------------------\n\nImportant: the only version of inxi that is supported is the latest current \nmaster branch version/commit. No issue reports or bug reports will be accepted \nfor anything other than current master branch. No merges, attempts to patch old \ncode from old versions, will be considered or accepted on the master branch of \ninxi. If you are not updated to the latest inxi, do not file a bug report since \nit's probably been fixed ages ago. If your distro isn't packaging a current \ninxi, then file a bug report with your packager, not here. \n\nThe development branch inxi-perl/pinxi  has been moved to its own standalone \nrepo, pinxi, at https://codeberg.org/smxi/pinxi - this is the only place \ndevelopment happens.\n\ninxi is 'rolling release' software, just like Debian Sid, Gentoo, or Arch Linux \nare rolling release GNU/Linux distributions, with no 'release points'.\n\nDistributions should never feel any advantage comes from using old inxi versions \nbecause inxi has as a core promise to you, the end user, that it will never \nrequire new tools to run. New tools may be required for a new feature, but that \nwill always be handled internally by inxi, and will not cause any operational \nfailures. This is a promise, and I will never as long as I run this project \nviolate that core inxi requirement. Old inxi is NOT more stable than current \ninxi, it's just old, and lacking in bug fixes and features. For pre 2.9 \nversions, it's also significantly slower, and with fewer features.\n\nYour distro not updating inxi ever, then failing to show something that is fixed \nin current inxi is not a bug, and please do not post it here. File the issue \nwith your distro, not here. Updating inxi in a package pool will NEVER make \nanything break or fail, period. It has no version based dependencies, just \nsoftware, like Perl 5.xx, lspci, etc. There is never a valid reason to not \nupdate inxi in a package pool of any distro in the world (with one single known \nexception, the Slackware based Puppy Linux release, which ships without the full \nPerl language. The Debian based one works fine).\n\n--------------------------------------------------------------------------------\nSEMANTIC VERSION NUMBERING\n--------------------------------------------------------------------------------\n\ninxi uses 'semantic' version numbering, where the version numbers actually mean \nsomething.\n\nThe version number follows these guidelines:\n\nUsing example 3.2.28-6\n\nThe first digit(s), \"3\", is a major version, and almost never changes. Only a \nhuge milestone, or if inxi reaches 3.9.xx, when it will simply move up to 4.0.0 \njust to keep it clean, would cause a change. \n\nThe second digit(s), \"2\", means a new real feature has been added. Not a tweaked \nexisting feature, an actual new feature, which usually also has a new argument \noption letter attached. The second number goes from 0 to 9, and then rolls over \nthe first after 9. \n\nThe third, \"28\", is for everything not covered by 1 and 2, can cover bug fixes, \ntweaks to existing features to add support for something, full on refactors of \nexisting features, pretty much anything where you want the end user to know that \nthey are not up to date. The third goes from 0 to 99, then rolls over the \nsecond.\n\nThe fourth, \"6\", is extra information about certain types of inxi updates. I \ndon't usually use this last one in master branch, but you will see it in \nbranches one,two, inxi-perl, inxi-legacy since that is used to confirm remote \ntest system patch version updates.\n\nThe fourth number, when used, will be alpha-numeric, a common version would be, \nin say, branch one: 2.2.28-b1-02, in other words: branch 1 patch version 2.\n\nIn the past, now and then the 4th, or 'patch', number, was used in trunk/master \nbranches of inxi, but I've pretty much stopped doing that because it's \nconfusing.\n\ninxi does not use the fiction of date based versioning because that imparts no \nuseful information to the end user, when you look at say, 2.2.28, and you last \nhad 2.2.11, you can know with some certainty that inxi has no major new \nfeatures, just refactors or expansion of existing logic, enhancements, fine \ntunings, and bug fixes. And if you see one with 2.3.2, you will know that there \nis a new feature, almost, but not always, linked to one or more new line output \nitems. Sometimes a the changes in the third number can be quite significant, \nsometimes it's a one line code or bug fix. \n\nA move to a new full version number, like the rewrite of inxi to Perl, would \nreflect in first version say, 2.9.01, then after a period of testing, where most \nlittle glitches are fixed, a move to 3.0.0. These almost never happen. I do not \nexpect for example version 4.0 to ever happen after 3.0 (early 2018), unless so \nmany new features are added that it actually hits 3.9, then it would roll over \nto 4.\n\n================================================================================\nBSD / UNIX\n--------------------------------------------------------------------------------\n\nBSD support is not as complete as GNU/Linux support due to the fact some of the \ndata simply is not available, or is structured in a way that makes it unique to \neach BSD, or is difficult to process. This fragmentation makes supporting BSDs \nfar more difficult than it should be in the 21st century. \n\nThe BSD support in inxi is a slowly evolving process. Evolving in the strict \ntechnical sense of evolutionary fitness, following fitness for purpose, that is \n(like OpenBSD's focus on security and high quality code, for instance), not as \nin progressing forwards. Features are being added as new data sources and types \nare discovered, and others are being dropped, as prior data sources degenerate \nor mutate to a point where trying to deal with them stops being interesting. \n\nOnce it starts growing evident that a particular branch has hit a dead end and \nno longer warrants the time required to follow it to its extinction, support \nwill be reduced to basically maintenance mode. In other words, inxi follows this \nevolutionary process, and does not try to revive dead or dying branches, since \nthat's a waste of time.\n\nNote that due to time/practicality constraints, in general, only the original \nBSD branches will be supported: OpenBSD+derived; FreeBSD+derived; NetBSD+derived \n(in that order of priority, with a steep curve down from first to last). With \nthe caveat that since it's my time being volunteered here, if the BSD in \nquestion has basically no users, or has bad tools, or no usable tools, or \ninconsistent or unreliable tools, or bad / weak data, or, worst, no actual clear \nreason to exist, I'm not willing to spend time on it as a general rule. \n\nOther UNIX variants will generally only get the work required to make internal \nBSD flags get set and to remove visible output errors. I am not interested in \nthem at all, zero. They are at this point basically historical artifacts, of \ninterest only to computer museums as far as I'm concerned.\n\n--------------------------------------------------------------------------------\nTRUE BSDs \n--------------------------------------------------------------------------------\n\nAll BSD issue reports unless trivial and obvious will require 1 of two things:\n\n1. a full --debug 21 data dump so I don't have to spend days trying to get the \ninformation I need to resolve the issue, file by painful file, from the issue \nposter. This is only the start of the process, and realistically requires 2. to \ncomplete it.\n\n2. direct SSH access to at least a comparable live BSD version/system, that is, \nif the issue is on a laptop, access has to be granted to the laptop, or a \nsimilar one. \n\nOption 2 is far preferred because in terms of my finite time on this planet of \nours, the fact is, if I don't have direct (or SSH) access, I can't get much \ndone, and the little I can get done will take 10 to 1000x longer than it should. \nThat's my time spent (and sadly, with BSDs, largely wasted), not yours. \n\nI decided I have to adopt this much more strict policy with BSDs after wasting \nuntold hours on trying to get good BSD support, only to see that support break a \nfew years down the road as the data inxi relied on changed structure or syntax, \nor the tools changed, or whatever else makes the BSDs such a challenge to \nsupport. In the end, I realized, the only BSDs that are well supported are ones \nthat I have had direct access to for debugging and testing. \n\nI will always accept patches that are well done, if they do not break GNU/Linux, \nand extend BSD support, or add new BSD features, and follow the internal inxi \nlogic, and aren't too long. inxi sets initial internal flags to identify that it \nis a BSD system vs a GNU/Linux system, and preloads some data structures for BSD \nuse, so make sure you understand what inxi is doing before you get into it.\n\n--------------------------------------------------------------------------------\nAPPLE CORPORATION OSX\n--------------------------------------------------------------------------------\n\nNon-free/libre OSX is in my view a BSD in name only. It is the least Unix-like \noperating system I've ever seen that claims to be a Unix, its tools are mutated, \nits data randomly and non-standardly organized, and it totally fails to respect \nthe 'spirit' of Unix, even though it might pass some random tests that certify a \nsystem as a 'Unix'. \n\nIf you want me to use my time on OSX features or issues, you have to pay me, \nbecause Apple is all about money, not freedom (that's what the 'free' in 'free \nsoftware' is referring to, not cost), and I'm not donating my finite time in \nsupport of non-free operating systems, particularly not one with a market \ncapitalization hovering around 1 trillion dollars, with usually well north of \n100 billion dollars in liquid assetts. \n\n================================================================================\nMICROSOFT CORPORATION WINDOWS\n--------------------------------------------------------------------------------\n\nTo be quite clear, support for Windows will never happen, I don't care about \nWindows, and don't want to waste a second of my time on it. I also don't care \nabout cygwin issues, beyond maybe hyper basic issues that can be handled with a \nline or two of code. inxi isn't going to ruin itself by trying to handle the \nsilly Microsoft path separator \\, and obviously there's zero chance of my trying \nto support PowerShell or whatever else they come up with. \n\nWhile I would consider doing Apple stuff if you paid my hourly full market \nrates, in advance, I would not consider touching Windows for any amount of \nmoney. My best advice there is, fork inxi, and do it yourself if you want it. \nYou'll soon run screaming from the project however, once you realize what a \nnightmare you've stepped into.\n\nIf you are interested in something like inxi for Windows, I suggest, rather than \nforking inxi, you just start out from scratch, and build the features up one by \none, that will lead to much better code.\n\n### EOF ###\n","funding_links":["https://www.paypal.com/donate/?hosted_button_id=77DQVM6A4L5E2","https://liberapay.com/smxi/"],"categories":["HarmonyOS","Perl","Operation System"],"sub_categories":["Windows Manager","GNU/Linux Only"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsmxi%2Finxi","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsmxi%2Finxi","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsmxi%2Finxi/lists"}