List of required/used utilities

[bp0]

These are binary utilities used by hardinfo via popen or the like.

The Debian package is in parenthesis. Perhaps @tsimonq2 could review the package dependencies of the Debian hardinfo package to make sure that at least those of "Feature Requirements" are available.

Hard Requirements:

• ?

Feature Requirements:

• lsmod (kmod), required for kernel module list
• lspci (pciutils), required for pci device list, and/or gpu device list if gpus use pci
• udisksd (udisks2) for storage information including nvme
  • fallback: lsscsi (lsscsi) may be required for storage device information if /proc/scsi/scsi doesn't exist
• glxinfo, (mesa-utils) required for GLX info
• netstat (net-tools) required for network statistics
• route (net-tools) required for routing table
• fwupdmgr

Optional, gives more information:

• net (samba-common-bin), required for samba info and share list
• locale, required for install locales (language support)
• lsb_release
• xrandr
• xdpyinfo
• dmidecode
• cdrecord
• apcaccess (apcupsd?), UPS information

[mckaygerhard]

umm maybe i must make a "docs" directory, and only points minimal info in README, so split information.. what do you think guys?

[mckaygerhard]

nd that idea works for a jekil automatic page build using the gitlab page features that build a site based on markdonw files.. i think its a better idea..

[lpereira]

It's a good idea -- but you can use a Wiki page for that. Everyone with a GitHub account should be able to edit those. I just enabled it: https://github.com/lpereira/hardinfo/wiki

On Sun, Mar 25, 2018 at 8:58 AM, PICCORO Lenz McKAY < [email protected]> wrote:

nd that idea works for a jekil automatic page build using the gitlab page features that build a site based on markdonw files.. i think its a better idea..

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lpereira/hardinfo/issues/243#issuecomment-375981100, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA6mUBFypnel9bweQBE7DQxFBnbNvX5ks5th76NgaJpZM4Syzmf .

-- Leandro

[mckaygerhard]

uh! wiki now enabled, well in my projects i integrated wiki as submodule git, due each github wiki are a git repo itseflt.. so with this i make 3 things at same time:

1. make the website from the wiki directly in the "docs" directory
2. makes obvously the wiki
3. maintain in sync the documentations and the site, the most important

the number 3 its the most important, avoids duplication of work and mantain in sync all the references

now that the wiki are enable wheantime i will populate.. let me know if something are wrong..

[mckaygerhard]

hi again back, @lpereira wiki for that its duplicate work, if there's already a gh-pages branch that can write markdown files and that files will later be parsed as html with github auto pages builder, that wiki are innecesary due are a duplication of work...

all the site can contain in a great organized structure wiki, doc and hardinfo site place.. i made good works with older project in the past, and recent too.. i can made a example in a fork brand htat builds the place site from the gh-pages .. all you must to do its later after a merge of the respective pull request, made configurations on the github repository that implements the web page from the gh-pages brnd, that's all

a example result rudimentary was:

• https://venenux.github.io/gambasex/

[mckaygerhard]

seems udisk2 are not requirement?

[ocerman]

@mckaygerhard not it is not requirement, it is optional.

[mckaygerhard]

why it's optional?

[ocerman]

It is used as primary method for detecing storage devices , if udisks2 is not present or fails to detect any drivers, hardinfo will use fallback methods to detect storage devices. So hardinfo works without udisks2, but it can provide additional information.

// EDIT: however, fallback methods cannot detect NVMe devices // EDIT2: Well.. we can say it is required if we want to detect NVMe devices

[mckaygerhard]

thanks @ocerman .. now original issue here does not have that info included..

[mckaygerhard]

hi @lpereira and @bp0 , if udisk are need for nvme so what happened with systemd-less linux?

[bp0]

The lsscsi fallback also lists NVMe devices, although doesn't give much information.

Also /sys/class/nvme

[kapsh]

@mckaygerhard systemd-less distros build udisks against eudev. Weird requirement for a feature (as a user I couldn't figure out how nvme disks are different) but not a show-stopper.