This bug only affects 2.0.* kernels, which is why it slipped by. -- Dave
Messages Inline: Outline:
1. One more tiny problem by Denny Herlihy, 2000, Feb 08
to: "This is fixed in the 3.1.10 release"