Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!ucbvax!mcmaster.ca!BEAME
From: BEAME@mcmaster.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: RE: PC-NFS filename mapping problem?
Message-ID: <89Dec9.160356est.57481@ugw.utcs.utoronto.ca>
Date: 9 Dec 89 21:03:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13


We ran into this problem with our BWNFS on the PC and Wollongong NFS
server software. The server sends a zero terminated filename with a length
which is a multiple of 4. Thus for "hostname.exe" the length might be set
to 16. Most Unix boxes would get the name using XDR_STRING which will use
a strncpy to copy the filename. Since the filename is zero terminated, the
correct string will be extracted. PC-NFS might look at the length (16) and
determine that the file needs to be converted. We added a "specification
kludge" to BWNFS to check for the zero termination and we can now handle this
bug in Wollongongs NFS.

        - Carl Beame
        Beame@McMaster.CA