Date: Sun, 7 May 2000 14:40:29 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Martin Str|mberg cc: djgpp-workers AT delorie DOT com Subject: Re: Idea: \\host\share\file -> /dev/net/host/share/file In-Reply-To: <200005071011.MAA00558@father.ludd.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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. One problem that you will have to deal with is that /dev/net might be converted to x:/dev/net where x: is a random drive letter, probably quite different from the drive letter to which the UNC is mapped. In any case, a small number of library functions *must* have a drive letter, so we will need to invent something to cause those functions to DTRT. (The reason it wasn't done until now is that, officially, DJGPP doesn't support UNCs.) > are you saying that WINDOZE already understands /dev/net!? No, of course not.