KDE Plasma has a very nice and compact way to get system info, in text.
I rewrote that once in bash and extended it a bit, to include more useful things like GPU info, GPU RAM and package manager integration.
It is currently broken.
On Fedora we only have fpaste, which has a complex CLI interface (with the default not being local), takes pretty long and produces a rather huge output for most use cases.
We struggle a bit because of that lack. Could fpaste maybe get an alias to produce more compact, simpler, local output?
So, it takes long when it’s getting repodata—because if the user has not been using their user cache, this needs to be updated.
If we’re happy to get rid of that particular bit (perhaps an --offline option that runs dnf -C or something, or parses the repo files instead of using dnf repolist), it’ll be quicker. The other commands don’t really take much time.
As noted, please file these issues at fpaste and they can be all be worked on. It’s just a python script, so it’s easy to modify.
Looking at the original post, something similar to kinfo, in text format, could be obtained under GNOME by going to the Settings app -> System -> About -> System Details, and from there hitting the Copy button.
Example:
(Disk capacity missing, maybe because the system is virtualized)
I have made some research, and, unfortunately, gnome-control-center doesn’t have CLI output options. Nor did I find anything else GNOME-specific which would bring system information to the CLI.
The closest I have found, and is DE-agnostic, is fastfetch. Unfortunately it is not installed by default on Fedora, however, it has a really small footprint. Can be run without generating logo, with fastfetch -l none.
I’ve never seen that work, including today F40, and I’m even doing the most boring partition layout possible (standard, no home, giant root as ext4).
Someone on QA should probably look at that, especially if they take the time to have a virtualization tag
If we are still talking about the GNOME Settings app (gnome-control-center) displaying disk capacity, it is working for me with a bare metal install on SSD, so I don’t know if it is virtual machine vs bare metal, or rather nvme vs ssd.
The thread seems to evolve in a similar direction as my “kde sysinfo” rewrite.
I just looked for random commands to show the output.
Package manager integration, just checking if the command is available and using $1 as search query, works really well
Software things (most are broken in KDE 6 so I need to rewrite and maybe just use kinfo)
Additional hardware stuff
Disk usage should be BTRFS native.
I think it would make sense to do a more minimal version of fpaste. Maybe by using a set of flags, and likely by contributing there. Anybody good in python?