aboutsummaryrefslogtreecommitdiffstats
path: root/inxi.1
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@ubuntu.com>2017-07-08 00:20:43 -0400
committerLibravatarUnit 193 <unit193@ubuntu.com>2017-07-08 00:20:43 -0400
commit4899534a5cd63704242f4703ef6f8b12f9a2b7e2 (patch)
tree73005575d3f73bd970da786b861de314fbfe9fa4 /inxi.1
parent052cce0c187b13923516adbdcaa7168d858fce20 (diff)
downloadinxi-4899534a5cd63704242f4703ef6f8b12f9a2b7e2.tar.bz2
inxi-4899534a5cd63704242f4703ef6f8b12f9a2b7e2.tar.xz
inxi-4899534a5cd63704242f4703ef6f8b12f9a2b7e2.tar.zst
New upstream version 2.3.23upstream/2.3.23
Diffstat (limited to 'inxi.1')
-rw-r--r--inxi.184
1 files changed, 61 insertions, 23 deletions
diff --git a/inxi.1 b/inxi.1
index c2cb5ae..d05bbdb 100644
--- a/inxi.1
+++ b/inxi.1
@@ -1,4 +1,4 @@
-.TH INXI 1 "2017\-05\-31" inxi "inxi manual"
+.TH INXI 1 "2017\-06\-29" inxi "inxi manual"
.SH NAME
inxi \- Command line system information script for console and IRC
.SH SYNOPSIS
@@ -103,7 +103,9 @@ matches CPU max speed. If CPU max speed does not match CPU actual speed, shows b
information. See \fB\-x\fR and \fB\-xx\fR for more options.
.TP
.B \-d
-Shows optical drive data. Same as \fB\-Dd\fR. With \fB\-x\fR, adds features line to output.
+Shows optical drive data. Same as \fB\-Dd\fR. With \fB\-x\fR, adds features line to output. Also shows
+floppy disks if present. Note that there is no current way to get any information about the floppy device
+that I am aware of, so it will simply show the floppy id, without any extra data.
\fB\-xx\fR adds a few more features.
.TP
.B \-D
@@ -126,12 +128,15 @@ those arguments in the command, like: \fBinxi \-Frmxx\fR
.B \-G
Show Graphic card information. Card(s), Display Server (vendor and version number), for example:
\fBDisplay Server: Xorg 1.15.1 \fR
-,screen resolution(s), glx renderer, version). At some point Wayland and other display servers
-may be added once enough data has been collected.
+,screen resolution(s), OpenGL renderer, OpenGL core profile version/OpenGL version.
+
+If detected (currently only available if on a desktop: will attempt to show the server type, ie, x11,
+wayland, mir. When xorg is present, its version information will show
+after the server type in parentheses. Future versions will show compositor information as well.
.TP
.B \-h
The help menu. Features dynamic sizing to fit into terminal window. Set script global \fBCOLS_MAX_CONSOLE\fR
-if you want a different default value, or use \fB-y <width>\fR to temporarily override the defaults or actual window width.
+if you want a different default value, or use \fB\-y <width>\fR to temporarily override the defaults or actual window width.
.TP
.B \-\-help
Same as \fB\-h\fR
@@ -161,7 +166,7 @@ Note that \fB\-m\fR uses \fBdmidecode\fR, which must be run as root (or start \f
If memory information was found, and if the \fB\-I\fR line or the \fB\-tm\fR item have not been triggered,
will also print the ram used/total.
-Because dmidecode data is extremely unreliable, inxi will try to make best guesses. If you see \fB(check)\fR after capacity number, you should check it for sure with specifications. \fB(est)\fR is slightly more reliable, but you should still check the real specifications before buying ram. Unfortunately there is nothing \fBinxi\fR can do to get truly reliable data about the system ram, maybe one day the kernel devs will put this data into \fB/sys\fR, and make it real data, taken from the actual system, not dmi data. For most people, the data will be right, but a significant percentage of users will have either wron max module size, if present, or max capacity.
+Because dmidecode data is extremely unreliable, inxi will try to make best guesses. If you see \fB(check)\fR after capacity number, you should check it for sure with specifications. \fB(est)\fR is slightly more reliable, but you should still check the real specifications before buying ram. Unfortunately there is nothing \fBinxi\fR can do to get truly reliable data about the system ram, maybe one day the kernel devs will put this data into \fB/sys\fR, and make it real data, taken from the actual system, not dmi data. For most people, the data will be right, but a significant percentage of users will have either wrong max module size, if present, or max capacity.
.TP
.B \-M
Show machine data. Device, Motherboard, Bios, and if present, System Builder (Like Lenovo).
@@ -170,8 +175,8 @@ may also show bios revision as well as version. \fB\-! 33\fR can force use of \f
Will also attempt to show if the system was booted by BIOS, UEFI, or UEFI [Legacy]. The last one is legacy BIOS boot mode
in a systemboard using UEFI but booted as BIOS/Legacy.
-Device requires either /sys or dmidecode. Note that 'other-vm?' is a type that means it's usually a vm, but inxi
-failed to detect which type, or to positively confirm which vm it is. Primary vm identification is via systemd-detect-virt
+Device requires either /sys or dmidecode. Note that 'other\-vm?' is a type that means it's usually a vm, but inxi
+failed to detect which type, or to positively confirm which vm it is. Primary vm identification is via systemd\-detect\-virt
but fallback tests that should support some BSDs as well are used. Less commonly used or harder to detect VMs may not
be correctly detected, if you get a wrong output, post an issue and we'll get it fixed if possible.
@@ -204,6 +209,8 @@ Shows, if detected: \fB/ /boot /home /opt /tmp /usr /var /var/tmp /var/log\fR. U
.B \-r
Show distro repository data. Currently supported repo types:
+\fBAPK\fR (Alpine Linux + derived versions)
+
\fBAPT\fR (Debian, Ubuntu + derived versions)
\fBPACMAN\fR (Arch Linux + derived versions)
@@ -218,7 +225,7 @@ Show distro repository data. Currently supported repo types:
\fBURPMQ\fR (Mandriva, Mageia + derived versions)
-\fBYUM/ZYPP\fR (Fedora, Redhat, maybe Suse + derived versions)
+\fBYUM/ZYPP\fR (Fedora, Redhat, Suse + derived versions)
(as distro data is collected more will be added. If your's is missing please show us how to get this
information and we'll try to add it.)
@@ -250,7 +257,7 @@ Make sure to have no space between letters and numbers (\fB\-t cm10\fR \- right,
\- cpu only. With \fB\-x\fR, shows also memory for that process on same line.
.TP
.B \-t m\fR
-\- memory only. With \fB\-x\fR, shows also cpu for that process on same line. If the \i-I line is not triggered,
+\- memory only. With \fB\-x\fR, shows also cpu for that process on same line. If the \-I line is not triggered,
will also show the system used/total ram information in the first \fBMemory\fR line of output.
.TP
.B \-t cm\fR
@@ -328,7 +335,7 @@ Examples: \fB\-W 95623\fR OR \fB\-W Boston,MA\fR OR \fB\-W45.5234,\-122.6762\fR
OR \fB\-W bodo,norway\fR.
.TP
.B \-y <integer >= 80>
-This is an absolute width override which sets the output line width max. Overrides \fBCOLS_MAX_IRC\fR / \fBCOLS_MAX_CONSOLE\fR globals, or the actual widths of the terminal. If used with \fB\-h\fR or \fB\-c 94-99\fR, put \fB\-y\fR option first or the override will be ignored. Cannot be used with \fB\-\-help\fR/\fB\-\-version\fR/\fB\-\-recommends\fR type long options. Example: \fBinxi \-y 130 \-Fxx\fR
+This is an absolute width override which sets the output line width max. Overrides \fBCOLS_MAX_IRC\fR / \fBCOLS_MAX_CONSOLE\fR globals, or the actual widths of the terminal. If used with \fB\-h\fR or \fB\-c 94\-99\fR, put \fB\-y\fR option first or the override will be ignored. Cannot be used with \fB\-\-help\fR/\fB\-\-version\fR/\fB\-\-recommends\fR type long options. Example: \fBinxi \-y 130 \-Fxx\fR
.TP
.B \-z
Adds security filters for IP addresses, Mac, location (\fB\-w\fR), and user home directory name. Default on for irc clients.
@@ -367,9 +374,10 @@ The following shows which lines / items get extra information with each extra da
\fB/etc/sudoers\fR (sudo v. 1.7 or newer):
.B <username> ALL = NOPASSWD: /usr/sbin/hddtemp (sample)
+
.TP
.B \-x \-G
-\- Direct rendering status for Graphics (in X).
+\- Direct rendering status for Graphics.
.TP
.B \-x \-G
\- (for single gpu, nvidia driver) screen number gpu is running on.
@@ -383,18 +391,18 @@ The following shows which lines / items get extra information with each extra da
Note that there is no way I am aware of to filter out the deprecated IP v6 scope site/global
temporary addresses from the output of \fBifconfig\fR. \fBip\fR tool shows that clearly.
-\fBip-v6-temporary\fR \- (\fBip\fR tool only), scope global temporary. Scope global temporary deprecated is not shown
+\fBip\-v6\-temporary\fR \- (\fBip\fR tool only), scope global temporary. Scope global temporary deprecated is not shown
-\fBip-v6-global\fR \- scope global (\fBifconfig\fR will show this for all types, global, global temporary,
+\fBip\-v6\-global\fR \- scope global (\fBifconfig\fR will show this for all types, global, global temporary,
and global temporary deprecated, \fBip\fR shows it only for global)
-\fBip-v6-link\fR \- scope link (\fBip\fR/\fBifconfig\fR) \- default for \fB\-i\fR.
+\fBip\-v6\-link\fR \- scope link (\fBip\fR/\fBifconfig\fR) \- default for \fB\-i\fR.
-\fBip-v6-site\fR \- scope site (\fBip\fR/\fBifconfig\fR). This has been deprecated in IPv6, but still exists.
+\fBip\-v6\-site\fR \- scope site (\fBip\fR/\fBifconfig\fR). This has been deprecated in IPv6, but still exists.
\fBifconfig\fR may show multiple site values, as with global temporary, and
global temporary deprecated.
-\fBip-v6-unknown\fR \- unknown scope
+\fBip\-v6\-unknown\fR \- unknown scope
.TP
.B \-x \-I
@@ -452,7 +460,16 @@ Note that \fBvolts\fR shows the data (if available) as: Voltage Now / Minimum De
\- Adds disk serial number.
.TP
.B \-xx \-G
-\- Adds vendor:product ID of each Graphics card.
+\- Adds vendor:product ID of each Graphics card.
+.TP
+.B \-xx \-G
+\- Wayland/Mir only: if found, attempts to show compositor (experimental).
+.TP
+.B \-xx \-G
+\- For free drivers, adds OpenGL compatibility version number if it's available. For nonfree drivers,
+the core version and compatibility versions are the same. Example:
+
+\fB3.3 Mesa 11.2.0 (compat\-v: 3.0)\fR
.TP
.B \-xx \-I
\- Show init type version number (and rc if present).
@@ -496,9 +513,9 @@ Supports most known display managers, like xdm, gdm, kdm, slim, lightdm, or mdm.
\- Automatically uploads debugger data tar.gz file to \fIftp.techpatterns.com\fR.
.TP
.B \-xxx \-B
-\- Adds battery chemistry (like: \fBLi-ion\fR), cycles (NOTE: there appears to be a problem with the Linux kernel
+\- Adds battery chemistry (like: \fBLi\-ion\fR), cycles (NOTE: there appears to be a problem with the Linux kernel
obtaining the cycle count, so this almost always shows \fB0\fR. There's nothing that can be done about this glitch, the
-data is simply not available as of 2016-04-18), location (only available from dmidecode derived output).
+data is simply not available as of 2016\-04\-18), location (only available from dmidecode derived output).
.TP
.B \-xxx \-m
\- Memory bus width: primary bus width, and if present, total width. eg: bus width: 64 bit (total: 72 bits). Note that total / data widths are mixed up sometimes in dmidecode output, so inxi will take the larger value as total if present. If no total width data is found, then inxi will not show that item.
@@ -527,6 +544,27 @@ Turns on hostname in System line. Overrides inxi config file value (if set): B_S
.TP
.B \-! 33
Force use of \fBdmidecode\fR. This will override \fB/sys\fR data in some lines, like \fB\-M\fR.
+.TP
+.B \-! 34
+Skip SSL certificate checks for all downloader actions (\fB\-U\fR, \fB\-w\fR, \fB\-W\fR, \fB\-i\fR).
+Use if your system does not have current SSL certificate lists, or if you have problems making a connection for
+any reason. Only works with \fBwget\fR, \fBcurl\fR, and \fBfetch\fR. This must go before the other options you use.
+
+.TP
+.B \-! 40
+Will try to get display data out of X (does not usually work as root user).
+Default gets display info from display \fB:0\fR. If you use this format: \fB\-! 40:1\fR it
+would get it from display \fB1\fR instead, or any display you specify
+as long as there is no space between \fB\-! 40\fR and the \fB:[display id]\fR.
+
+Note that in some cases, \fB\-! 40\fR will cause inxi to hang endlessly when running the option
+in console with Intel graphics (confirmed). Other free drivers like nouveau/ati unknown yet.
+It may be that this is a bug with the intel graphics driver, more information required.
+
+You can test this easily by running this command out of X/display server: \fBglxinfo -display :0\fR
+
+If it hangs, \fB\-! 40\fR will not work.
+
.SH DEBUGGING OPTIONS
.TP
.B \-%
@@ -607,7 +645,7 @@ Then you can start inxi directly, like this:
Newer (2014 and later) WeeChats work pretty much the same now as other console IRC
clients, with \fB/exec \-o inxi \fR[\fBoptions\fR]. Also, newer WeeChats have dropped
-the \fB\-curses\fR part of their program name, ie: \fBweechat\fR instead of \fBweechat-curses\fR.
+the \fB\-curses\fR part of their program name, ie: \fBweechat\fR instead of \fBweechat\-curses\fR.
Deprecated:
@@ -646,7 +684,7 @@ exists, it will go there, and as a last default, the legacy location is used:
See wiki pages for more information on how to set these up:
.TP
-.I http://smxi.org/docs/inxi-configuration.htm
+.I http://smxi.org/docs/inxi\-configuration.htm
.SH BUGS
Please report bugs using the following resources.
@@ -673,7 +711,7 @@ is is a fork of locsmif's largely unmaintained yet very clever, infobash script.
Original infobash author and copyright holder:
Copyright (C) 2005\-2007 Michiel de Boer a.k.a. locsmif
-inxi version: Copyright (C) 2008\-16 Harald Hope
+inxi version: Copyright (C) 2008\-17 Harald Hope
Initial CPU logic, konversation version logic, and occasional
maintenance fixes: Scott Rogers