From:	Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id:	<200005080854.KAA04162@lws256.lu.erisoft.se>
Subject:	Re: Idea: \\host\share\file -> /dev/net/host/share/file
To:	djgpp-workers AT delorie DOT com
Date:	Mon, 8 May 2000 10:54:20 +0200 (MET DST)
In-Reply-To:	<Pine.SUN.3.91.1000507143119.23267A-100000@is> from "Eli Zaretskii" at May 07, 2000 02:40:29 PM
X-Mailer:	ELM [version 2.5 PL3]
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

Eli said:
> On Sun, 7 May 2000, Martin Str|mberg wrote:
> 
> > Perhaps you misunderstand me? The idea is to use
> > /dev/net/... internally to avoid this destructiveness, and map
> > \\host\ to /dev/net/host on entry to the C library and then map it
> > back to \\host just before calling *DOZE.
> 
> Who will map the UNCs to /dev/net?  There's no single entry point to
> library functions that deal with file names, so this is not really 
> trivial.  An application can do that, but it will need to have special
> code for this.
> 
> Also, it is not clear to me what is simpler: to add the support for 
> /dev/net or just make sure \\host\share survives all the functions that 
> parse file names.  Feel free to suggest patches, though.

Oh! I see now. The problem isn't primarily the library, it's the
applications that munge/change the double slashes. Oh, well, it was
just an idea. 

Do the net directors (if that's what they are called) handle "//"
equivalently as "\\" (similar to DOZE's handling of "/" and "\")?


Right,

						MartinS

- Raw text -