Xref: utzoo comp.unix.i386:6633 comp.unix.wizards:22807 Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!ames!ncar!ico!dougm From: dougm@ico.isc.com (Doug McCallum) Newsgroups: comp.unix.i386,comp.unix.wizards Subject: Re: i386 unix with NFS - getcwd() & /bin/pwd inode problem Message-ID: <1990Jul9.142023.17830@ico.isc.com> Date: 9 Jul 90 14:20:23 GMT References: Reply-To: dougm@ico.ISC.COM (Doug McCallum) Distribution: na Organization: Interactive Systems Corp., Boulder CO Lines: 15 In article denny@tss.com (Denny Page) writes: >When you are in a directory which is mounted via nfs, and the inode of >the current directory is > 65535 (such as on a sun), /bin/pwd reports >"read error in .." Getcwd() uses /bin/pwd to do its work, and as such >doesn't function. Is anyone aware of a fix or a work around for this? This is a difficult problem to work around. AT&T changed internal inode numbers to long's but left the "stat" system call version of the inode number a short. Just changing it and rebuilding the world would solve the problem but would then break every application that comes from somewhere else. Fixes have to be made such that they are compatible with previous systems and systems from other vendors. I expect that some type of fix will be made in a future release of our (ISC) version once we have one which will let the binary work on other systems that don't have the fix.