That's the easy part; the CML1 config code may be ugly and broken, but
at least it's relatively stable. What you'd also have to do is maintain an
entire CML1 ruleset in parallel with the canonical CML2 one. That's
the hard part.
I've been keeping the CML2 ruleset synced with CML1 for a year now.
It's been an ugly, nasty, horrible job -- *much* nastier, by an order
of magnitude, than designing and writing the CML2 engine. Going the
other direction would be worse. "Like chewing razor blades" is the
simile that leaps to mind.
(And no, dropping back to CML1 format for the masters wouldn't be an
option; it doesn't have the semantic strength to enable CML2's new
capabilities.)
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>Certainly one of the chief guarantees of freedom under any government, no matter how popular and respected, is the right of the citizens to keep and bear arms. [...] the right of the citizens to bear arms is just one guarantee against arbitrary government and one more safeguard against a tyranny which now appears remote in America, but which historically has proved to be always possible. -- Hubert H. Humphrey, 1960 - 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/