On Fri, 30 Dec 2011, Ben Kaduk wrote:
BK>On Fri, Dec 30, 2011 at 5:58 AM, Ulrich Spoerlein <uqs@freebsd.org> wrote:
BK>> Author: uqs
BK>> Date: Fri Dec 30 10:58:14 2011
BK>> New Revision: 228990
BK>> URL: http://svn.freebsd.org/changeset/base/228990
BK>>
BK>> Log:
BK>> Spelling fixes for usr.sbin/
BK>>
[snip]
BK>> Modified: head/usr.sbin/bsnmpd/modules/snmp_wlan/BEGEMOT-WIRELESS-MIB.txt
BK>> ==============================================================================
BK>> --- head/usr.sbin/bsnmpd/modules/snmp_wlan/BEGEMOT-WIRELESS-MIB.txt Fri Dec 30 10:45:00 2011 (r228989)
BK>> +++ head/usr.sbin/bsnmpd/modules/snmp_wlan/BEGEMOT-WIRELESS-MIB.txt Fri Dec 30 10:58:14 2011 (r228990)
BK>> @@ -82,8 +82,8 @@ WlanMgmtReasonCode ::= TEXTUAL-CONVENTIO
BK>> associationLeave(8),
BK>> associationNotAuthenticated(9),
BK>> -- XXX: TODO - FIXME
BK>> - dissasocPwrcapBad(10),
BK>> - dissasocSuperchanBad(11),
BK>> + disassocPwrcapBad(10),
BK>> + disassocSuperchanBad(11),
BK>
BK>This file looks like it might be intended to be machine-readable -- I
BK>would worry about changing it without test/review.
BK>Perhaps this spelling "error" is even the reason for the XXX comment above.
Absolutely. If there is a spelling error in an SNMP MIB outside comments
or description strings it must stay there. Otherwise applications reading
that file will break.
This is also true for the corresponding .def file.
harti