X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200112261227.NAA13449@father.ludd.luth.se>
Subject:	Re: The deep directory bug
In-Reply-To:	<2110-Wed26Dec2001095528+0200-eliz@is.elta.co.il> from Eli Zaretskii at "Dec 26, 2001 09:55:29 am"
To:	djgpp-workers AT delorie DOT com
Date:	Wed, 26 Dec 2001 13:27:11 +0100 (MET)
X-Mailer:	ELM [version 2.4ME+ PL54 (25)]
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

According to Eli Zaretskii:
> > From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
> > 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.
> 
> 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.

Ok. Then I suggest we leave /dev in place (as DOZE devices is present
in every directory) and add the /dev directory to djdev*b.zip or every
*b.zip. Or create it some other way.


Right,

						MartinS

- Raw text -