Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete guidance needed to view the hw-probe command options #164

Open
Ricky-Tigg opened this issue Nov 1, 2023 · 0 comments
Open

Complete guidance needed to view the hw-probe command options #164

Ricky-Tigg opened this issue Nov 1, 2023 · 0 comments

Comments

@Ricky-Tigg
Copy link

OS: Fedora, edition 39.

$ dnf rq --userinstalled hw-probe
hw-probe-0:1.6.5-2.fc39.noarch
$ rpm -ql hw-probe | grep -iE '\.gz$|\.md$'
/usr/share/doc/hw-probe/README.md

Hello. As per the above output, no man-page file is provided, a README file is provided. As it appears from the existing README file, no command options guide is revealed. Executing the main command alone won't reveal yet the command by which these options can be revealed; illustration:

$ hw-probe | awk 'NF'
Hardware Probe 1.6
A tool to probe for hardware, check operability and find drivers
License: LGPL-2.1-or-later OR BSD-4-Clause
Usage: hw-probe [options]
Example: hw-probe -all -upload

Fine, let's play. Do I get lucky while trying as option the commands usually in use in other Linux tools for which a man-page file is provided. Here were my attempts, in this order: first, help; no luck | second, -help; lucky, at last.

That demonstrated if ever needed, the need for a relevant guidance as part of the output resulting from hw-probe. Since "Usage: hw-probe [options]" and "Example: hw-probe -all -upload" are irrelevant as a complete guidance, it is pertinent to remove them from the printing, and replace them by a relevant guidance, typically "Execute 'hw-probe -help' to view the command options.".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant