Hi, I know nothing about the background to the mail below, but if it's of any help, macfanctld uses the following hardwired paths, reading: /sys/devices/platform/applesmc.768/temp<n>_input and writing: /sys/devices/platform/applesmc.768/fan1_min /sys/devices/platform/applesmc.768/fan2_min /sys/devices/platform/applesmc.768/fan1_manual /sys/devices/platform/applesmc.768/fan2_manual If any of those are to be broken, please advice in advance so i can update the source before you break it, avoiding that the users fry their MacBooks. Thanks, Mike -- Mikael StrÃm <mikael@xxxxxxxxxxx> On Sat, 2010-12-18 at 12:57 +0100, Henrik Rydberg wrote: > On Sat, Dec 18, 2010 at 12:29:52PM +0100, Julien BLACHE wrote: > > "Henrik Rydberg" <rydberg@xxxxxxxxxxx> wrote: > > > > Hi, > > > > >> Which applications? libsensors-based applications definitely don't > > >> hard-wire anything. > > > > > > The ones I am thinking of are pommed and macfanctld, there are > > > probably others. The sysfs nodes have been around a while, so it is > > > not really surprising. If there is a policy saying it is ok to break > > > userspace in this case, that's fine. > > > > I've just changed pommed to probe for applesmc through /sys/class/hwmon, > > so you can go ahead and break it as far as I'm concerned :) > > Great, thanks Julien. And macfanctld should not be a problem either (ccing the author). > > Henrik > _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
