dmitriy.kazimirov/inxi
1
0
Fork 0
mirror of https://github.com/smxi/inxi.git synced 2025-09-01 18:19:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

readme edit

Browse source
This commit is contained in:
Harald Hope 2018-10-03 13:18:37 -07:00
parent 8c36c8b695
commit 8958850fb8
1 changed files with 5 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.txt
View file

@ -247,15 +247,11 @@ If you are piping output to paste or post (or writing to file), inxi now
automatically turns off color codes, so the old suggestion to use -c 0 to turn automatically turns off color codes, so the old suggestion to use -c 0 to turn
off colors is no longer required. off colors is no longer required.
inxi should always show you your current system state, as far as possible, and inxi strives to be as accurate as possible, but some things, like memory/ram
should be more reliable than your own beliefs about what is in your system, data, rely on radically unreliable system self reporting based on OEM filling
ideally. In other words, the goal in inxi is to have it be right more than it out data correctly, which doesn't often happen, so in those cases, you want
is wrong about any system that it runs on. And not to rely on non current to confirm things like ram capacity with a reputable hardware source, like
system state data if at all possible. Some things, like memory/ram data, rely crucial.com, which has the best ram hardware tool I know of.
on radically unreliable system self reporting based on OEM filling out data
correctly, which doesn't often happen, so in those cases, you want to confirm
things like ram capacity with a reputable hardware source, like crucial.com,
which has the best ram hardware tool I know of.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
COMMITMENT TO LONG TERM STABILITY COMMITMENT TO LONG TERM STABILITY