On Wed, 4 Jul 2007 17:01:48 +0100 Dave wrote: DS> On 04/07/07, Robert Story <[EMAIL PROTECTED]> wrote: DS> > What about simply shortening the name of the leaf files? i.e. : DS> > DS> > cd agent/mibgroup/snmp-notification-mib/snmpNotifyFilterTable/* DS> > rename snmpNotifyFilterTable sNFT snmpNotifyFilterTable* DS> DS> I wondered about that, but decided against it - for two reasons. DS> DS> a) readability DS> snmpNotifyFilterTable is more meaningful than sNFT
But the parent directory would provide the full name... DS> b) code impact DS> changing the names of files means changing the DS> name of various routines (e.g. the init routine). Ah. ugh. A much stronger argument. DS> > If that's not sufficient, mabye moving the sub-directory? DS> > DS> > cd agent/mibgroup DS> > mv snmp-notification-mib/snmpNotifyFilterTable/ notification/ DS> DS> Why is it necessary to have a separate subdirectory at all? DS> There are only three tables in this particular MIB Ok, what about moving the files up on level from their current directory? I do like having rewrites in *-mib directories.. If you're really keep to eliminate one of the the notification directories, what about moving notification/* to snmp-notification-mib/? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
