[Nut-upsdev] ups.firmware

Kjell Claesson kjell.claesson at telia.com
Tue Aug 29 15:08:51 UTC 2006


OK
tis 2006-08-29 klockan 11:37 +0200 skrev Arnaud Quette:
> 2006/8/25, Niklas Edmundsson <nikke at acc.umu.se>:
> > 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
> > 'control:00.01 etc is better, since NUT shouldn't die due to
> > moderately long strings ;)
> 
> that suits me fine.
> 

Thanks, Then I go for the 'control:00.01 ...' string.

Regards
Kjell




More information about the Nut-upsdev mailing list