Sender: richdawe AT bigfoot DOT com Message-ID: <3A49E1D5.B6984074@bigfoot.com> Date: Wed, 27 Dec 2000 12:34:29 +0000 From: Richard Dawe X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: Draft patch for opendir() extension References: <7263-Tue26Dec2000184932+0200-eliz AT is DOT elta DOT co DOT il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. Tim Van Holder wrote: > Aside from the /dev stuff, which was indeed my main target (so ls /dev > would list them), I was thinking along the line of sockets - on Unix, > they're actual directory entries. With libsocket, also having them > appear as entries in the directory _might_ be useful. And there may > be other future uses (maybe DJGPP will support other special files > through fsext in the future). This is a bit offtopic, but might be interesting: I'm not sure how useful this would be for libsocket's sockets in general. TCP/IP socket handles cannot be passed between DOS boxes, unfortunately. OTOH libsocket's Unix domain sockets have a well-defined pathname -> device name mapping, so maybe that would. Both TCP/IP sockets and Unix domain sockets could be passed to child programs (using some variant of the proxy method used to pass long command-lines?), with some mechanism to resurrect libsocket's internal data structures. It certainly would be nice for Unix domain sockets to appear in ls listings, but I'm not sure if there are any easy ways of achieving this. Each Unix domain socket corresponds to a pair of mailslots - each corresponding to an end of the connection. You would need to enumerate all the mailslot paths, to generate the list of Unix domain paths. And how do you distinguish a mailslot from a Unix domain socket? Bye, Rich =] -- Richard Dawe [ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]