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.
