We have an application or two that uses Rx directly. Our uniqname system is one of them. I don't know offhand what its requirements are.
> Once all of the other "trunk is completely useless for linux servers > right now" problems are resolved, something I was thinking of working on > (along with my 5 million other projects) is a cleanup of the XDR stuff. > Disabling any non-used stuff would definately be an option here. (Does > ANYONE use Rx directly for anything besides AFS?) > > One of the main things I want to do is to rename all of the functions > and structures to make them distinct to AFS. This will allow fully > prototyping everything xdr without conflicting with the O/S provided > headers and libs. We already use our own xdr libs for everything, might > as well eliminate the naming conflict as well. > > I'd agree though, should probably be fixed or axed. > > -- Nathan > > On Fri, 2003-03-21 at 10:18, Jim Rees wrote: > > [ moving this discussion to openafs-devel ] > > > > Is xdr_mem.o used by anything? It is only linked with the Windows version > > of the code. It makes me nervous to have known bad code in the tree, even > > if it's unused. > > > > Let's either take it out of the tree, or patch it. > > _______________________________________________ > > OpenAFS-devel mailing list > > [EMAIL PROTECTED] > > https://lists.openafs.org/mailman/listinfo/openafs-devel > -- > > ------------------------------------------------------------ > Nathan Neulinger EMail: [EMAIL PROTECTED] > University of Missouri - Rolla Phone: (573) 341-4841 > Computing Services Fax: (573) 341-4216 > > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel > _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
