Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!rhorn@seismo.CSS.GOV@infinet.UUCP From: rhorn@seismo.CSS.GOV@infinet.UUCP (Rob Horn) Newsgroups: mod.protocols.tcp-ip Subject: Re: Need information on NFS Message-ID: <8612232001.AA29359@infinet.UUCP> Date: Tue, 23-Dec-86 15:01:06 EST Article-I.D.: infinet.8612232001.AA29359 Posted: Tue Dec 23 15:01:06 1986 Date-Received: Wed, 24-Dec-86 05:40:32 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 8 Approved: tcp-ip@sri-nic.arpa I think that the reason PC-NFS is client only has much more to do with the extreme difficulty in setting up any kind of server under MSDOS than it has to do with the NFS protocol. MSDOS is just not suitable for multi-tasking. It only understands one process plus N interrupt service routines. Any server must act as an interrupt service routine, and be subject to the associated restrictions, if it is to coexist with other applications. This also explains why other vendors of ftp and telnet also provide client only versions for MSDOS.