Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!ames!sgi!brendan@illyria.wpd.sgi.com
From: brendan@illyria.wpd.sgi.com (Brendan Eich)
Newsgroups: comp.sys.sgi
Subject: Re: csh and nfs
Summary: Fixed csh on sgi.com
Message-ID: <93230@sgi.sgi.com>
Date: 23 Mar 91 00:26:11 GMT
References: <9103211941.AA28942@masig2.ocean.fsu.edu> <1991Mar22.190717.27233@cs.umn.edu>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 18

In article <1991Mar22.190717.27233@cs.umn.edu>, slevy@poincare.geom.umn.edu (Stuart Levy) writes:
> We see the same problem w/NeXT 1.0. The fault's in the BSDreaddir() code which
> csh uses -- it does directory reads into a 512-byte buffer, which the NeXT NFS
> server could probably handle but doesn't.  It's disappointing NeXT didn't fix
> this in 2.0.  SGI's normal readdir(), used by sh, ls, etc. has a larger buffer
> (4K?) and succeeds.  I'm told by a helpful SGI person that the next major
> release will have a BSDreaddir() with larger buffer, but meanwhile we're stuck
> 
> One thing you might try in the mean time: use tcsh instead of csh.
> I think there are a handful of tcsh binaries up for anonymous FTP on
> tesla.ee.cornell.edu and/or ftp.brl.mil.  We have "tcsh.iris4d-irix3.3.1";
> it *does* successfully glob with the NeXT.

Thanks for summarizing this lingering SGI/NeXT bug.  Those who aren't ready
for tcsh can ftp a fixed csh from sgi.sgi.com:~ftp/sgi/csh.  There's a README
file; you must be running 4D1-3.3 or later.

/be