X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10112252310.AA16943@clio.rice.edu>
Subject:	Re: The deep directory bug
To:	djgpp-workers AT delorie DOT com
Date:	Tue, 25 Dec 2001 17:10:44 -0600 (CST)
Cc:	ams AT ludd DOT luth DOT se
In-Reply-To:	<200112251724.SAA11359@father.ludd.luth.se> from "Martin Str|mberg" at Dec 25, 2001 06:24:40 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> 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?

No, that was found to be an issue with the short name being over
64 characters long (which are illegal in true DOS).  

> Or is it the symptom of it? 
> Or is it a new bug? Or an old known one?

This would be completely separate.  I suspect it's a byproduct of our
special handling of the /dev device.

ls -l /dev does show interesting stuff if /dev directory exists - all 
the files in the root directory (and none of the files in /dev).

ls -lR on /dev appears to have even more interesting things,
like /dev/dev in them (even when /dev is empty).

(above are using ls from Andrew's refresh).  I always thought the 
rule for /dev in DJGPP was "don't do that".

- Raw text -