Messages in this thread |  | | Date | Fri, 09 Feb 2001 18:31:59 -0600 | From | "David L. Nicol" <> | Subject | Re: bidirectional named pipe? |
| |
According to the Understanding the Linux Kernel book I plowed through yesterday afternoon the EXT2 file system has a defined file type "socket," distinct from fifo.
How does one set up a named socket in a file system? Is it a legacy constant that has never been supported or what?
"David L. Nicol" wrote: > > Alan Cox wrote: > > > > > I'm porting some software to Linux that requires use of a bidirectional, > > > named pipe. The architecture is as follows: A server creates a named pipe > > > > Pipes are not bidirectional in Linux. We follow traditional non stream > > behaviour > > > > > /dev/spx". I experiemented with socket-based pipes under Linux, but I > > > couldn't gain access to them by open()ing the name. Is there help? I > > > > AF_UNIX sockets are bidirectional but like all sockets use bind() and > > connect().
> You could patch the file system code, I wonder how deep the changes would have > to be, if you did it in terms of lots of fifos. > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > Please read the FAQ at http://www.tux.org/lkml/
-- David Nicol 816.235.1187 dnicol@cstp.umkc.edu "I don't care how they do it in New York"
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |