Andrey Chernov wrote: > On Thu, Oct 14, 2004 at 02:59:34PM +0200, Ian FREISLICH wrote: > >>but zero response IIRC. Maybe making it on by default was a little >>hasty, but anyone that follows -CURRENT like they should if they >>run it weuld have been aware of this and set debug.mpsafenet=0 in >>their loader.conf when they saw that commit. > > > There is nowhere said in this commit that if_de would or ever may be > broken. Everydays something new coming, and this commit is one between > similar others, nothing brings special attention to be aware of. I'll > expect special 'WARNING: de owners' message to current in such situations, > i.e. if something is not fixed to work together. > The changes for locking the network stack have been going on for >2 years. During that time I and many others have called for people to help. At some point you have to leave certain code behind or you'll never make progress. Robert Watson made the extra effort to provide legacy support for drivers that lacked proper locking (I intended to just leave them broken until someone stepped up and fixed them). That this particular driver broke regardless is unfortunate but inconsequential relative to other issues. Given the price of 100baseT NICs these days if you're not willing to fix the code yourself I don't see it as a massive hardship to go buy replacements for your de cards. SamReceived on Thu Oct 14 2004 - 18:13:33 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:17 UTC