That's a bsd method, which slipped into inxi, I've replaced that with -r which is the correct syntax, and which will work
on old linux systems as well as new.
Since there is no functional change and only very old installs would ever see the difference, I'm leaving the version number
alone. New tarball as well.
Also added -x option, show shell version number as well. For dash/csh, this uses a hack of getting dpkg version,
which covers many users, but not all, hopefully I can find a universal way to get shell version for dash/csh
fallback for only /etc/SuSE-release present, presents only first line of that file.
Also improved the /etc/os-release handler to include more data if the PRETTY_NAME field is blank.
New tarball as well.
Hexchat bug fix/workaround, worked around dev decision to start popping up a gtk dialogue when running
hexchat -v or --version command.
Now reads the actual user config files, hopefully anyway. Since trusting config files that are in the user
~./hexchat directory for version information is quite unreliable, this is just a quick hack, but that's fine,
inxi is always happy to hack around bad developer ideas to provide the most accurate, or best guess, at the
answer.
is I believe the only one that actually uses this at this point.
Preferred is lsb-release, because that tends to be more accurate.
Note, this may trigger arch derived distro errors, sigh...
in path, ie, /dev/mapper/truecrypt1 for example.
Also fixed some subtle bugs that could in some instances trigger errors on partition label/uuid, not likely, but it could.
via xprop, so that is now moved to full desktop version handling. This requires bypassing the gnome test, which
is a good thing, because the gnome test uses a deprecated method for gnome detection. Still works, but best to
move from it no matter what.
New tarball, new inxi version.
that makes it a bit more readable. New version number, new tarball.
I debated making it one per line default as soon as -x is triggered but will leave it this way for now, with -xx
you get the easier to read single line output in all cases, so that's probably good enough.
ssh'ed into box, and don't remember what dm is running the desktop. Shows N/A if in X if nothing detected, does not show
out of X since could be a headless server.
Updated man page, new tarball.
And if user is logged in as root. The -U procedure for inxi itself will run independently of that.
On completion of inxi download/update, if successful, will do the man page update/install.
And that's that.
Biggest change, totally reworked the man page, now it's much more complete and has a lot more information.
Includes how to run in IRC clients, how to create konversation shortcut for /inxi type start.
Ok, that's it, probably will refine the desktop extra information and maybe add a dm or two more.
Also added in startx detection for when no dm was detected, thanks JavaAtom for that one.
I decided to just add an -xxx option, for extra extra extra data, no output if nothing detected.
No big support issues, and Mint has used inxi by default for a while, so I think it's fine to add this for them.
entrance gdm gdm3 kdm kdm-trinity lightdm lxdm mdm nodm slim wdm xdm
there's been a relative flood of new display managers, and a few more are probably coming, so
it's actually a somewhat useful thing to have this option.
This is also going to close issue 30, which is not going to be further handled due to ratrace
of trying to support various software packages running on the systems.
Also updated man page for that -xx item.
Now RAID works like this:
-b - if no /proc/mdstat, or if no devices found and module is running, show nothing, otherwise show short form as before
-F - if no proc/mdstat, show nothing, if no devices but mdstat and if -xx, show all lines, otherwise show normal
-R - show all messages and missing file/module information so users, particularly sys admins, know right away module
is running even if no devices.
-v 6 and less, like -F. -v 7, like -R run, ie, show all messages.
this gets rid of unneeded line output given that only if you have md_mod running will you have any data for /proc/mdstat
and that module is only running if you have mdraid installed.
Also redid the no data messages for no module state and no devices state to better reflect what is actually happening.
Good adjustment and good cleanup of unneeded output while tightening the actual usability of the specific messages received.
Includes 4 levels, -b shows basic only, -R shows primary info, device id, components, state, and report on drives
-Rx shows more, and triggers a second info line per device with more raid info.
-Rxx also adds more information, and triggers system raid support info and unmounted raid devices line.
-F uses -R now.
And that's that, enough raid stuff for a lifetime.
That would need to be set in the inxi override config file. The page must show only
one line of output, and that last item on that line must be the ip address.
Ok, that's it, not a big deal, but some people may prefer a non smxi ip address page
for whatever reason, so have at it. Or not.
inxi thinks it's a single core cpu, no matter if it's multicpu or multicore.
Using the: cpu cores
value to double check, as a fallback. This seems to work, ie, if cpu cores is listed as 1
but processor count * cpu count is > 1, then clearly the intel reporting bug is in play.
Note that this is NOT an inxi bug, but is a bug in how some intel cpus create their
cpuinfo data, but since intel is a major player, it's worth handling that issue.
Apparently if you pack an array that is global inside a subshell, that does not register on the primary level of bash.
Who knew?
Maintainers, this is a serious bug fix, so updat to 1.7.27 now or the usb cards will not be seen.
Fixing this required using find, so find will have to be added to the recommended apps, but
leaving it off for now until sure this method is the only way to do it.
The earlier used grep method to get the paths did not work, why, I don't know.
This may require redoing the usb path finder logic, we'll see.
This is set dynamically as well. For irc it uses no : except for line starters and item starters, like:
ID: or IF: or 1: and so on. Also made cpu per core clock speed the same, using now 1: instead of (1)
that saves one character too per core, but makes it all the same, consistent.
This also now becomes a user adjustable parameter, via config files, can set irc/console separator character(s)
Ok, bored, now on with the day.
this solves the problem exposed when there is no ipv6 output, and thus the last line used to test for end of record was vanished.
now it's all just treated like ifconfig except a few small differences of which item to slice out.
A case where pcibusid includes the pre- 0000: appeared, that broke the -N pcibus id handling for -n, which made for no output.
Now inxi will just slice off that in the initial lspci creator.
several bug fixes, one quite serious (not caused by inxi, lsusb -v takes 1 minute to run in some releases).
The lsusb bug is very bad, and hopefully someone will report that upstream, at Arch and Debian Sid it's seen.
lsusb -v hangs very badly.
Another bug fix with error output for some unknown reason on using cat on some /sys files for networking.
Layout bug fixes as well.
Package maintainers, this one is a real bug squasher release, thanks.
This required recoding that function, so I also made -i show IPv6 with -x as well. Might as well start getting used to it.
Also fixed and added wrapping for the -i output, that wasn't working right before, now is standardized to other lines.
got rid of that horrible banlist array/function thing, now it's hard coded.
On a dual core system, this saves literally 0.1 seconds on execution, about 10-20% of execution time.
this also fixes a bug that has always existed, which is if you use spaces to replace instead of ''.
Another advantage of this new method it fixes the fact that each and every string character would be considered a match, null replaced with null.
This was due to the fact that each banlist string started with |, ie, it contained a null character in the search pattern... sigh.
This is why we don't use stupid bash tricks, ok people? They hide bugs, and make the code write only.
New internal line character counter implemented, with support for user set line lengths for both irc and console.
More line wrapping added, and some fine tuned. Also wraps -A now, and adds alsa information to end of first line as well if > 1 card and less than line length max
fixed a bug with remote mounted partitions, created line length counter function that cleans off color code characters to allow for accurate
line counts for line breaks.
Removed legacy print code, repeated code blocks for single/multiple cards, for audio/network.
Made also always print out whether or not a card is present, since you can have alsa without having a card.
This actually shortened inxi for once, and simplified some legacy methods that were totally unnecessary and just complicated the print functions, now all print
functions use the same for loop print out methods on arrays.
Optimized graphics driver function massively, knocked off about 60% of execution time by switching to a single read through via
gawk..
In terms of dual core system, that saved literally about 1 second execution total time.
new option: --recommends
This lets users check their system for all the required/recommended apps, and also shows any missing core directories,
with an explanation of what each item does.
Also prints out a list of distro packages that should help users install the missing package.
So far only debian/ubuntu and arch linux lists are done.
Adjusted the 2-5 options to include the various new features that have been added recently.
Got rid of the entire old way of using verbosity level numbers internally in the script to trigger events, now all those printout
triggers are done via clearly named global switch variables which are set in the initial Option selector function only.
This should not make any particular difference to users, but it makes it easier to read the printout logic code, and to see what
full/basic/verbosity level output actually is going to do.
Also changed -d to -b, and added an error handler to -d showing it's been deprecated.
-d will be needed in the future for advanced -D data, probably cd/dvd etc, and I want to keep the consistency, as much as possible,
that is, m will be advanced M data, p is advanced P, n is advanced N, and so on.
I know this breaks some people's habits, but I think with the deprecated option warning/error, it should be fine, and it's
best to get this done now than to wait until inxi actually is going to use the -d advanced disk option.
Ok, that's it, just basically a code clean up version.
Also if > 0, will show added to display version, like: 1.6.3-4
I've found that google svn from googlecode isn't propagating the data across its data centers quickly or consistently
which makes testing and debugging a real pain in the butt when dealing with people in different geographical areas.
Now we'll be able to confirm that you have dev version xx, ie, the latest uploaded, without doing pointless primary
version number bumps.
When patch number is 00, no display occurs, but it still shows on updating via -U
New feature: -m, with -xx as optional extra extra data
-m shows system, mobo, bios, and with -xx, chassis, if present.
Will also try to guess at if it's a laptop.
Added debugger option, data collector -@ 14, all data.
Fixed long time logging bug, arrays were't writing out in quotes, have to extract out of quotes then send to logger.
Added 802.11 to usb nic/wifi card detection strings.
Updated help menu more to be more readable, and corrected some errors there too.
Improved loaded/unloaded/failed output for gfx driver, now lists them by categor, ie: loaded: ati,radeon unloaded: fbdev
This is because of the high count of loaded/unloaded drivers some systems show, especially for radeon/ati card types.
Added logging for inxi in debugger data collector, and include now the log file, that should be of use.