Subject: Re: ioctl and EOPNOTSUPP
To: Christos Zoulas <email@example.com>
From: Ian Zagorskih <firstname.lastname@example.org>
Date: 06/05/2003 05:01:33
On Wednesday 04 June 2003 21:42, Christos Zoulas wrote:
> In article <email@example.com>,
> Ian Zagorskih <firstname.lastname@example.org> wrote:
> >On Wednesday 04 June 2003 13:25, Simon Burge wrote:
> >According to:
> >...both ENOTTY and EOPNOTSUP are required by POSIX.
> Read carefully. EOPNOTSUP is only meaningful on sockets, not as the ret=
> value of ioctl(). In fact, if you look at the man page for ioctl(), you=
> see that EOPNOTSUP is not supposed to be returned by ioctl().
> I don't the ENOTTY kitchensink approach but the standards mandate
Yes, you are right. At least ioctl(2) description from
=2E.says the same just course it's applicible on exactly STREAMs file=20
descriptors. But as far as i understand in NetBSD ioctl() can be called w=
any fd, no ? It's not required to be STREAMS.