dave@tacky.cs.olemiss.edu ("David E. Johnson") (12/10/89)
We have setup a UNIX System V.3 NFS server for our PC applications. However, file mapping between UNIX and DOS filenames is being done wrong. Valid DOS filenames of length 6-8 plus an extension of any length gets mapped as if they are invalid in DOS. Such names as "hostname.exe" get mapped as "hostn~xx". This causes all DOS programs to not be able to run under NFS. When we use a Sun as the server, the mapping is done correctly. Has anyone run across this problem before? If so, is there anything that I can do about it? Thanks in advance for any help you can give me... David E. Johnson ** Title: Systems Programmer Department of Computer Science ** Telephone: (601) 232-7396 The University of Mississippi ** Internet: dave@cs.olemiss.edu 336 Weir Hall ** University, MS 38677 **
BEAME@mcmaster.ca (12/10/89)
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