On Mon, 13 Sep 2004 12:47:20 -0600 Bruce wrote: BS> My second thought was to put it into LM-SENSORS-MIB. That MIB, though BS> appears to be geared specifically to the lm-sensors package for linux.
That is exactly where you should be going. The MIB is not specific to lm-sensors, other than containing the name. If you look at the mib, it's pretty generic. It has tables for temperatures, fans, voltage and misc. BS> So, perhaps a MIB might be in order. (Do I need an RFC for an individual BS> MIB? Maybe I'll be famous yet.) Nope. Anyone can write a MIB. You only need a RFC if you want it to be and internet standard MIB, and then it has to go through the IETF, which I don't thing you want to do. I wouldn't recommend it, anyways. BS> Next problem is that the methodology used to derive the CPU temperature on BS> one specific piece of Sun hardware is different on another piece. The BS> net-snmp code could get really, really messy. Try and find a way to make it nice and generic at the mib level. Maybe a table drive approach. BS> A subsequent problem is that my code may be in violation of Sun's licensing BS> agreement. However, it is based upon .h files found within their published BS> operating system, so presumably the code could be published with Copyright BS> disclaimers similar to those already inserted by Sun's contributing BS> engineers (Hi, guys!!). Are you using documented API calls? As long as you don't have access to proprietary information, are not under a non-disclosure agreement and wrote the code yourself (not copied from copyrighted code), you are probably ok. BS> This may also apply to using my code to populate Sun's MIB. If the MIB is publicly available, they can't stop your from implementing it in an agent. BS> So here's how I see it working so far. I create a binary that works on BS> such-and-such hardware with the appropriate disclaimers (use at your own BS> risk, don't sue me I don't have any money) with a published API. I hope by binary you mean library. BS> 1. Sun may still hate it. They may claim my helper application is BS> affecting their bottom line. Again, if it's your code and a published API, I wouldn't worry about it. BS> 2. The Solaris net-snmp community is reliant upon me (as coder of the BS> helper app) not to get hit by a bus/jitney/taxi/rickshaw/hovercraft. Not if you make it open source. Start your own project on sourceforge. BS> 3. I've only got a limited range of hardware at my disposal. Others may BS> have code to contribute for other platforms but can't because I'm hogging BS> the source to the helper app. See #2. Accept patches. -- Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
