On Monday 12 May 2008 13:05:26 Bill Nottingham wrote: > Dan Williams ([EMAIL PROTECTED]) said: > > > Now, the question is: What does this change screw up??? > > > > Originally we did monitor /etc/sysconfig/networking/profiles/default > > (which is one of the 3 hardlink locations) but many people expect to > > change the files in /etc/sysconfig/network-scripts/ instead. Not > > everyone uses system-config-network evidently. > > Moreover, /etc/sysconfig/network-scripts is defined to be > the active location for current configuration - networking/profiles/default > isn't actually read by the actual scripts, so it's probably not what > NM should be looking at to be in sync.
First of all, I missed some of the replies to my message because of email filter I do so I just caught these replies. If /etc/sysconfig/network/scripts/ is the "correct" main directory, then system-config-network should be "fixed" to also use it as the main directory (I don't see s-c-network going away anytime soon). Regardless, the nm-system-settings-hardlinks patch I should work whether NetworkManager's directory is changed or not (at least that is what my testing showed) ... see https://bugzilla.redhat.com/show_bug.cgi?id=444502 for the patch. This fix is a bit crude (at least I think so) but it does seem to work. -- Gene _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
