Steven Stallion writes: > So what is the right approach? It doesn't seem that any are in favor of > hacking around the issue in ifconfig or in ip. Adding support for DL_PPP > has a gob of issues all on its own as well. I imagine there is going to > be more than a little politicking done before all is said and done > (especially if DL_PPP is the solution).
I think DL_PPP is the cleanest way out -- for that one component. Something needs to be done about the other components that are camping out on this bit of mis-functionality -- Sebastien noted that the "nit" driver also does this. It's not impossible that there are others, and it may be hard to find them all. (That could be where a _temporary_ one-time-per-boot warning would actually be useful.) > This is beginning to feel a bit like a rabbit hole - I would certainly > be curious to see where it goes, but if no one cares it is a moot point. Yeah. It's also one we've poked around in before. > Bad analogies aside, I suppose what I am really asking, is this even > worth pursuing? I have a good bit of time I can dedicate toward this > (and other issues) and I would like the opportunity to do something more > substantive within Solaris networking. It sounds like you have the requisite features -- an understanding of the problem and the time to take it on. I don't know if it's the most important fire burning in this forest, but if you feel it's worth doing, and are willing to work out the kinks, I'd certainly support that. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
