KnetworkManager

Derek Broughton news at pointerstop.ca
Wed Aug 8 17:20:08 BST 2007


James Tappin wrote:

> On Tue, 07 Aug 2007 20:20:01 -0300
> Derek Broughton <news at pointerstop.ca> wrote:
> 
> DB> >
> DB> > Now reported as Bug #130863
> DB> >
> DB>
> DB> I think that's reasonable, but do you not realize that it's actually
> DB> a _design_ feature?  NetworkManager (if you reported this against
> DB> knetworkmanager, you reported it to the wrong place, I believe)
> DB> specifically ignores anything you've chosen to manually maintain -
> DB> by using /etc/network/interfaces.
> 
> I think that's debatable. I have reported as a bug that knetworkmanager
> writes its manual configurations to /etc/network/interfaces thus
> preventing itself from using NetworkManager. 

Hmmm.  I see your point, but knetworkmanager never actually uses interfaces. 
When you choose "manual configuration", it invokes the standard KDE network
config tool.  Now, _I_ know that, and probably you know that, but we
certainly can't expect a new user to realize that "manual configuration"
means "manage this device _outside_ network manager".  At the very least
it's a poorly worded option in KNetworkManager.

> I do agree however that it 
> could be interpreted as a misfeature of NetworkManager; however my take
> is that as knetworkmanager uses NetworkManager to provide its list of
> available connections then it ought not to prevent it from providing
> that list.

Yes, indeed.
-- 
derek




More information about the kubuntu-users mailing list