X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Wed, 26 Dec 2001 09:55:29 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-Id: <2110-Wed26Dec2001095528+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <200112251724.SAA11359@father.ludd.luth.se> (message from Martin Str|mberg on Tue, 25 Dec 2001 18:24:40 +0100 (MET)) Subject: Re: The deep directory bug References: <200112251724 DOT SAA11359 AT father DOT ludd DOT luth DOT se> 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 > From: Martin Str|mberg > Date: Tue, 25 Dec 2001 18:24:40 +0100 (MET) > > I happen to have a "/dev" directory (because of a make install of > fileutils). If I run "find / -iname 'what-ever'" I get a lot of > "e:/djgpp/bin/find.exe: /dev/one_directory: No such file or directory > (ENOENT)" where one_directory is every directory in the root of the > drive. > > Can this be the cause of the bug regarding deep directory problems? > > Or is it the symptom of it? > > Or is it a new bug? Or an old known one? It's an unfortunate side effect of the special handling of fiel names that begin withj "/dev/": _put_path effectively removes "/dev/" from file names, so DOS tries to look them in the root directory or in the current working directory. We need that to support /dev/FOO where FOO is some DOS device. The problem is that a DOS device can use any name, so we cannot easily know whether what comes after /dev/ is a file or a device. The only way to know that is to usse a DOS function call, which is a no-no inside _put_path. You shouldn't have anything under /dev. > find is straight from the ordinary .ZIP from a simtel.net mirror and > is version 4.1. I suggest to use `locate' instead: it is faster, and won't show you all the bogus files.