2008/12/25 Patrick Shanahan
* Rob OpenSuSE
[12-24-08 13:39]: 2008/12/24 Carlos E. R.
: No, he indicated that he was using 10.3/KDE 3.5x, but didn't *specifically* request a "KDE" command.
So the whole rcnetwork restart, is a symptom of a problem, not part of the solution.
Agreed, but the question was:
Right, so it's KDE 3 not 4. But once GUI evironments, took it upon themselve not to punt to the system configured scripts, to handle such details; but accessed low level config stuff themselves in preference to calls of ifup/ifdown, there's a problem. That is why, 10.3 YaST Network Devices component has the option "Configure with Network Manager" or "Traditional method with ifup/down" in it. Network Manager duplicates functionality in a place and way that may make sense on desktop, but very much not on sever systems. I don't think the user wants to know about how it's done, but rcnetwork being able to talk to dbus and haldaemon is nice on openSUSE, but that intergration is SuSE code. Other distro's haven't done that, when I last looked. So now, if you're a KDE developer looking at that bug report, as Carlos pointed out "rcnetwork restart" is not a usable option, and as they're already talking to the low level stuff, rather than relying on system configuration, that is the way they'll go. It'll be no less portable than what they've written already. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org