kevin@cfctech.cfc.com (Kevin Darcy) (08/29/90)
I have a bizarre question concerning RFS, etc. on 3B2's. In the past, we have shared space between partitions of our LAN'ed machines by using the loopback feature of RFS. Works like a charm. Now, we have a need to do the same thing on _non-networked_ machines, and that seems to present some problems. According to TFM, it appears that one shalt have a Transport Provider when attempting to bring up RFS, since RFS uses the services of listeners, etc. Obviously, we have no Transport Provider, and in theory at least, have no NEED of one, since (I'm making some perhaps-incorrect assumptions here) the loopback option doesn't actually USE the Transport Provider to move data, and as far as name service is concerned, we can make each machine Primary Name Server for its own little domain. Is there some undocumented way to bring up RFS *without* a Transport Provider given those parameters? Assuming there is not, what would I need to do to create a "dummy" Transport Provider to humor RFS? (Running a listener on /dev/null doesn't work, of course, but it was worth a shot :-). I'm assuming I'd need to create a STREAMS driver, which at least responds positively to SOME of the TLI-related messages through TIMOD or TIRDWR. But what is the minimum set necessary to fool listeners into thinking that there is a real Transport Provider out there? Any help would be greatly appreciated. ------------------------------------------------------------------------------ kevin@cfctech.cfc.com | Kevin Darcy, Unix Systems Administrator ...sharkey!cfctech!kevin | Technical Services (CFC) Voice: (313) 948-4863 | Chrysler Corporation Fax: (313) 948-4975 | 27777 Franklin, Southfield, MI 48034 ------------------------------------------------------------------------------