Date:	Thu, 8 Oct 1998 19:18:06 +0100 (BST)
From:	George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To:	Klaus Peter Wegge <wegge AT c-lab DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: file utilities and X:/dev
In-Reply-To:	<199810081524.RAA29395@narvi.c-lab.de>
Message-ID:	<Pine.OSF.4.05.9810081912410.8902-100000@sable.ox.ac.uk>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Thu, 8 Oct 1998, Klaus Peter Wegge wrote:

> The "cp", "mv", "ls", "mv" ... commands, comming with DJGPP 2.01
> have a funny behaviour.
> Example:
> cp lib*.a ..
> leads to a message:
> d:/djgpp/bin/cp: libtcp.a: No such file or directory (ENOENT)
> 
> It took a long time since I found out it was no good idea to
> name the development directroy "d:\dev".
> There may be some reasons for that behaviour but
> PLEASE PLEASE PLEASE
> tell the users about this knowwn bug/feature at a significant
> place or better:
> put a simple test for
> X:/dev/... (where X is an abitrary drive)
> to a batchfile (setdjgpp.bat?) to generate a warning
> understandable by a nonhacker.
> I just know, how to get around the problem, but others will
> get into the same truble.

It's not that simple.  setdjgpp.bat would not be able to do this
unless it checked every drive in the system for that directory.
Even so, most people don't use setdjgpp.bat anyway.  The fact is
that if you're using djgpp programs you should not try to use
root-level directories called `dev'.

It's already explained clearly in the FAQ, section 22.20 --
press `i' then type `/dev' to look it up via the index.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

xu do tavla fo la lojban  --  http://xiron.pc.helsinki.fi/lojban/lojban.html

- Raw text -