Messages in this thread | | | Date | Sun, 28 Nov 2004 14:07:04 +0100 | From | Tomas Carnecky <> | Subject | Re: Problem with ioctl command TCGETS |
| |
Al Viro wrote: > On Sun, Nov 28, 2004 at 12:22:03PM +0100, Miklos Szeredi wrote: > >>>The set-get is supposed to be used for queries, too? The size of value is >>>only used for the get case to describe the buffer length in that case? >>>because otherwise the set-get case may require a short value in and a large >>>answer structure out. >> >>You misunderstand the motivation. This is to get/set small compact >>parameters, not huge structures or big data. Think get/setsockopt(). > > > 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?
And what's the option? So without ioctl, how would you reaplace this: ioctl(cdrom_fd, CDROMEJECT, 0)?
tom - 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/
| |