From: "Cyrus Patel" Organization: Johannes Gutenberg Universitaet To: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Date: Tue, 11 Feb 2003 17:22:22 +0100 MIME-Version: 1.0 Subject: Re: fix for copyrite.c[c]/copyrite.pl CC: djgpp-workers AT delorie DOT com (DJGPP developers) Message-ID: <3E4931A3.2855.C979899C@localhost> In-reply-to: <10302111457.AA01750@clio.rice.edu> References: <3E48E5B7 DOT 27234 DOT C850F28B AT localhost> from "Cyrus Patel" at Feb 11, 2003 11:58:25 AM X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 11 Feb 2003 at 8:57, Charles Sandmann wrote: > > btw, in an NT (2K) VDM however I saw 'file not found' errors for > > stat() when the pathlen > 64. Shouldn't LFNizing have avoided that? > > No, LFN on W2K/XP still have path length limits on the short name > equivalents. It shows how it works under the hood ... Given copyrite.c uses only dir/file names that were obtained with readdir(), isn't it working exclusively in the LFN "name space"? > There is code in DJGPP to work with this - but you must use relative > paths instead of absolute paths when deep in the directory structure. Do you mean relative in the sense that a dirname without a path still needs to be prefixed with a ".\"? If not: copyrite.c uses only relative paths (because it doesn't use glob() ;) chdir(dp->d_name); do_dir(); chdir(".."); > I think the last block should be handled by manual edits, Well, do you have someone in mind who is going to go through and inspect/edit each file manually? :) > especially since it may have modifications copyright DJGPP. > There probably should be a slightly different header to show this. yep. see any BSD-derived source for example. Like netdb.h which has the original regents copyright followed by a DEC/Vixie one, followed by an implementation specific one.