Messages in this thread | | | Subject | Re: Problem with ioctl command TCGETS | From | Miklos Szeredi <> | Date | Sun, 28 Nov 2004 13:32:17 +0100 |
| |
> Think read(2)/write(2). We already have several barfbags too many, > and that includes both ioctl() and setsockopt(). We are stuck with > them for compatibility reasons, but why the hell would we need yet > another one?
You can't replace either ioctl() or setsockopt() with read/write can you? Both of them set out-of-band information on file descriptors.
Proc maybe ('/proc/PID/fdparam/FD/param')? I'm sure some people would have objections to that too.
Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |