Rene, Thank you for reporting this. I agree that this failure is an unwelcome surprise to those users who upgrade to 2.6.26 but are still using libsensors <= 2.10.6. Jean, Mark, Hans, I'm actually fine with adding a temporary kernel config option along the lines Rene suggested to ease the migration to linux-2.6.26 for those users. But the config option would need to be scheduled for removal after a certain period (say 6 months) so we don't have to maintain it forever. More importantly, I think it would also have to be disabled by default so that it would not have a negative impact on what we think are the majority of properly configured systems. After all, we fixed this bug in user-space about out 4 months ago and as you point out, the distro upgrade path is actually quite well looked after. So I'm not sure how useful it would be to the target users. After they run into the problem, they'd probably google it and find that they can either tweak a kernel config option or upgrade libsensors. And we'd prefer that they do the later rather than the former, yes? just let me know. thanks, -Len -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
