> Couldn't it behave as a named pipe would in the local filesystem?> I'm sure I've seen this work elsewhere? (Not that that means it's> the correct thing to do, but...)

It would work if 1. you used 2.0.36+ (*not* 2.2) or 2. you had a unfsdserver (not sure about knfsd though, so this could become "if you have alinux server").

It's as simple as this: NFSv2 doesn't know about named pipes and peoplehave hacked their way around this limitation. It just happens that linuxchose a different hack than everybody else.

I had at some point a patch for 2.1.something which made linux usechar<255,255> as the NFSv2 encoding for a named pipe. I'll see if I canget it to work with 2.2, but it'll have to wait until tonight when I getback home. :)

Ion

-- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt.

-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to majordomo@vger.rutgers.eduPlease read the FAQ at http://www.tux.org/lkml/