On Fri, 08 Oct 2004 10:31:36 -0700 Michael wrote:
MJS> Modified Files:
MJS> Tag: V5-1-patches
MJS> memory.c MJS> Log Message:
MJS> fix bug#1043197 - provide a function to test os version and release
I don't think this is the right way to do this. I think this should be a configure time test, not a run-time test.
In addition, adding something like this should really be done the right way, which means it should work for more than one platform, and should go through review on coders.
I agree that more discussion is warranted.
I had presented to coders over the past weeks in several messages
a short pronouncement that I believe there were some patches that
RedHat and Debian were applying, which might have a positive effect
on the base source. Two of the items were specific to 2.4 kernel features that were deprecated in the Linux 2.6 kernel.
The net-snmp community probably has a significant number of 2.4 kernels running underneath net-snmp.
Robert, I believe you suggested something that would take the behavior of SO_BSDCOMPAT and the MemShared patches from Fedora and apply them in a kernel appropriate fashion. There isn't anything today that configures for a specific kernel version, nor should there be, within some reason. So I for one do not agree that the decision should be made during configuring of the source.
Although it has an application specific today to Linux, I believe that other platforms support uname, and if they didn't, the netsnmp_os_prematch method is not an altogether bad way to encapsulate that.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
