revoke() is available in BSD.
Announcement
Collapse
No announcement yet.
X.Org Server Development Process Is Questioned
Collapse
X
-
Originally posted by uid313 View PostWhy does not Linux have a revoke() after all these years?
There already been patches committed to add this, why have it not been merged?
Comment
-
Originally posted by daniels View PostThey don't cover all the corner cases, some of which are viciously hard to deal with. To be honest, I think the best course of action would be an input-specific revoke(), but last time that got proposed, it got shot down in LKML internal bitchfights.
Maybe they should just merge something, and accept a less-than-perfect solution, so have something that kinda does what its supposed to do even if it doesn't cover all the corner cases.
Then later it can be improved in time to mature and further stabilize.
Comment
-
Originally posted by curaga View PostThen they'd be stuck with the inferior solution in kernel forever.
Whatever implementation of revoke() goes into the kernel has to be perfect on the first run or extensible enough to not matter.All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by uid313 View PostHmm, maybe if there were a revoke() implementation as a loadable kernel module?All opinions are my own not those of my employer if you know who they are.
Comment
-
It's their model
Something new comes along and they delete the old.
GEM vs EXA vs XXA
Then there was DRI vs DRI2.
Modesetting.
The list grows but I still blame distributions for screaming "Upstream" more than senators scream "Bipartisanship".
It's getting old.
You just can't keep up. I commend Nvidia for keeping up with the Jones'.
Comment
-
Originally posted by squirrl View PostSomething new comes along and they delete the old.
GEM vs EXA vs XXA
Then there was DRI vs DRI2.
Modesetting.
The list grows but I still blame distributions for screaming "Upstream" more than senators scream "Bipartisanship".
It's getting old.
You just can't keep up. I commend Nvidia for keeping up with the Jones'.
DRI was supplanted by DRI2...which was in the X server, not the kernel. The x server drops stuff.
Modesetting moved from the X server (userspace) to the kernel (KMS)
Nvidia keeps up because...they replace most of the stack with their own pieces because of cross-platform support
Wanna try again squirrl?All opinions are my own not those of my employer if you know who they are.
Comment
Comment