[comp.protocols.nfs] PC-NFS 3.5 Filename truncation

jb@falstaff.mae.cwru.edu (Jim Berilla) (05/04/91)

Well, I finally upgraded to version 3.5 and things seem to be running
smoothly, except...

I have a few programs which run on pc's and store data on a mounted
filesystem.  I've been writing to files with names like "mp-100t-910503"
which 3.0.1a handled quite nicely.  Now 3.5 truncates the filename.

Is there any way to turn off the filename truncation?  It's really nice
to do an ls and see which tests have been run without having to look in
each file.  The data is processed on Suns, so I don't have to deal with
the name mapping on the pc's.

Any help would be appreciated.

-- 
      Jim Berilla / jb@falstaff.cwru.edu / 216-368-6776
"My opinions are my own, except on Wednesday mornings at 9 AM,
           when my opinions are those of my boss."

rhoward@msd.gatech.edu (Robert L. Howard) (05/05/91)

jb@falstaff.mae.cwru.edu (Jim Berilla) writes:

>I have a few programs which run on pc's and store data on a mounted
>filesystem.  I've been writing to files with names like "mp-100t-910503"
>which 3.0.1a handled quite nicely.  Now 3.5 truncates the filename.

>Is there any way to turn off the filename truncation?  It's really nice
>to do an ls and see which tests have been run without having to look in
>each file.  The data is processed on Suns, so I don't have to deal with
>the name mapping on the pc's.

I had this problem too.  I called Sun and they supplied a patch to 
the pcnfs.sys file which disables this filename truncation.  Here
it is (hopefully it's cool to post a Sun suuplied patch....)

---------------------Sun supplied patch-----------------------------
Here's a patch that reenables the bug so people can (usually) use long
filenames and get away with it.  Unfortunately because of serialization
this must be done on each pcnfs.sys individually unless they have
copyser:

1. Make a backup copy of pcnfs.sys.

2. Do the following, noting blank lines.  At both addresses there
should be "jz" instructions if you want to unassemble them first:

----------------
debug pcnfs.sys
a a70d
nop
nop

a a74f
nop
nop

w
q
----------------

3. Reboot.
---------------------end Sun supplied patch-------------------------

Hope this helps,
Robert
--
| Robert L. Howard             |    Georgia Tech Research Institute     |
| rhoward@msd.gatech.edu       |    MATD Laboratory                     |
| (404) 528-7165               |    Atlanta, Georgia  30332             |
-------------------------------------------------------------------------
|     "Reality is showing us that perhaps we should do with nuclear     |
|      power the same thing Keloggs is advocating for Corn Flakes -     |
|      Discover it again for the first time." -- John De Armond         |

TOMIII@MTUS5.BITNET (Thomas Dwyer III) (05/06/91)

I would also be very interested in disabling the filename truncation that
version 3.5 does on MS-DOS filenames.  Geoff - how about a switch in config.sys
like the one that allows spaces in filenames?


Thomas Dwyer III                        Email: tomiii@mtu.edu
Network Programmer                             tomiii@mtus5.BITNET
Computing Technology Services           Voice: (906) 487-2110
Michigan Technological University       Fax:   (906) 487-2787

geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) (05/08/91)

You know those Peanuts cartoons where Charlie Brown is standing there
with his mouth wide open screaming AAARGH! (in 36 point bold) while
Lucy gazes at him innocently? That how this question made me feel....

Back in 85-86 when I designed the file name handling I decided
(innocently) to be reasonably lax in what I let through, figuring that
people would do the kinds of things these correspondents described, and
why not let them. Then a year or two later along came a couple of apps
which would sometimes open "averylongfilename" and sometimes "averylon"
(probably depending on some library code) and would expect the same
file to be opened. "After all," it was pointed out, "that's what
happens under DOS, and on Novell, and...." So in 3.5 we "fixed" it, and
promptly broke several other applications. Hence my Charlie Brown
expletive.

Anyway, I'm going to formalize the patch described in the last article
into a configuration switch, or something like that. But be warned,
the default behaviour will be DOS-like (unless Microsoft changes the
rules.....)

Geoff
-- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM)   --
------------------------------------------------------------------------------
--     Sun Microsystems PC Distributed Systems ...                          --
--            ... soon to be a part of SunTech (stay tuned for details)     --