Mike Frysinger wrote: > the libtirpc package is self described as a "standalone package". i wonder > how far that actually goes. wrt NIS, it requires the system C library to > provide NIS functionality or you get a build failure in a few files. would be > nice if libtirpc were usable without any NIS baggage at all. NIS used RPC procedures to communicate. As it stands today NIS is currently using the RPC procedures glibc. In the future there is a very good chance that NIS will start using the RPC procedures in libtirpc especially if IPV6 support is needed... So I'm a bit confused on what you mean by "NIS baggage" in the libtirpc package. steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
