Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!asuvax!ncar!mephisto!mcnc!xanth!abcfd01.larc.nasa.gov!tadguy
From: tadguy@abcfd01.larc.nasa.gov (Tad Guy)
Newsgroups: comp.sys.amiga
Subject: Re: DNet's nfs: and Amiga ka9q
Message-ID: <TADGUY.90Mar28180210@abcfd20.larc.nasa.gov>
Date: 28 Mar 90 23:02:10 GMT
References: <5548@jarthur.Claremont.EDU>
Sender: news@cs.odu.edu
Organization: NASA/Langley Research Center, Hampton, VA
Lines: 28
In-reply-to: bgribble@jarthur.Claremont.EDU's message of 28 Mar 90 18:42:30 GMT

In article <5548@jarthur.Claremont.EDU> bgribble@jarthur.Claremont.EDU (Bill Gribble) writes:
> I've mounted nfs: in my startup-sequence with the following mountlist entry:
> 
>   NFS:    Handler = L:nfs-handler
>           Stacksize = 8000
>           Priority = 5
>           GlobVec = -1
>   #
> 
> This seems to be what I've been told to use, but when I try cd nfs:
> or dir nfs: on the amiga end it just hangs the cli I called from.
> Any advice?

This worked for me using DNet 2.02L -- you don't say which version
you're running, and the MountList entry may be different in 2.14.

Recently posted elsewhere in this newsgroup:
| Note that, at least in 2.02L, the nfs server on the (UNIX host) is
| seriously byte-order dependent.  Unless you add calls to swab() in all
| the right places, it'll only work on machines that use network byte
| order (such as the mc680x0), not on Intel or VAX processors.
| 
| It's also slow.  It was useful when I had my Amiga at ODU and running
| DNet at 19.2kbps, but at 2400bps it isn't too awesome.  It is still
| useful for unpackaging things (like huge warp files), though, and is a
| really good idea...

	...tad