Ticket #2371 (new enhancement)
Let sensors-detect pick mainboard configuration files from a local database
| Reported by: | khali | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | sensors-detect | Version: | 3.1.0 |
| Keywords: | Cc: |
Description
sensors-detect now detects the mainboard based on DMI data. It could easily check in a local filesystem-based database for a suitable configuration file, and copy that file to /etc/sensors.d if found.
The configuration files could for example live under /usr/share/libsensors/config. There we would have one subdirectory per manufacturer (matching the DMI manufacturer string after normalization), and in each subdirectory, configuration files for each product (again after name normalization.)
We might need to have two top-level subdirectories: by-dmi-system and by-dmi-baseboard, depending on how the mainboard is best identified. I'm not yet sure if this is required or if we can just merge both methods into a single tree for simplicity.
This approach seems a good intermediate point between the current situation (no automatic configuration) and the ideal of an online database fed by users. Ultimately we want an online database, but this is a lot more work and nobody has stepped in to achieve it durably so far. One big benefit of the local storage is that the format can evolve until we are happy with what we have. It will be easier to move to an online database if we know what format it needs to have.
