Inxi

README for inxi - a command line system information tool

The new faster, more powerful Perl inxi is here! File all issue reports with the master branch. All support for versions prior to 3.0 is now ended, sorry.

Make sure to update to the current inxi from the master branch before filing any issue reports. The code in pre 2.9 versions literally no longer exists in inxi 3. Bugs from earlier versions cannot usually be solved in the new version since the pre 2.9 and the 2.9 and later versions are completely different internally.

---

CODEBERG SOURCE REPO

Packagers: Make sure to change your package URLs and repos to use codeberg.org.

The previous inxi-perl, tarballs, and docs branches are now standalone repos on codeberg.org:

docs > https://codeberg.org/smxi/inxi-docs master inxi-perl > https://codeberg.org/smxi/pinxi master master > https://codeberg.org/smxi/inxi master tarballs > https://codeberg.org/smxi/inxi-tarballs master

inxi-perl has been rebuilt and now only contains the pinxi, pinxi.1 files, plus a minimal README.txt for github users. docs and tarballs have been deleted. The inxi-perl branch should not be used, and exists only so that current pinxi users can update from there to get the new version with new URLs.

inxi master and inxi-perl/pinxi will be mirrored until late 2023, then they will no longer get updates.

The inxi repo only contains master, plus the one, two branches, which are obsolete.

---

Please file issue reports or feature requests at:

https://codeberg.org/smxi/inxi

Please take the time to read this helpful article from the Software Freedom Conservancy:

https://sfconservancy.org/GiveUpGitHub/

Any use of this project's code by GitHub Copilot, past or present, is done without my permission. I do not consent to GitHub's use of this project's code in Copilot.

---

DONATE

Help support the project with a one time or a sustaining donation.

Paypal: https://www.paypal.com/donate/?hosted_button_id=77DQVM6A4L5E2

LiberaPay (sustaining donations): https://liberapay.com/smxi/

================================================================================ DEVELOPMENT AND ISSUES

Make inxi better! Expand supported hardware and OS data, fix broken items!

---

HELP PROJECT DEVELOPMENT! SUBMIT A DEBUGGER DATASET

This is easy to do, and only takes a few seconds. These datasets really help the project add and debug features. You will generally also be asked to provide this data for non trivial issue reports.

Note that the following options are present:

1. Generate local gz'ed debugger dataset. Leaves gz on your system: inxi version >= 3: inxi --debug 20
2. Generate, upload gz'ed debugger dataset. Leaves gz on your system: inxi version >= 3: inxi --debug 21
3. Generate, upload, delete gz'ed debugger dataset: inxi version >= 3: inxi --debug 22

You can run these as regular user, or root/sudo, which will gather a bit more data, like from dmidecode, and other tools that need superuser permissions to run.

ARM (plus MIPS, SPARC, PowerPC) and BSD datasets are particularly appreciated because we simply do not have enough of those.

---

FILE AN ISSUE IF YOU FIND SOMETHING MISSING, BROKEN, OR FOR AN ENHANCEMENT

inxi strives to support the widest range of operating systems and hardware, from the most simple consumer desktops, to the most advanced professional hardware and servers.

The issues you post help maintain or expand that support, and are always appreciated since user data and feedback is what keeps inxi working and supporting the latest (or not so latest) hardware and operating systems.

See INXI VERSION/SUPPORT/ISSUES/BUGS INFORMATION for more about issues/support.

See BSD/UNIX below for qualifications re BSDs, and OSX in particular.

================================================================================ SOURCE VERSION CONTROL

inxi: REPO: https://codeberg.org/smxi/inxi MAIN BRANCH: master DEVELOPMENT BRANCHES [not used]: one, two

pinxi [development version for inxi]: REPO: https://codeberg.org/smxi/pinxi MAIN BRANCH: master

pinxi is the standalone development version of inxi. inxi branches one, two are rarely if ever used. inxi 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 various user systems.

Please: NEVER even think about looking at or using previous inxi commits, previous to the current master version, as a base for a patch. If you do, your patch / pull request will probably be rejected.

PULL REQUESTS: Please talk to me before starting to work on patches of any reasonable complexity. inxi is hard to work on, and you have to understand how it works before submitting patches, unless it's a trivial bug fix. Never work with inxi master, always work with pinxi master, since it can be quite far ahead of inxi. inxi master has only one purpose, to get updated to next inxi when pinxi is ready to be copied over to inxi. pinxi is always equal to or ahead of master branch inxi.

Man page updates, doc pages updates, etc, of course, are easy and will probably be accepted, as long as they are properly formatted and logically coherent.

When under active development, pinxi releases early, and releases often. inxi is stable and is generally only updated when a new tagged version is completed.

PACKAGERS: inxi has one and only one 'release', and that is the current tagged version in the master branch (plus pinxi repo, of course, but pinxi should in general not be packaged).

---

MASTER BRANCH

This is the only supported branch, and the current latest commit/version is the only supported 'release'. There are no 'releases' of inxi beyond the current commit/version in master. All past versions are not supported.

git clone https://codeberg.org/smxi/inxi --branch master --single-branch

OR direct fast and easy install:

wget -O inxi https://codeberg.org/smxi/inxi/raw/master/inxi

OR easy to remember shortcut (which redirects to codeberg.org):

wget -O inxi https://smxi.org/inxi wget -O inxi smxi.org/inxi

NOTE: There are no 'Releases' per se. There are only tagged commits, period. A tag is a pointer to a commit, and has no further meaning. A tagged commit however is the target for packagers.

If your distribution has blocked -U self updater and you want a newer version:

Open /etc/inxi.conf and change false to true: B_ALLOW_UPDATE=true

---

SPECIAL NOTE FOR LEGACY OPERATING SYSTEMS WITH NO TLS 1.2 OR GREATER: Modern web servers are dropping support for TLS 1.0, 1.1, and so has smxi.org, this means to install inxi onto an older system with only TLS 1.0 or 1.1 available, you will need to do this to install inxi onto the old system:

wget -O /usr/local/bin/inxi ftp://ftp.smxi.org/outgoing/inxi

then update inxi/man pages after that with inxi -U 4, which uses FTP, not HTTP, to download the file.

For pinxi, just change inxi to pinxi above (add --man to get the man page), and it will work the same.

---

DEVELOPMENT VERSION (in pinxi repo)

All active development is done in the pinxi repo master branch.:

git clone https://codeberg.org/smxi/pinxi

OR direct fast and easy install:

wget -O pinxi https://codeberg.org/smxi/pinxi/raw/master/pinxi

OR easy to remember shortcut (which redirects to codeberg.org):

wget -O pinxi https://smxi.org/pinxi wget -O pinxi smxi.org/pinxi

Once new features have been debugged, tested, and are reasonably stable, pinxi is copied to inxi in the inxi master branch.

It's a good idea to check with pinxi if you want to make sure your issue has not been corrected, since pinxi is always equal to or ahead of inxi.

See SPECIAL NOTE FOR LEGACY OPERATING SYSTEMS above to install pinxi on very old operating systems with out of date TLS version.

---

LEGACY INXI (in inxi-legacy repo)

If you'd like to look at the Gawk/Bash version of inxi, you can find it in the inxi-legacy repo, as binxi in the /inxi-legacy directory:

Direct fast and easy install:

wget -O binxi https://codeberg.org/smxi/inxi-legacy/raw/master/binxi

OR easy to remember shortcut (which redirects to codeberg.org):

wget -O binxi https://smxi.org/binxi

This version will not be maintained, and it's unlikely that any time will be spent on it in the future, but it is there in case it's of use or interest to anyone.

This was kept for a long time as the inxi-legacy branch of inxi, but was moved to the inxi-legacy repo 2021-09-24.

================================================================================ SUPPORT INFO