Skip to content
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.

Home

Jump to bottom
smxi edited this page Nov 30, 2023 · 24 revisions

inxi wiki

The primary documentation for the inxi project has been moved to a permanent stable home: smxi.org/docs/inxi.htm

Because it took way too long to move the googlecode wiki HTML into cleaned up real HTML, and because wiki logic generally is just weak and kind of pathetic in terms of standard web development concepts, I'm not going to support any wiki data beyond this single page, so please do not try to create a standard wiki here.

The following are the resources available for inxi support, help, documentation, etc.

  • Donate to the project, with either a single or a recurring donation. You can donate using Paypal or create a sustaining recurring donation at LiberaPay - Any amount is always welcome, and appreciated.
  • smxi.org inxi documentation - inxi has a lot of stuff going on in it, documentation helps.
  • inxi installation instructions - various install options for inxi. Most distributions have inxi packages, but not all of them update it routinely.
  • inxi options - explanation of the inxi options. This is updated every new master branch release.
  • inxi man page - html version of the inxi man page. This is updated every new master branch release.
  • inxi changelog - html version of the inxi changelog. This is updated every new master branch release. It's very verbose because it's intended to be a complete record of Changes.
  • inxi core mission - useful for potential contributors who might not understand why things in inxi are done the way they are. Covers support for Legacy OS/Hardware, optimizations, and primary philosophy.
  • inxi json/xml output - understanding the json/xml data structures so you can process it. DO NOT ASK ME FOR PROGRAMMING HELP!
  • inxi support forums - post actual discussion type issues here, or use the issues tracker here, makes no difference, except the forum will be way more sticky and visible over time.
  • inxi issue tracker - use the codeberg.org issue tracker/bug reporter to report issues/bugs.
  • inxi IRC support: channel #smxi on irc.oftc.net or irc.libera.chat - sometimes IRC support is faster or more efficient.
  • For git, the following branches and repos are of interest (note: pinxi and inxi support the -U self-updater command for easy updating once installed. one and two would overwrite inxi master version, which is why they are almost never used):
    • master - codeberg.org/smxi/inxi master The master main branch. No other version of inxi than the current one in master is supported, so please upgrade your inxi to current before posting any issue or bug reports. See the installation instructions for how to do that. Devs: use pinxi since that is always either ahead or even with master.
    • one - codeberg.org/smxi/inxi one Alternate rarely used development branch for inxi.
    • two - codeberg.org/smxi/inxi two Alternate rarely used development branch for inxi.
    • pinxi - codeberg.org/smxi/pinxi master (Obsolete: inxi/inxi-perl branch) This is the primary development release. Using pinxi lets you run inxi and pinxi on same system.
    • inxi-docs - codeberg.org/smxi/inxi-docs master (Obsolete: inxi/docs branch) This is the collection of html/css files that you'll find the inxi documentation in at smxi.org.
    • tarballs - codeberg.org/smxi/inxi-tarballs master (Obsolete: inxi/tarballs branch) A weak effort on my part to create a history of inxi. It's a collection of tarballs going back pretty much to the start of inxi, but they are randomly updated, and are NOT a reference point for packagers. They are a reference point for me and for anyone interested in how inxi grew and developed, nothing more.

If you have edits or changes for the smxi.org inxi documentation, you can file an issue here. The pages are in git here for your convenience, but please do not put those live anywhere else or google gets confused about which are the real versions. And please don't turn them into wiki pages elsewhere, people tend to do that once, then it gets stagnant and stale, but google doesn't know which is the real version, so please stick to the real documentation always.

inxi debugging data requests

If you file a bug report, or issue, you will probably be asked to create and upload the inxi data debugger gz file. inxi uploads it automatically when you run the following command: inxi --debug 22

You are probably unlikely to get support in any real way if you are asked to provide this debugger data and don't do it, because the support time is cut by between 10 and 1000 times on our end when the full debugger data is available, so if you won't provide it, we probably won't help you.

Clone this wiki locally