Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bryan From: bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End) Newsgroups: comp.sys.amiga Subject: Re: DNet's nfs: and Amiga ka9q Message-ID: <468@mohawk.cs.utexas.edu> Date: 29 Mar 90 00:22:41 GMT References: <5548@jarthur.Claremont.EDU> Reply-To: bryan@cs.utexas.edu Organization: Spam Detection & Removal Squad, Austin, TX Lines: 44 Spam-Content: Negligible In article <5548@jarthur.Claremont.EDU> bgribble@jarthur.Claremont.EDU (Bill Gribble) writes: =- =-I know there have been several DNet nfs questions recently, but I'm not =- afraid to add another one: =- =-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? =- Try this: NF0: Handler = l:nfs-handler Stacksize = 6000 Priority = 0 GlobVec = 1 # This is the mountlist entry that is included in the latest version of DNet on ucbvax. More importantly, make sure you have the latest version of nfs-handler, if you're using a recent version of DNet (i.e. 2.1x). It appears that something has changed in the code for snfs that breaks older versions of nfs-handler. I had the same symptoms you are seeing until I replaced both the mountlist entry and nfs-handler simultaneously. By the way, I'm always seeing comments like "This seems to be what I've been told to use," or "There isn't any documentation for DNet client xxxx." Don't people get the entire distribution when they install DNet? Where are these partial distributions coming from? Or is it that people just don't R TFM? +++++++++++ On another note, has anyone been able to get through to Matt on overload? I've been getting bouncing mail for three months using the path apple!spooge!overload!dillon, which is the only path our pathalias stuff knows about.