>> If `fixing it' means calling socketpair() from userspace and doing any
>> necessary frobbing there, it actually means *reducing* kernel size (...and
>> relegating pipe(2) to COMPAT_14).
>
>pipe(2) is defined to be one-way. socketpair(2) creates a two-way pipe.
>
>I didn't find any obvious way in the manual page to suppress one of the ways.
>Hm. The libc wrapper could partially shutdown(2) the ends, I guess....

would that even matter?  if you get back a two-way pipe, it can still
be used as a one-way pipe.

for that matter...i still don't see the harm in making the kernel
copyout() the pipe fds.  how would that not solve the problem (besides
losing a little history)?

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."