#16160: Shell commands - critical data option
------------------------+-----------------------------------------
Reporter: lelldorin | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: - General | Version: R1/Development
Resolution: | Keywords: Private data, critical data
Blocked By: | Blocking:
Platform: All |
------------------------+-----------------------------------------
Comment (by pulkomandy):
Just don't call the commands which list these. If you stick with listdev
and listusb that's all the info we need in a system analysis tool.
syslogs are sometimes useful in a bugtracker when trying to pinpoint the
exact cause of a problem and fixing it. But that usually takes several
runs of adding extra tracing to the driver, asking the bug reporter to try
again and get more info, until the problem can be identified and solved.
In the case of a hardware database, all we need is the list of hardware,
and the user should report if it works or not, because you can't know this
from the syslog in most cases.
--
Ticket URL: <https://dev.haiku-os.org/ticket/16160#comment:2>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
