Bug 203638
Summary: | lsusb not included by default | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Suzanne Hillman <shillman> |
Component: | comps | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | Keywords: | Desktop |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-08-24 16:59:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Suzanne Hillman
2006-08-22 19:53:47 UTC
What's the usage case for this, as it's merely an informational tool? Similar to the usage of lspci, I would think. Largely to determine what one's system currently supports for USB (since, for example, many internal card readers are USB-based), as well as being helpful to give additional information for USB which is not yet supported. I'll ask for more information from the person who originally noted that it was missing. (And that would be me ;) There are a wide variety of USB devices that one could plug in, and when they don't work, lsusb is one of the first steps to find out why. (One can generally google the ID info and find more compatibility info/status...) Also, if you want something specific to happen for different USB devices, don't you need the IDs for writing a highly specific udev rule? Yes, although that can be pulled from lshal or similar. Assinging to comps. lusb added as a default for the Base group. |