> we always will apply the final result just fine, when stuff stops
quoted text
> changing. It's actually a nice feature and no a problem at all, that
> we only see the most recent state.

Stuff never stops changing until the machine shuts down, its undefined.

quoted text
> Sure, with the ioctl() we've seen many not interesting changes, but we
> often miss the single one that is important -- the last last one. The
> thing is that we don't need to sleep here and miss changes.

So we fix the ioctl interface, it's not exactly hard to do now is it.

quoted text
> It's a straight-forward and simple text interface that does all we
> need to track console and vt changes.

Except that it doesn't address things like the permissions side of things.

NAK again

"We have an interface that doesn't quite work for our case and we think
that is a bug" is not the reasoning behind writing a new random one with
a totally disconnected permission model that doesn't work either.

Fix the one we have.

Alan
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/