Messages in this thread | | | Date | Sun, 28 Nov 2004 12:48:47 +0000 | From | Al Viro <> | Subject | Re: Problem with ioctl command TCGETS |
| |
On Sun, Nov 28, 2004 at 01:32:17PM +0100, Miklos Szeredi wrote: > > 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.
Out-of-band == should be on a separate channel... - 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/
| |