Matthew Kirkwood wrote:
> > Why don't you just give O_NONE (value: 3) this behaviour?
>
> Partially because I didn't want to break applications already
> using this (IMHO, rather dubious) feature.
>
> Mostly, though, because I wanted to leave the O_RDWR/etc.
> permission checks in the open() path, to avoid the possibility
> of giving out descriptors to otherwise inaccessible files.
O_NONE already does some kind of permission check -- you can only open a
file that has read and write access. You certainly can't open an
inaccessible file.
I don't think there would be many complaints if that were changed to
read _or_ write.
-- Jamie
