(from <a href="http://bugzilla.gnome.org/show_bug.cgi?id=347406">Gnome Bugzilla #347406</a>) Although data for acpi thermal zones is exposed through /proc/acpi, and potentially sysfs in the near future, it is not currently being exposed in HAL. We'd like to rectify that... <blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><pre id="comment_text_8">Looking through the issue some more, it became clear that the first step would be to get a spec drawn up for how these new keys would be added to HAL. Here is a first draft: <a href="http://www.hoodidge.net/development/thermal_zone_v1.html">http://www.hoodidge.net/development/thermal_zone_v1.html </a> Its seperate from the sensors namespace that you created Richard, because in the context of ACPI, a thermal zone is an abstract device, possibly made up of many sensors on many physical devices. I'm especially interested in figuring out how I could clarify the different trip_points. Since there are 7 possible actions, its on the border of being excessive to have them all listed, but the alternative would be to have developers parse the strings to determine the S-level, temperature and action. Additionally, what other methods could be useful? I've been going off of the information on this page: <a href="http://acpi.sourceforge.net/documentation/thermal.html">http://acpi.sourceforge.net/documentation/thermal.html </a> .</pre></blockquote> What do you all think? Whats missing/unclear? Thanks a lot! Stu Hood