On 06/20/2018 05:53 PM, Gerald B. Cox wrote:
I believe we're missing something fundamental here. If a
program/service etc. requires specific hardware to work
and it can't gracefully handle situations where that hardware is not
present - it shouldn't be a default.
The way to handle this (and other similar situations) is to take away
the default status until it can handle
situations where the hardware doesn't exist. This is systems
programming 101 - and frankly I am a
bit surprised it's a matter of debate.
There is a similar situation with other services, in particular the VM
support services. They are turned on by default, they would fail if not
running on the specific VM, but they are set to be conditional on being
run in that VM. I don't see how that is different than this case.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/PPZ6HHOXFCAQ4LZMVF6XRH2LIBLADZIF/
