[Nut-upsdev] ups.firmware
Niklas Edmundsson
nikke at acc.umu.se
Fri Aug 25 07:41:32 UTC 2006
On Thu, 24 Aug 2006, Peter Selinger wrote:
> Another possibility is to let the driver construct a compound firmware
> string. How about ups.firmware = 'c:00.01 i:01.10 r:02.00 n:00.10
> d:02.00'? The firmware variable is an opaque string anyway, and as
> far as I know, there is no restriction on its formatting. Is there a
> reason why the driver shouldn't synthesize this string?
I'd go with the compound string. The firmware version is only for
informational purposes anyway, and by going the compound-string-route
you don't have to create firmware.usb, firmware.snmp, firmware.io and
whatever might be present in all different upsen.
IMHO you don't have to cryptify the string though. 'control:00.01
interface:01.10' etc is better, since NUT shouldn't die due to
moderately long strings ;)
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke at acc.umu.se
---------------------------------------------------------------------------
Norm: "I'm the ideal weight for someone 10 feet tall."
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
More information about the Nut-upsdev
mailing list