| |||||||||||||
Williams: That's when I reach for my revolver...Williams: That's when I reach for my revolver...Posted Mar 24, 2009 13:05 UTC (Tue) by dwmw2 (subscriber, #2063)In reply to: Williams: That's when I reach for my revolver... by ras Parent article: Williams: That's when I reach for my revolver...
"He must be living in some parallel universe. I have _never_ had the good fortune to see NetworkManager work as it supposed to."I was saying that a year or so ago, but I've changed my mind. Since then, I have had it working relatively sanely on a few machines. It is getting better. That isn't to say there aren't still some problems though — the lack of support for Bluetooth DUN and PAN is painful, although hopefully that should be fixed soon. Watching the system automatically unmount all my NFS file systems while I was in the middle of a 'yum update' from NFS, just because there was a brief power glitch to the Ethernet switch, wasn't a particularly fun experience either...
(Log in to post comments)
Williams: That's when I reach for my revolver... Posted Mar 24, 2009 13:21 UTC (Tue) by dcbw (guest, #50562) [Link]
Just for you David, I got an SE phone with DUN that works on T-Mobile's HSDPA network where I already have an unlimited data plan. So now I have the ability to easily debug and fix issues with Bluetooth.
Williams: That's when I reach for my revolver... Posted Mar 24, 2009 13:25 UTC (Tue) by dwmw2 (subscriber, #2063) [Link]
Cool. Does it do PAN too? Although PAN isn't particularly hard to set up on another Linux box...
Williams: That's when I reach for my revolver... Posted Mar 24, 2009 13:37 UTC (Tue) by dcbw (guest, #50562) [Link]
No, it doesn't do PAN, but adamw is shipping me a HTC WinMo phone that does.
Williams: That's when I reach for my revolver... Posted Mar 24, 2009 13:36 UTC (Tue) by dcbw (guest, #50562) [Link]
And I'd like to point out that largely *because* NetworkManager usually doesn't work around stupid drivers and bad infrastructure, but instead encourages developers (including myself) to fix that infrastructure and drivers, we've come quite a long way in driver quality over the past few years.
NetworkManager is both the carrot and the stick. If NM just worked around broken stuff and proprietary drivers, it would be a hacktower of doom and we may still be stuck largely in 2006-wireless land.
Examples of driver/stack fixes due to NetworkManager:
- mac80211 adhoc mode association event and ibss merging timeout fixes
|
|||||||||||||