Hi!
I suggest to send out a clear statement to people who expect that broken MIBs should be `somehow usable':
BROKEN MIBS ARE BROKEN! DON'T USE THEM! Get the current MIBs that come with the current NET-SNMP release.
Dave> In this particular situation, it's not the user's fault Dave> that the MIBs are broken.
Ok. But it's the user's fault to upgrade the NET-SNMP release without upgrading the configuration.
Dave> The SMI MIB file (that's now taking down the libSMI parser) was Dave> deliberated emasculated to fit in with the UCD MIB parser. Dave> Yes, I *know* this was the Wrong Thing To Do (though I suspect Dave> it might date back to the underlying CMU code). But we've got Dave> to deal with life as it is, not as we'd like it to be!
Let me give a general blabla statement...
I think, it's for any large and long standing project like NET-SNMP to evolve and to make progress, even if it causes some changes that cause incompatibilties in the first place. If a number of changes go to a new release, it's reasonable to say to the users: ``If you really need compatibility with the old stuff, then keep with the old stuff. If you would like to take advantage of the new stuff, then you have to adapt some things.'' Otherwise, you add another dimension of nasty compatibility overhead with every improvement. Let's put the developers' energy in improvements instead of compatibility.
Dave> We haven't really discussed how we're going to go about shipping Dave> the net-snmp/libSMI combination - and I suppose one approach might Dave> be to ship the two code trees together, and hack in an explicit Dave> warning message, just before that exit. Dave> But I can't say that strikes me as a particularly clean or Dave> acceptable way of dealing with this! Harrie and I are OK for Dave> the moment (now we know what to avoid), so we can think about Dave> this problem at leisure, rather than trying to fix it on the fly.
Sure, I agree shiping NET-SNMP with a patched libsmi wouldn't be what like to have.
I just tried to track down the problem that causes the termination. Can you please send me the module in question?
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.