[Nut-upsuser] Belkin F6C1100-UNV

[Eric S. Raymond]

Peter Selinger <selinger at mathstat.dal.ca>:
> Well, the actual driver should print some message at debug level 0
> before croaking. Like "I didn't recognize this UPS; please try
> specifying the vendorid and/or subdriver parameters". I don't think it
> can be handled by upsdrvctl itself, as it can't know why some
> particular driver fails. The bad news is that it has to be done in
> each driver separately.
> 
> Alexander, can you do that?
> 
> Some other drivers, like newhidups, already do such a thing; see e.g. 
> drivers/belkin-hid.c:404-408.

More generally than that: no driver should *ever* croak and die
without emitting an informative message to standard error.  That's
what standard error is *for*!

I think I'm going to join the dev list and raise a little hell over there.
You're talking about fixing one symptom, but there's an underlying 
disease here that needs to be cured.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>