On Thu, Sep 10, 2009 at 05:26:24PM +0200, Petr Salinger wrote: >> So the fix would be to change that behaviour then...
> It is usually upstream decision whether some "Optional Feature" > have default "yes", "no" or "auto". > In this case upstream uses "yes", not "auto". So please submit a patch changing that. Consider, for example, making the decision conditional on the OS if you're concerned about this but are you sure upstream has even considered the options here? >> Sure, but all that means is that a FreeBSD variant of the kernel >> interface needs to be provided. > It might happen in future, but so far "NetworkManager supports _only_ > those drivers that are shipped with the upstream Linux kernel". That's an unrelated issue - what that means is that there's been several people going off on their own and implementing non-standard wireless ABIs. > Please (re)consider, whether having Network Manager is crucial > to use ypcat. ypcat makes no use of Network Manager. ypbind can, though. I'd be willing to take a patch such as I've been asking for which means that I don't need to pay attention to missing components on FreeBSD. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
