- switch(nal){
- case TCPNAL:
- /* userspace NAL */
- case IIBNAL:
- case VIBNAL:
- case OPENIBNAL:
- case RANAL:
- case SOCKNAL:
- snprintf(str, PTL_NALFMT_SIZE - 1, "%u:%u.%u.%u.%u,%u",
- (__u32)(id.nid >> 32), HIPQUAD((id.nid)) , id.pid);
- break;
- case QSWNAL:
- case GMNAL:
- case LONAL:
- snprintf(str, PTL_NALFMT_SIZE - 1, "%u:%u,%u",
- (__u32)(id.nid >> 32), (__u32)id.nid, id.pid);
- break;
- default:
- snprintf(str, PTL_NALFMT_SIZE - 1, "?%d? %llx,%lx",
- nal, (long long)id.nid, (long)id.pid );
- break;
- }
- return str;
+ /*
+ * This is an aweful HACK. Basically the problem is on
+ * Catamount, the build system links in liblustre.a to
+ * all the test executables, and at this point its not
+ * clear how to modify the build system to prevent this
+ * from happening. So providing our own call to
+ * _sysio_lustre_init() that does nothing, prevents
+ * liblustre.a from initializing.
+ *
+ * Why is liblustre.a initializing a problem anyway. Well
+ * this main() in this module calls init_obdclass(), as
+ * well as the llite_lib.c's _sysio_lustre_init(). Two
+ * calls to init_obdclass() cause an assertion. Secondly
+ * it doesn't even logically make sense, this is module
+ * does not need lustre file system functionality, it's
+ * just the echo_tester.
+ *
+ */
+ /*lprintf("--> THIS OVERRIDES liblustre.a INITIALIZATION <--\n");*/
+ return 0;