I agree : this way network-manager will not _depend_ on resolvconf, but it will use it when available (and not disrupt the symlink)
note that the patch in http://mail.gnome.org/archives/networkmanager-list/2005-July/msg00184.html works in the way of the pseudocode: it has a snippet if (!g_file_test (RESOLVCONF_BIN, G_FILE_TEST_IS_EXECUTABLE)) return rewrite_resolv_conf(mgr, error); that ignores resolvconf if the binary is not there a. On Mon, Mar 27, 2006 at 08:40:25PM +0200, Thomas Hood wrote: > I agree that network-manager should follow the example of many other > network configurer applications and do the following (expressed in sh > pseudocode): > > > # Create resolvconf nameserver information record > if [ -x /sbin/resolvconf ] ; then > echo <nameserver info> | /sbin/resolvconf -a network-manager > else > ...futz with /etc/resolv.conf directly... > fi > > # Delete resolvconf nameserver information record > if [ -x /sbin/resolvconf ] ; then > /sbin/resolvconf -d network-manager > else > ...futz with /etc/resolv.conf directly... > fi > > See the resolvconf package README for more information. There is also > lots of example code in resolvconf-compatible packages. > > -- > Thomas Hood > Debian resolvconf maintainers -- Andrea Mennucc "Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
