I think it is entirely appropriate to discuss oskit issues, including what to put in the Debian oskit package, on oskit-users. Things like new drivers are of as much interest to any other oskit user as to specifically Hurd folks using oskit-mach, and the people who are truly authoritative on the oskit are there. So please continue this discussion there.
As to the question of drivers, can you be more specific? Are there 2.2.12 drivers that are not there? Or are you putting later 2.2.x drivers in? I had considered doing a wholesale upgrade of the linux code in the oskit to the latest 2.2.x, which is 2.2.20. This is pretty easy to do (for me), but it's something that requires a lot of testing on a variety real hardware before you'd want to put it in. I am not able to do that testing myself. The Utah folks (at least used to) have some equipment (machines with a variety of ethernet cards, for example) to test on, but we can't presume they would have the person resources to get much testing done. Of course, it never hurts to ask; but ideally we should line up volunteers to test the experimental oskit code from me while we get it in shape to go in. If the new code gets tested on a variety of hardware so we have some confidence that things that worked before still work now, the Utah folks will be happy to fold it in and make a new "official" snapshot. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
