On Apr 1, 2005, at 03:14, Darren Reed wrote:
This has already been raised and when 4.1.8 gets imported into -current,
a fix will showup there soon.
If you plan to stick with 2.0.x then it may be necessary to roll a patch
and send that to releng.
I'm definately wanting to stick with something stable. Once a 2.1 makes it out, I may go there, but I'll definately stay in 2.x for the forseeable future.
Could you direct me as to where changes need to me made? I'd be happy to make them, and roll a PR up to get this fixed in netbsd-2 and netbsd-2-0.
Thanks.
- Chris
