Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!convex!central!newstop!eastapps!hinode!geoff From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) Newsgroups: comp.protocols.nfs Subject: Re: PC-NFS 3.5 Filename truncation Message-ID: <6004@eastapps.East.Sun.COM> Date: 7 May 91 22:56:12 GMT References: <1991May4.081455.29048@usenet.ins.cwru.edu> Sender: news@East.Sun.COM Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top) Organization: Sun Microsystems PC-NFS Engineering Lines: 25 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) --