Some months ago I noted that a new kernel introduced a failure to be able
to unlock X after locking. Still there in 2.5.69 for RH 7.2, 7.3, and 8.0.
Is there any plan to address whatever causes this problem with a kernel
fix, or is a 2.4 kernel still the way to go if you need to lock X. I
realize many developers work in environments where there's no need.
-
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/
This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:26 EST