On Thu, Dec 07, 2006 at 05:12:47PM -0500, Woody Suwalski wrote: > Since /dev/temperature is a superset of /dev/temp, it is always using same > major:minor. > Applications (except for fand, this may be fixed) are already using /dev/temp > if /dev/temperature > does not exist. > However I still think that is worth "acenting" that on Netwinder we actually > need an "enhanced" > /dev/temp, which historically was called "dev/temperature". Physically both > are the same (vide > /dev/loop0 and /dev/loop/0). > > The nwutil package can quite easily add the z65_netwinder_temperature.rules > file to > /etc/udev/rules.d, where it will not harm if udev is not installed. > However if you see that "/dev/temperature" name is potentially conflicting > with other > architectures, we may drop the backward compatibility and switch to /dev/temp. > > The manpage has been written in pre-udev times and is supposed to give a hint > to the user, why > the utilities might be not functional...
Thanks for taking the time to explain it to me, that makes a lot of sense to me. I wasn't getting the superset notion. Given the above, I agree with a symlink approach (fwiw, I'd prefer '/dev/nwtemp' over '/dev/temperature', if the additional features are specific to netwinders). However, it would seem more deterministic if the symlink was presented when the necessary features are available, not just when the nwutil package is installed. i.e., the udev rule only comes into effect when the ds1620 driver is loaded. I'm not exactly sure what the best way to implement this would be, my udev foo is pretty basic. I would guess that we'd want to use a rule with a PROGRAM callout that can verify that the added functionality is there. Is there an identifying string in /proc/therm we could use? -- dann frazier | HP Open Source and Linux Organization -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
