> Given how long this bug has been around, I'm guessing this is okay to wait for 2.6.28. Does that seem okay with you, Michael? We've managed to work around it in past releases, but it's a thorn and would be nice to see resolved sooner than later.