>>> O_EXEC is mutually exclusive with O_RDONLY, O_WRONLY, or O_RDWR

>> - simply don't include this poorly-designed functionality in NetBSD.

> Unless you want to change O_RDONLY to be non-zero and version all the
> syscalls that use it :-)

I don't see any need to do that, unless they were crazy enough to
_require_ that the implementation error out if O_EXEC is combined with
one of the other three.  (I would expect that to just be an application
error, which an implementation may choose to assign meaning to.)

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mo...@rodents-montreal.org
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Reply via email to