Hi!
> So I guess things have already been a bit messy in this
> area for many years, even before linux even existed, and
> in some cases you can't really do anything about it because
> the behaviour is mandated by the applicable standards, like
> POSIX, SUS, or whatever.
> (The blocking of the open on a tty device is explicitly
> documented in my copy of the X/Open specification.)
If X/Open documents security hole, then, I guess, X/Open will have to
be changed.
Pavel
--
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
- Re: Why side-effects on open(2) are evil. (was Re: [RFD w/... Pavel Machek
- Re: Why side-effects on open(2) are evil. (was Re: [R... Alexander Viro
- Re: Why side-effects on open(2) are evil. (was Re: [R... Daniel Phillips
- Re: Why side-effects on open(2) are evil. (was Re... Oliver Xymoron
- Re: Why side-effects on open(2) are evil. (wa... Daniel Phillips
- Re: Why side-effects on open(2) are evil.... Oliver Xymoron
- Re: Why side-effects on open(2) are ... Daniel Phillips
- Re: Why side-effects on open(2) are evil.... Edgar Toernig
- Re: Why side-effects on open(2) are ... Alexander Viro
- Re: Why side-effects on open(2) are ... Daniel Phillips
- Re: Why side-effects on open(2) ... Oliver Xymoron
