[ First - *please* don't mail me directly. Keep discussions on
the list, where others can both learn and offer advice. Thanks. ]
On Wed, 12 Jan 2005 12:22:05 -0800 [EMAIL PROTECTED] wrote:
WC> I have finally completed my analysis of the IF-MIB implementation,
WC> though I now find that it is implemented twice. One set of code is
WC> found in the directory ./agent/mibgroup/if-mib and the other set of
WC> code is found in the directory ./agent/mibgroup/mibII, and this
WC> observation leads me to question.
WC>
WC> 1) Why are these two implementations present?
The if-mib version is a re-write, using the new MFD style code. However, it is
only working on Linux, and thus the previous version was left in place.
Eventually, the mibII version will go away.
WC> 2) How do I include the code in the if-mib directory into the
WC> daemon, as opposed to the code in the mibII directory?
Specify --enable-mfd-rewrites during configure. Again, this will only work on
Linux.
WC> 3) I imagine that Dave Shield wrote the mibII
WC> directory code,
WC> and that you wrote the if-mib code.
I did write the if-mib code (port the Linux portion of the mibII code is more
like it). And the mibII is an amalgam of thw work of many people.
WC> I suspect that the functions prefixed with
WC> *netsnmp*, such as are defined in the files interface_linux.c
WC> and interface_common.c, can be used by my code without
WC> alteration. That is, these are foundation routines, used
WC> to provide basic functionality in maintaining the content
WC> of the fundamental data structures of the MFD method. Are
WC> my suspicions consistent with your view of the MFD method?
Functions with a netsnmp prefix could be in the agent, helper or snmp
libraries. Functions prefixed with mfd or _mfd are in the interface file, or
the helper library.
WC> I am using the Net-SNMP 5.2 release,
WC> and if you provide some instruction regarding acquisition of the
WC> pre1 scripts, I will use them. Use of the CVS tool for obtaining
WC> toolkit components is not something that I am familiar with, and
WC> so I am reluctant to do so without some (at least minimal)
WC> instruction.
If you don't want to use cvs to keep up with local fixes, you can grab the
latest tarball in the files/download section of the web page. If you want to
try CVS, instructions can be found at
http://www.net-snmp.org/cvs/
If you want to follow the main line (what will be 5.3), no branch tag is
needed. If you want to track the 5.2.x release, use the V-5-2-patches branch
tag.
--
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
