2009/9/2 Charles Lepple <[email protected]> > On Sep 2, 2009, at 5:33 AM, Arnaud Quette wrote: > > Since this file is not much computed currently (it's mostly useful for >> configuration tools), we can break the format without worrying much. >> > > Sounds good to me. > > We might want to take this opportunity to define a "version=2" header of > some sort, so that in the future, the tools will immediately know whether or > not they are compatible. (At some point, we might want to move to a > key-value format, especially if the information gets too sparse because of > differences between PDUs and UPSes.) >
good idea. I only added a few information in the header, including @PACKAGE_VERSION@ but the version compat is more obvious. I've attached the current draft header for info. Do any Linux distributions do any processing based on that file? > not Debian, and not that I know. the only consumer ATM (to my knowledge) is Opengear. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
# Network UPS Tools - @PACKAGE_VERSION@ - Hardware Compatibility List # version=2 # # This file is used for various purposes, like building the HTML compatibility # list or displaying information in NUT configuration tools. # # If you write a new driver, modify an existing one to add more support, # or just know about some equipment that isn't listed but should be, # please send us a patch to update this file. # # The format: # # <manufacturer> <device type> <support level> <model name> <model extra> <driver [parameters]> # # Details: # - device type: ups, pdu, scd # - support level: a number from "1" to "5" (stars) meaning: # * protocol based on reverse engineering # ** based on fragments of publicly available protocol # *** based on publicly available protocol # **** vendor provided protocol # ***** vendor provided protocol and hardware # - driver [parameters]: mention the driver(s) (separated by "or" if there are # several possibilities. Any mandatory parameter(s) must be referenced, as # they will be parsed by configuration helper softwares. # For example, genericups entries must mention the "upstype=nn" format. # # Duplicate text in the last field will be cooked out during the conversion # to HTML with ROWSPAN magic. They must be an exact match for this to work.
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
