minfo --output json --category cpu,memory Example JSON snippet:
Minfo is not the fastest on raw execution (neofetch wins), but it offers the best balance of features and low resource consumption. Issue: minfo: command not found Solution: Ensure the binary is in your PATH . Reinstall via package manager or manually symlink: minfo 1.0.2
"cpu": "model": "AMD Ryzen 7 5800X", "cores": 16, "threads": 16, "bogomips": 7985.29 , "memory": "ram_total_mb": 32768, "ram_used_mb": 12288 Example script: Whether you are troubleshooting a kernel
ssh user@remote "minfo --category all --output compact" Prometheus exporters can call Minfo and convert its JSON to metrics. Example script: Unlike bloated GUI-based system monitors
Whether you are troubleshooting a kernel panic, auditing a remote server, or simply curious about the silicon beneath your operating system, Minfo 1.0.2 promises a streamlined, scriptable solution. This article unpacks everything you need to know about version 1.0.2: its core features, installation methods, command-line usage, real-world applications, and why this specific release matters. Minfo—short for "Machine Information"—is a command-line utility designed to harvest and display critical hardware and software metrics. Unlike bloated GUI-based system monitors, Minfo operates entirely in the terminal, returning clean, parseable output.
Hostname: dev-laptop OS: Ubuntu 24.04 LTS (Kernel 6.5.0-14-generic) CPU: 12th Gen Intel Core i7-1260P (16 cores) RAM: 15.2 GiB total | 6.1 GiB used | 8.9 GiB free Main Disk: /dev/nvme0n1 | 512 GB (74% free) For scripting and automation, use --output json :
minfo --category memory,storage | grep -E "Free|Available" Build a custom Conky or Rainmeter widget that parses minfo --output yaml for minimal resource usage. 4. Remote Diagnostics over SSH When a client reports a slow machine, a single command gives you the full picture: