[Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread John Goerzen
On 2008-04-15, Joe Buehler [EMAIL PROTECTED] wrote: John Goerzen wrote: So I have a need to write data to a POSIX named pipe (aka FIFO). Long story involving a command that doesn't have an option to read data from stdin, but can from a named pipe. How about /dev/stdin? Only works on

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Brandon S. Allbery KF8NH
On Apr 16, 2008, at 11:16 , John Goerzen wrote: On 2008-04-15, Joe Buehler [EMAIL PROTECTED] wrote: John Goerzen wrote: So I have a need to write data to a POSIX named pipe (aka FIFO). Long story involving a command that doesn't have an option to read data from stdin, but can from a named

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Miguel Mitrofanov
You are insulting other Unixes. It works on Mac OS X, for example. On 16 Apr 2008, at 19:16, John Goerzen wrote: On 2008-04-15, Joe Buehler [EMAIL PROTECTED] wrote: John Goerzen wrote: So I have a need to write data to a POSIX named pipe (aka FIFO). Long story involving a command that

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Brandon S. Allbery KF8NH
On Apr 16, 2008, at 13:23 , Miguel Mitrofanov wrote: You are insulting other Unixes. It works on Mac OS X, for example. Not just that, but IIRC Linux was late to the party: Solaris got / dev/fd/ and /dev/stdin before Linux got /proc/$$/fd/ (which gets symlinked to /dev/fd/). -- brandon

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Donn Cave
On Apr 16, 2008, at 10:25 AM, Brandon S. Allbery KF8NH wrote: On Apr 16, 2008, at 13:23 , Miguel Mitrofanov wrote: You are insulting other Unixes. It works on Mac OS X, for example. Not just that, but IIRC Linux was late to the party: Solaris got / dev/fd/ and /dev/stdin before Linux got

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread John Goerzen
On Wed April 16 2008 12:20:37 pm Brandon S. Allbery KF8NH wrote: On Apr 16, 2008, at 11:16 , John Goerzen wrote: On 2008-04-15, Joe Buehler [EMAIL PROTECTED] wrote: John Goerzen wrote: So I have a need to write data to a POSIX named pipe (aka FIFO). Long story involving a command that

[Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Simon Marlow
Donn Cave wrote: I have run into this problem, with Network.Socket (socket). If I remember right, ktrace showed me what was happening. This isn't my favorite thing about Haskell. Is there even a means provided to set it back to blocking? There isn't a way right now to open a file using a

Re: [Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-16 Thread Richard A. O'Keefe
One question is whether the program is statically or dynamically linked, and if the latter, whether it is possible (as it is in many Unices) to slide your own open(2) definition in between the program and the system library. If it is, it's possible to slide in something that fakes /dev/stdin.

[Haskell-cafe] Re: I/O system brokenness with named pipes

2008-04-15 Thread Joe Buehler
John Goerzen wrote: So I have a need to write data to a POSIX named pipe (aka FIFO). Long story involving a command that doesn't have an option to read data from stdin, but can from a named pipe. How about /dev/stdin? -- Joe Buehler ___