resolvconf-1.69ubuntu1/0000755000000000000000000000000012076277005012051 5ustar resolvconf-1.69ubuntu1/README0000644000000000000000000007240512076274066012745 0ustar README file for resolvconf Contents ~~~~~~~~ News Introduction Rationale HOWTO Order of entries in resolv.conf Requirements Technical overview Usage information for developers Usage information for maintainers Usage information for administrators FAQ TODO DONE Credits News ~~~~ * Last updated 4 December 2012 for version 1.69 Introduction ~~~~~~~~~~~~ Resolvconf is a framework for keeping track of the system's information about currently available nameservers. It sets itself up as the intermediary between programs that supply nameserver information and applications that need nameserver information. Rationale ~~~~~~~~~ /etc/resolv.conf was once a simple static configuration file where the sysadmin placed a few directives that rarely needed to be changed. That changed with the advent of mobile computing: a computer can now move from one network to another quite often. Debian currently includes many packages that alter resolv.conf more or less automatically. Some of them are listed below, along with a short description of what they do which I have tried to keep up to date. (Figures in parentheses show the number of the package's popularity-contest votes as of 5 January 2005.) pcmcia-cs (914) Can overwrite resolv.conf with no backup unless (as of 3.2.5-1) resolvconf is installed. By default, doesn't. ppp (4533) pppd optionally overwrites /etc/ppp/resolv.conf . By default, does. pppconfig (3702) Moves resolv.conf out of the way and puts it back when done. pppoeconf (2938) Prior to version 1.0, overwrites resolv.conf, attempting to merge its stuff with the existing contents. Creates a backup in /etc/ but doesn't restore it. gnome-ppp (24) Contains experimental code, currently commented out, that overwrites resolv.conf. gnome-system-tools (1349) Allows the user to write directly to /etc/resolv.conf. systemconfigurator (94) Allows the user to write directly to /etc/resolv.conf. webmin (781) Prior to version 1.150-2, the Network Configuration|DNS Client page can make changes to /etc/resolv.conf. As of 1.150-2 this page is read-only when resolvconf is installed. webmin-wvdial (8) Copies /etc/ppp/resolv.conf over /etc/resolv.conf after PPP connection established unless (as of version 1.160-3) the latter is a symbolic link; restores original contents from backup file when the connection is broken. xisp (1 -- removed) Adds lines to /etc/resolv.conf on PPP interface up and deletes those lines on interface down. totd (5) Prior to 1.4-4, PPP hook scripts can do things to /etc/resolv.conf but SFAICT are effectively no-ops if resolvconf is installed. Hard to tell. Postinst does things to /etc/resolv.conf and also rewrites dhclient_enter_hooks in a way incompatible with resolvconf. As of 1.4-4 totd plays nicely with resolvconf. dhcp-client (4005) Prior to version 2.0pl5-17, overwrites resolv.conf without making a backup. dhcp3-client (676) Overwrites resolv.conf unless make_resolv_conf() is redefined. Resolvconf redefines it. dhcpcd (104) Optionally overwrites resolv.conf . Default is not to do so. Prior to version 1:1.3.22pl4-8, hook script overwrites /etc/dhcpc/resolv.conf unless (as of 1:1.3.22pl4-7) resolvconf is installed. pump (734) Prior to version 0.8.15, blindly overwrites resolv.conf unless nodns option is used. No backup. As of version 0.8.15 pump calls resolvconf if it is installed instead of overwriting /etc/resolv.conf. udhcpc (44) Prior to version 0.9.8cvs20050124-2, blindly overwrites resolv.conf without making a backup. netenv (43) Contains sample code that, if uncommented, would overwrite /etc/resolv.conf without backing it up switchconf (12) Forcibly links selected resolv.conf file into place without making a backup. divine (9) Symlinks-in a resolv.conf for the selected network. Appears to trash whatever was in resolv.conf when it starts. intuitively (18) If a resolv.conf file is included in /etc/intuitively/NETWORK, blindly overwrites /etc/resolv.conf . laptop-netconf (23) Symlinks in a resolv.conf for the detected network. Seems to make a backup of resolv.conf but doesn't restore it. whereami (23) Contains utility scripts that modify resolv.conf laptop-net (42) Overwrites resolv.conf unless (as of 2.20) resolvconf is installed. Several other packages recommend to the user that scripts be written to alter or replace resolv.conf. Third-party software packages also futz with /etc/resolv.conf. Among them are the Cisco AnyConnect, Juniper AnyConnect and FortiClient SSL VPN clients. These packages do not cooperate; they simply overwrite one another's changes. Even those that back up and restore the file will corrupt it if interfaces are brought up and down in other than a LIFO order. Few of them support the use of a local DNS cache. Resolvconf (555) has been written in order to provide a framework for managing the resolv.conf file in an way that avoids the above problems. HOWTO ~~~~~ Resolvconf works with most interface configurers in Debian ('(*)' below meaning "with some manual configuration"): isc-dhcp-client, dhcpcd, pump, udhcpc ppp ifupdown network-manager DNS caches: bind9(*), djbdns dnscache, dnsmasq, nscd, pdnsd, totd DNS recursing nameservers: bind9(*), pdns-recursor(*) and with any program that uses a DNS client library that consults /etc/resolv.conf to obtain its list of nameservers: the GNU C Library resolver library adns the djbdns resolver library FireDNS Take the following steps to set things up. Unfortunately, it is not always simply a matter of installing the resolvconf package -- especially if you have already tried to deal with the above problems locally by customizing your configuration. 1. You may have already installed resolvconf at this point. OK. 2. Stop obsolete programs from writing to /etc/resolv.conf * netenv + Purge or make sure that /sbin/netenv hasn't been configured such that it overwrites /etc/resolv.conf * switchconf + Purge or make sure that there are no resolv.conf files under the /etc/switchconf/ directory * xisp + Purge * divine + Purge * intuitively + Purge * laptop-netconf + Purge * whereami Purge or make sure that you aren't using the "setresolver", "bind-forwarders" or "setdnsmasq" utility scripts. * etc. Delete or disable local scripts of any kind that futz with /etc/resolv.conf 3. Configure packages not to overwrite /etc/resolv.conf and to work properly with resolvconf 3.1 ppp * Make sure that the usepeerdns option is used. With this option, pppd will obtain nameserver addresses from the peer and these will be added to resolvconf's database. 3.2 pump * Make sure that neither the nodns nor the noresolvconf option is used -- either in pump.conf or on the command line 3.3 dhcpcd * Make sure that SET_DNS is not set anywhere in /etc/dhcpc/config . (In recent versions of dhcpcd, on initial installation, SET_DNS is not set.) 3.4 ifupdown * Remove any "up" or "down" commands from /etc/network/interfaces that futz with /etc/resolv.conf and remove any scripts from /etc/network/if-*.d/ that futz with /etc/resolv.conf. * For each inet static logical interface through which a nameserver is accessible, add lines like the following to /etc/network/interfaces . dns-nameservers 11.22.33.44 55.66.77.88 dns-search foo.org bar.com Other recognized option words are 'dns-domain' and 'dns-sortlist'. These option names correspond to the option names used in the resolv.conf file with one exception: whereas one lists several nameserver addresses in /etc/resolv.conf on several "nameserver" lines, here one should list them all on a single "dns-nameservers" line. See resolv.conf(5) for more information. The lines entered in /etc/network/interfaces will be added to the resolver configuration file (without the "dns-" prefix, of course) when a physical interface is brought up as that logical interface. Note that the resolver configuration is updated AFTER all the "up" commands have been run; therefore "up" commands cannot make use of nameservers listed on "dns-nameservers" lines in the same logical interface stanza. Changing this will require modifying ifupdown so that it talks to resolvconf; currently resolvconf hooks into ifupdown using the script /etc/network/if-up.d/000resolvconf. Note too that scripts in /etc/network/if-up.d/ CAN make use of the added nameservers because those scripts run after 000resolvconf. 3.5 bind9 * To make bind9 supply its nameserver address 127.0.0.1 to resolvconf, set RESOLVCONF=yes in /etc/default/bind9. * To make bind9 use nameserver addresses supplied by other sources as addresses of forwarders, either (1) pursuade the maintainers of the bind9 package to implement this feature (as already requested at http://bugs.debian.org/483098) or (2) add a hook script to /etc/resolvconf/update.d/ which writes out a configuration file fragment and then tells named to re-read is configuration. A sample hook script meeting this description has been provided in /usr/share/doc/resolvconf/resolvconf-update-bind. 4. Install the resolvconf package if you have not already done so. If you have already done so then consider dpkg-reconfigure'ing it. Agree to symlink /etc/resolv.conf to /run/resolvconf/resolv.conf. You can decline the offer to append the original static resolver configuration file to the end of the dynamically generated resolver configuration file because you have already modified /etc/network/interfaces as directed above. 5. Reboot 6. Check /etc/resolv.conf to make sure that its contents make sense. If /etc/resolv.conf is not symlinked to /run/resolvconf/resolv.conf then a warning message will be printed when /sbin/resolvconf is run. If you want to keep resolvconf installed but for some reason do not want /etc/resolv.conf to be symlinked to /run/resolvconf/resolv.conf then you can disable the warning message by setting REPORT_ABSENT_SYMLINK=no in /etc/default/resolvconf. Order of entries in resolv.conf ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Some of the information in the resolver configuration file consists of a set of entries whose order is significant. Specifically, the order of nameserver lines nameserver x1.x2.x3.x4 nameserver y1.y2.y3.y4 determines the order in which nameservers are consulted and the order of items on the search line search da1.da2.org db1.db2.com determines the order in which domain names are tried. Resolvconf orders these entries according to the names of the interfaces to which they relate. (More truthfully, it orders them according to the record names in which they are stored, but it is a convention that records are named like the interfaces for which they are the records, possibly with some suffix.) The particular order is determined by the /etc/resolvconf/interface-order file. See interface-order(5) for more information. If you use ifrename, nameif or udev in order to assign stable names to your network interfaces, I recommend that you employ names that begin with the traditional pattern but differ from those names that the kernel uses as defaults. E.g., the kernel names Ethernet interfaces 'eth0', 'eth1', and so on, so you might rename your Ethernet interfaces to "eth_3com", "eth_cisco", etc. Similarly you might rename your Wi-Fi interfaces "wlan_airo" and "wlan_atmel". If you follow this advice then you won't have to modify the default interface-order file. Using a static file to order the entries is obviously not very flexible; however, it is adequate in most usage situations. Situations for which it is not adequate are generally situations in which it is better to use a local caching nameserver that can do things like monitoring and load balancing. Requirements ~~~~~~~~~~~~ I hope that resolvconf satisfies the following requirements. * Be opaque Resolvconf must be as opaque as possible. It must have a stable interface and mustn't require that maintainers know about its internals. * Be order-independent Interfaces going up and down in arbitrary order must be handled properly. * Be locally configurable Administrator choices must be respected. * Support DNS caches Local DNS cache programs must be able to arrange for nameserver addresses supplied by interfaces to be passed to them for use as forwarders. The libc resolver should use any local DNS caches that are available. * Be compatible with a read-only root filesystem Variable files must be easily relocated out of /etc/. * Be portable * Be simple Technical overview ~~~~~~~~~~~~~~~~~~ * The /etc/resolvconf/ directory contains: + resolv.conf.d/ Files related to the libc resolv.conf file - resolv.conf.d/head The head of the dynamically generated resolv.conf - resolv.conf.d/tail The tail of the dynamically generated resolv.conf - resolv.conf.d/base Information always included in the resolv.conf file. Dynamic information gets merged with this information. E.g., if base contains 'search a.b.c' and another record is added that contains 'search x.y.z' then the resulting file will have 'search a.b.c x.y.z'. + run/ Directory where run time files are stored. This can be replaced by a symlink if the admin so desires. Standardly this is a symlink to /run/resolvconf/. + update.d/ Scripts to run when nameserver information is updated + update-libc.d/ Scripts to run when the resolv.conf file changes * Symlink /etc/resolv.conf -> /run/resolvconf/resolv.conf * Configurers of interfaces call /sbin/resolvconf to provide resolv.conf-like information after the interface is brought up. They call it again to delete the information when the interface is brought down. /sbin/resolvconf then does the equivalent of "/etc/init.d/resolvconf reload". * "/etc/init.d/resolvconf reload" calls scripts in /etc/resolvconf/update.d/ which update DNS cache configuration file fragments, reload daemons and regenerate /etc/resolv.conf. If the latter has changed then nscd is restarted and scripts in /etc/resolvconf/update-libc.d/ are run. Usage information for developers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Interface configurers send resolver information to resolvconf in the format of the familiar /etc/resolv.conf file. Thus, for example, a program foo that has configured interface $IFACE would do the following after generating a resolv.conf file named 'new-resolv.conf'. resolvconf -a "${IFACE}.foo" < new-resolv.conf This command updates the resolver information related to interface $IFACE and configurer foo. Any information previously sent for this interface/configurer combination is overwritten. On bringing the interface down, the configurer (foo) would do the following. resolvconf -d "${IFACE}.foo" For another example, the proxy script for pppd forwards to resolvconf the resolver information that is made available to ip-up.d/ and ip-down.d/ scripts in environment variables DNS1, etc. echo "nameserver $DNS1" | resolvconf -a "${IFACE}.pppd" For additional examples, look at the hook scripts for isc-dhcp-client and ifupdown. Support for other configurers including dhcpcd, pump and udhcpc has been added to those packages. In general, any package that currently overwrites /etc/resolv.conf can be adapted to work with resolvconf while preserving backward compatibility by introducing a code fragment like the following. MYNAME=foo if [ -x /sbin/resolvconf ] ; then if [ "$DIRECTION" = "up" ] ; then echo -n "$RESOLVINFO" | /sbin/resolvconf -a "${IFACE}.${MYNAME}" else /sbin/resolvconf -d "${IFACE}.${MYNAME}" fi else # Do clever things to /etc/resolv.conf fi /sbin/resolvconf stores the information sent to it and then runs the scripts in /etc/resolvconf/update.d/ . One of the latter generates the libc resolver configuration file. Others generate lists of forwarders for dnsmasq or pdnsd to use. Any other program that needs to take action when resolver information is updated could likewise employ a script in /etc/resolvconf/update.d/ . Usage information for maintainers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Normally, when the resolvconf package is installed the resolvconf program takes control of /etc/resolv.conf. It derives the contents of that file from nameserver information that has been sent to it, as described above. Resolvconf is not part of the base system. It is generally installed after the system has fully booted. At that point interface configurers have already configured interfaces and obtained nameserver information. Caching nameservers may also have started. Because resolvconf is installed only later, the latter programs have (obviously) not sent their nameserver information to resolvconf. This means that after installation resolvconf does not have complete nameserver information. The most reliable solution to this problem is to reboot. But Debian rightly frowns on requirements to reboot, so the resolvconf package has been so designed that it partially addresses the problem just mentioned, as described below. In the future the problem may be fully solved, but this will require the cooperation of other Debian package maintainers. In order partially to address the problem of resolvconf having incomplete information after installation until the first reboot, resolvconf includes the entire contents of the original (i.e., pre-resolvconf-installation) resolv.conf in its database. Consequently, nameserver addresses are not lost when resolvconf is installed. Unfortunately this also means that those addresses are not removed when interfaces are brought down. Another way the resolvconf package addresses the problem is to allow other parties to call /sbin/resolvconf as soon as it appears in the filesystem: nameserver information can be registered with resolvconf before the resolvconf's postinst runs. This means that when, for example, dnsmasq and resolvconf are installed in the same dpkg run, and dnsmasq happens to be configured first, dnsmasq can still successfully register its nameserver address with resolvconf. The correct and complete way to solve the problem is for all suppliers of nameserver information to supply their information to resolvconf after resolvconf has been installed. As of resolvconf release 1.55 this is supported via the following mechanism. Any package, foo, that supports supplying information to resolvconf should include a hook script /usr/lib/resolvconf/dpkg-event.d/foo which, when called with the argument "install", takes whatever actions are necessary to cause the program(s) in foo to supply their nameserver information to resolvconf; and when called with the argument "remove" takes whatever actions are appropriate given that the resolvconf package has been removed (and, in being removed, may have removed foo's nameserver information). The hook script thus has the following form. #!/bin/sh # # /usr/lib/resolvconf/dpkg-event.d/foo # # The resolvconf dpkg-event hook script for the foo package # if foo_is_running ; then if [ "$1" = "install" ] ; then foo-ctrl send-nameserver-info-to-resolvconf elif [ "$1" = "remove" ] ; then ... fi fi If foo is controlled by an initscript whose methods take appropriate actions conditional upon resolvconf's presence then something like the following might be appropriate. force_reload_foo() { if which invoke-rc.d >/dev/null 2>&1 ; then invoke-rc.d foo force-reload elif [ -x /etc/init.d/foo ] ; then /etc/init.d/foo force-reload fi } case "$1" in install|remove) force_reload_foo ;; esac The hook script is called (with argument "install") from resolvconf's postinst "configure" method and (with "remove") from resolvconf's postrm "remove" method. Foo's hook script is called with argument "install" if and only if foo is fully installed both when resolvconf's preinst install runs and when its postinst configure runs. The hook script is called with argument "remove" if and only if foo is fully installed when resolvconf's postrm remove runs. The hook script must be owned by root and have its execute permission bit set and must have the same name as the package that owns it. Arguments other than "install" and "remove" are reserved for future use and must be silently ignored. Usage information for administrators ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The generation of the resolv.conf file can be controlled by editing the /etc/resolvconf/update.d/libc script. Different strategies can be followed. For example, one possible strategy would be to put only the most recently provided information into resolv.conf . The current default strategy is to put *all* available resolver information into resolv.conf, ordered by interface type as listed in the interface-order(5) file, except that no addresses are listed after a loopback address. The admin can of course disable resolv.conf automagic by deleting the /etc/resolv.conf symlink and putting a static file at that location. Once you have installed resolvconf properly you don't normally need to run /sbin/resolvconf from the command line. However, I once encountered a situation in which I did that. Perhaps it is a useful illustration. My ISP's nameserver went down and thus my caching nameserver could not resolve names. I knew of another host belonging to by ISP that I could use so I simply did: # echo "nameserver ww.xx.yy.zz" | resolvconf -a dummy This added the necessary nameserver line to /etc/resolv.conf and to dnsmasq's nameserver list. When my ISP's regular nameserver was fixed I did: # resolvconf -d dummy to restore the original situation. FAQ ~~~ Q. Why call it 'resolvconf' instead of 'update-resolver' or so? A. Debian's update-* commands are mostly maintainer programs that update static configuration files in /etc/. Mostly they run at package install time. Resolvconf, in contrast, is a run-time configurer. Q. Why use 'dns-nameservers' instead of 'dns-nameserver' as the option name in /etc/network/interfaces? A. Because 'dns-nameservers' can take several address arguments whereas the 'nameserver' line in /etc/resolv.conf can take only a single argument, and because there can be only one instance of any given option in a logical interface definition. TODO ~~~~ * bind9 # 483098: bind9: Please add resolvconf hook script to update forwarders list - NO REPLY for several months # 641714: Please add resolvconf packaging-event hook script - NO REPLY for several months * dnscache-run (from djbdns) # 582755: Add resolvconf support - NO REPLY for several years * gnome-ppp # 258064: Writes to /etc/resolv.conf - WORKAROUND introduced in July 2004 was to make gnome-ppp Conflict with resolvconf * gnome-system-tools # 258553: Incompatible with resolvconf - NO ACTION for several years * ifupdown + Handle dns-* commands natively so that the resolver is configured before "up" commands are run * kppp # 695121; LP#1086336: Writes to /etc/resolvconf - SUBMITTED * libadns1 + It consults resolv.conf so it should already be supported. However, someone should test it. * libares0 + It consults resolv.conf so it should already be supported. However, someone should test it. * libdjbdns1 + It consults resolv.conf so it should already be supported. However, someone should test it. + Someone should investigate whether it could be supported better. Perhaps /etc/dnsrewrite should be dynamically updated? * libfiredns0.9 + It consults resolv.conf so it should already be supported. However, someone should test it. + Someone should investigate whether it could be supported better. Perhaps /etc/firedns.conf should be dynamically updated? * maradns # 608946: resolvconf integration - Its initscript should probably do echo "nameserver 127.0.0.1" | resolvconf -a lo.maradns as dnsmasq and pdnsd do. - Could it have an update script that sets the "upstream_servers" variable? - Tagged WONTFIX since the maintainer doesn't have any free time * Net::DNS + It consults resolv.conf so it should already be supported. However, someone should test it. + Someone should investigate whether it could be supported better. * network-manager # 639803: Please add resolvconf packaging-event hook script - NO REPLY for several months * nscd # 266817: Please suggest resolvconf - Tagged WONTFIX * pdnsd # 628846: Include /usr/lib/resolvconf/dpkg-event.d/pdnsd - NO REPLY for several months * ppp # 208095: Please suggest resolvconf - Tagged WONTFIX * resolvconf + See http://bugs.debian.org/resolvconf * systemconfigurator # 272475: Please support resolvconf - NO REPLY for many years * Users of resolver libraries + For any package that contains a program that uses resolver(3) or a compatible library, add a /etc/resolvconf/update-libc.d/ script to notify running instances of the program that the resolver configuration file has changed. DONE ~~~~ * bind + Drop support for this obsolete version of BIND - DONE in resolvconf 1.48 * bind9 + Create script /etc/resolvconf/update.d/bind to: . Convert /etc/bind/named.options.sed into /var/run/bind/named.options (which is to be included in /etc/bind/named.conf) . Then run "/etc/init.d/bind9 reload" or "/etc/init.d/bind reload" - DONE in resolvconf package # 199255: Please support resolvconf - DONE in 1:9.2.3-1 # 252232: Please use 'lo.named' as resolvconf record name - DONE in 1:9.3.2-2 # 252285: Please Suggest resolvconf - DONE in 1:9.4.2-2 * debian-installer # 255187: Please add resolvconf support - DONE in version netcfg/0.71 * dhcp3-client + Use resolvconf via /etc/dhcp3/dhclient-enter-hooks - DONE in resolvconf package # 171798: dhclient-script should source hook scripts, not run-parts them - DONE in 3.0+3.0.1rc11-5 * dhcp-client # 248399: Needs resolvconf support - DONE in 2.0pl5-18 * dhcpcd + Support resolvconf without requiring local changes - DONE in 1:1.3.22pl4-7 * dnsmasq + Create script /etc/resolvconf/update.d/dnsmasq to generate /var/run/dnsmasq/resolv.conf - DONE in resolvconf package + Support resolvconf without requiring local changes - DONE in 1.13-2 + Include /etc/resolvconf/update.d/dnsmasq - DONE in 1.13-3 # 628003, #641717: Include /usr/lib/resolvconf/dpkg-event.d/dnsmasq - DONE in 2.58-3 * fetchmail + Use resolvconf to trigger restart on change of nameserver info - DONE in 6.2.5-4 * ifupdown + Use resolvconf via /etc/network/if-(up|down).d/ - DONE in resolvconf package * laptop-net + Use resolvconf instead of overwriting /etc/resolv.conf . - DONE in 2.21-1 * nscd # 252251: Please add resolvconf support - DONE in resolvconf 1.15 * pcmcia-cs # 212823: pcmcia-cs: please add support for the resolvconf package - DONE in 3.2.5-1 * pdns-recursor # 308677: /etc/init.d/pdns-recursor: Please add resolvconf calls - DONE in 2.9.18-4 * pdns-server # 304528: Please add resolvconf update script in order to automate the creation of the recursors list - DONE in 2.9.18-4 * pdnsd # 247946: Fix resolvconf support - DONE in pdnsd 1.1.10par-4 * postfix # 212552: Please reload on change of /etc/resolv.conf - DONE in 2.0.16-4 * ppp + Use resolvconf via /etc/ppp/ip-(up|down).d/ - DONE in resolvconf package * pppconfig # 242092: Disable pppconfig's futzing with /etc/resolv.conf - DONE in 2.3.1 # 266819: Please suggest resolvconf - DONE in 2.3.18+nmu3 * pppoeconf # 212756: Eliminate /etc/ppp/ip-up.d/000usepeerdns - DONE in 1.0 * pump # 194204: Please add proper resolvconf support - DONE in 0.8.15-1 * resolvconf + Created and added to dialup and broadband tasks * squid # 200572: Please use resolvconf resolver-update notification - DONE in 2.5.3-7 * totd + Use resolvconf to update resolv.conf and to get updated nameserver list * udhcpc # 302019: Please use resolvconf - DONE in 0.9.8cvs20050124-3 * webmin-core # 223483: Please play nicely with resolvconf - DONE in 1.150-2 * webmin-wvdial # 288481: Deletes symlink at /etc/resolv.conf - DONE in 1.160-3 Credits ~~~~~~~ The basic idea for resolvconf was expressed by Emile van Bergen on the debian-devel mailing list. http://lists.debian.org/debian-devel/2003/04/msg00580.html http://lists.debian.org/debian-devel/2003/04/msg00629.html I claim any braindamage in the implementation as my own. I thank all the maintainers who have helped with this effort by adding resolvconf support to their packages. Werner Heuser, Joe Nahmias and Andreas Barth have been helpful sponsors. This document was written by Thomas Hood using some material written by John Hasler. This document is part of resolvconf. resolvconf-1.69ubuntu1/bin/0000755000000000000000000000000012076277005012621 5ustar resolvconf-1.69ubuntu1/bin/resolvconf0000755000000000000000000001277612062416774014747 0ustar #!/bin/sh # # This file is part of the resolvconf package. # set -e echo_usage() { echo "Usage: resolvconf (-d IFACE|-a IFACE|-u|--enable-updates|--disable-updates|--updates-are-enabled|--create-runtime-directories|--wipe-runtime-directories)" ; } PATH=/sbin:/bin MYNAME="${0##*/}" RUN_DIR=/run/resolvconf IFACE_DIR="${RUN_DIR}/interface" ENABLE_UPDATES_FLAGFILE="${RUN_DIR}/enable-updates" POSTPONED_UPDATE_FLAGFILE="${RUN_DIR}/postponed-update" report_err() { echo "${MYNAME}: Error: $*" >&2 ; } # Check arguments CMD="$1" case "$CMD" in -a|-d) IFACE="$2" if [ ! "$IFACE" ] ; then report_err "No interface name specified" echo_usage >&2 exit 1 fi report_iface_err() { report_err "$* not allowed in interface record name" } case "$IFACE" in */*) report_iface_err "Slash" ; exit 1 ;; *" "*) report_iface_err "Space" ; exit 1 ;; .*) report_iface_err "Initial dot" ; exit 1 ;; -*) report_iface_err "Initial hyphen" ; exit 1 ;; ~*) report_iface_err "Initial tilde" ; exit 1 ;; esac ;; -u|--enable-updates|--disable-updates|--updates-are-enabled|--create-runtime-directories|--wipe-runtime-directories) if [ "$2" ] ; then report_err "The $CMD option does not take an argument" echo_usage >&2 exit 1 fi ;; *) report_err "Command not recognized" echo_usage >&2 exit 99 ;; esac # Handle creation and wiping of run-time directories case "$CMD" in --create-runtime-directories) umask 022 if [ ! -d "$RUN_DIR" ] ; then # Create directory at the target mkdir "$RUN_CANONICALDIR" || { report_err "Error creating directory $RUN_CANONICALDIR" ; exit 1 ; } fi # The resolvconf run directory now exists. if [ ! -d "${RUN_DIR}/interface" ] ; then mkdir "${RUN_DIR}/interface" || { report_err "Error creating directory ${RUN_DIR}/interface" ; exit 1 ; } fi # The interface directory now exists. We are done. exit 0 ;; --wipe-runtime-directories) # Delete files in the resolvconf run directory (target) but not the directory itself [ -d "$RUN_DIR" ] || exit 0 rm -f "$RUN_DIR"/resolv.conf rm -f "$ENABLE_UPDATES_FLAGFILE" rm -f "$POSTPONED_UPDATE_FLAGFILE" rm -rf "$IFACE_DIR" exit 0 ;; esac [ -d "$IFACE_DIR" ] || { report_err "$IFACE_DIR either does not exist or is not a directory" ; exit 1 ; } cd "$IFACE_DIR" update_and_exit() { rm -f "$POSTPONED_UPDATE_FLAGFILE" exec run-parts ${1:+--arg="$1"} ${2:+--arg="$2"} /etc/resolvconf/update.d } # Handle commands that don't require normalized_stdin() case "$CMD" in -d) if [ ! -e "$IFACE" ] ; then exit 0 fi if [ ! -s "$IFACE" ] ; then rm -f "$IFACE" exit 0 fi rm -f "$IFACE" if [ -e "$ENABLE_UPDATES_FLAGFILE" ] ; then update_and_exit -d "$IFACE" else : >| "$POSTPONED_UPDATE_FLAGFILE" exit 0 fi ;; -u) if [ -e "$ENABLE_UPDATES_FLAGFILE" ] ; then update_and_exit -u else : >| "$POSTPONED_UPDATE_FLAGFILE" exit 0 fi ;; --enable-updates) : >| "$ENABLE_UPDATES_FLAGFILE" || exit 1 if [ -e "$POSTPONED_UPDATE_FLAGFILE" ] ; then (update_and_exit -u) || : fi exit 0 ;; --disable-updates) rm -f "$POSTPONED_UPDATE_FLAGFILE" || : rm -f "$ENABLE_UPDATES_FLAGFILE" || exit 1 exit 0 ;; --updates-are-enabled) if [ -e "$ENABLE_UPDATES_FLAGFILE" ] ; then exit 0 else exit 1 fi ;; esac # # The following function must EXACTLY the same in the resolvconf # and test-normalization scripts. And the test must pass! # ### BEGIN FUNCTION TO COPY TO THE test-normalization SCRIPT ### # # Echo stdin with: # comments removed; # initial and terminal whitespace removed; # whitespace strings replaced by single blanks; # leading zeroes removed from nameserver address fields; # first set of zero fields in an IPv6 address collapsed to '::'; # empty lines removed. normalized_stdin() { sed \ -e 's/#.*$//' \ -e 's/[[:blank:]]\+$//' \ -e 's/^[[:blank:]]\+//' \ -e 's/[[:blank:]]\+/ /g' \ -e '/^nameserver/!b ENDOFCYCLE' \ -e 's/$/ /' \ -e 's/\([:. ]\)0\+/\10/g' \ -e 's/\([:. ]\)0\([123456789abcdefABCDEF][[:xdigit:]]*\)/\1\2/g' \ -e '/::/b ENDOFCYCLE; s/ \(0[: ]\)\+/ ::/' \ -e '/::/b ENDOFCYCLE; s/:\(0[: ]\)\+/::/' \ -e ': ENDOFCYCLE' \ - | \ sed \ -e 's/[[:blank:]]\+$//' \ -e '/^$/d' } ### END FUNCTION TO COPY TO THE test-normalization SCRIPT ### case "$CMD" in -a) OLD_CONTENT="" [ -f "$IFACE" ] && OLD_CONTENT="$(cat "$IFACE")" NEW_CONTENT="$(normalized_stdin)" # Proceed only if content has changed. The test here can't # eliminate 100% of redundant invocations of update scripts # because we don't do any locking; however it certainly does # eliminate most of them. if [ "$NEW_CONTENT" = "$OLD_CONTENT" ] ; then exit 0 fi IFACE_TMPFILE="${IFACE}_new.$$" cleanup() { rm -f "$IFACE_TMPFILE" ; } trap cleanup EXIT echo "$NEW_CONTENT" > "$IFACE_TMPFILE" mv -f "$IFACE_TMPFILE" "$IFACE" if [ -e "$ENABLE_UPDATES_FLAGFILE" ] ; then update_and_exit -a "$IFACE" else : >| "$POSTPONED_UPDATE_FLAGFILE" exit 0 fi ;; esac # Don't reach here exit 99 resolvconf-1.69ubuntu1/bin/list-records0000755000000000000000000000263112062416774015166 0ustar #!/bin/bash # Need bash because we use nullglob, extglob # # list-records # # Print, one per line, names of non-empty files in the current directory # that match the shell glob patterns in /etc/resolvconf/interface-order set -e # Stores arguments (minus duplicates) in RSLT, separated by newlines # Doesn't work properly if an argument itself contain whitespace uniquify() { RSLT="" while [ "$1" ] ; do for E in $RSLT ; do [ "$1" = "$E" ] && { shift ; continue 2 ; } done RSLT="${RSLT:+$RSLT }$1" shift done } ### Compile ordered list of resolv.conf-type files ### PATTERNS="lo.inet* lo.dnsmasq lo.pdnsd lo.!(pdns|pdns-recursor) lo tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* eth* ath* wlan* ppp* *" if [ -r /etc/resolvconf/interface-order ] ; then PATTERNS="$(sed -e ' s/^[[:space:]]\+// s/[[:space:]].*// s/#.*// /\//d /^~/d /^\./d /^$/d ' /etc/resolvconf/interface-order)" fi shopt -s nullglob extglob # The nullglob option isn't essential since the test -s below will eliminate # any unexpanded patterns. The extglob option makes the glob language of # interface-order patterns as powerful as regexps. # Pathname expansion occurs on the following line resulting, in general, # in multiple instances of filenames; duplicates must be removed. uniquify $PATTERNS for FLNM in $RSLT ; do # Only list records of non-zero size [ -s "$FLNM" ] && echo "$FLNM" done exit 0 resolvconf-1.69ubuntu1/man/0000755000000000000000000000000012076277005012624 5ustar resolvconf-1.69ubuntu1/man/resolvconf.80000644000000000000000000003005712062416774015105 0ustar .TH RESOLVCONF "8" "28 May 2012" "resolvconf" "resolvconf" .SH NAME resolvconf \- manage nameserver information .SH SYNOPSIS cat \fIFILE\fR | .B resolvconf \fB\-a\fR \fIIFACE.PROG\fR .PP .B resolvconf \fB\-d\fR \fIIFACE.PROG\fR .PP .B resolvconf \fB\-u\fR .PP .B resolvconf .B \-\-enable\-updates | .B \-\-disable\-updates | .B \-\-updates\-are\-enabled | .B \-\-create\-runtime\-directories | .B \-\-wipe\-runtime\-directories .SH DESCRIPTION The resolvconf package comprises a simple database for run-time nameserver information and a simple framework for notifying applications of changes in that information. Resolvconf thus sets itself up as the intermediary between programs that supply nameserver information and applications that use that information. .PP Information is added to or removed from the database using the .B resolvconf program. See the .B OPTIONS section below for a discussion of the available options. .SH SUPPLIERS OF NAMESERVER INFORMATION Normally the .B resolvconf program is run only by network interface configuration programs such as .BR pppd (8) (for ppp interfaces); by DHCP clients such as .BR dhclient (8); by .BR ifup (8) and .BR ifdown ; and by DNS caches such as .BR dnsmasq (8) (for the loopback interface). These programs obtain nameserver information from some source and push it to .BR resolvconf . .SS dhclient The .B dhclient program, for example, may receive nameserver addresses and domain search list information during its negotiation with the DHCP server; if so, its hook script .I /etc/dhcp/dhclient\-enter\-hooks.d/resolvconf pushes this information to .B resolvconf. .SS ifup The .B ifup program can be used to configure network interfaces according to settings in .IR /etc/network/interfaces . To make .B ifup push nameserver information to .B resolvconf when it configures an interface the administrator must add .B dns\- option lines to the relevant .B iface stanza in .IR interfaces (5). The following option names are supported: .BR dns\-nameservers , .BR dns\-search , and .BR dns\-sortlist . The .B dns\-domain option is deprecated in favor of .BR dns\-search . .PP To add nameserver addresses, add a single line beginning with .BR dns\-nameservers . .PP .EX dns\-nameservers 192.168.1.254 8.8.8.8 .EE .PP Note that one or more addresses can be given on this line, separated by spaces, and note the "s" at the end of the option name, in contrast with the .IR resolv.conf (5) option name .BR nameserver . Remember that in .IR interfaces (5) each option can be used at most once per stanza. .PP To add search domain names, add a line beginning with .BR dns\-search . .PP .EX dns\-search foo.org bar.com .EE The resulting stanza might look like the following example. .PP .EX iface eth0 inet static address 192.168.1.3 netmask 255.255.255.0 gateway 192.168.1.1 dns\-nameservers 192.168.1.254 8.8.8.8 dns\-search foo.org bar.com .EE .PP N.B.: On a machine where resolvconf has just been or is about to be installed and which previously relied on a static .I /etc/resolv.conf file, the nameserver information in that static file should be migrated to the appropriate .B iface stanza(s) in .IR interfaces (5). .PP .SS Command line The administrator .I can run .B resolvconf from the command line to add or delete nameserver information, but this is not normally necessary or advisable. .SH CONSUMERS OF NAMESERVER INFORMATION Nameserver information provided to .B resolvconf is stored for use by subscribers to .BR resolvconf 's notification service. Subscriber packages that need to know when nameserver information has changed should install a script in .I /etc/resolvconf/update.d/ (or in .IR /etc/resolvconf/update\-libc.d/ : see below). For example, DNS caches such as .BR dnsmasq (8) and .BR pdnsd (8) subscribe to the notification service so that they know whither to forward queries. Client hook scripts will find the files containing nameserver information in the current directory. .SS libc The most important software package that subscribes to the notification service is the GNU C Library .IR resolver (3). This library is used by many applications that need to resolve domain names. When nameserver information is updated, the script .I /etc/resolvconf/update.d/libc generates a new version of the resolver configuration file, .IR /run/resolvconf/resolv.conf , as described below. If the new version of the file differs from the previously generated one then the hook scripts found in .IR /etc/resolvconf/update\-libc.d/ are executed. .PP The dynamically generated resolver configuration file always starts with the contents of .I /etc/resolvconf/resolv.conf.d/head and ends with the contents of .IR /etc/resolvconf/resolv.conf.d/tail . Between .I head and .I tail the .I libc script inserts dynamic nameserver information compiled from, first, information provided for configured interfaces; second, static information from .IR /etc/resolvconf/resolv.conf.d/base . Specifically, it writes: .IP " 1)" 5 up to three .B nameserver lines, ordered according to .IR /etc/resolvconf/interface\-order , possibly fewer if one of the addresses is a loopback address and the .B TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS environment variable is affirmatively set, as discussed in the .B ENVIRONMENT VARIABLES section; .IP " 2)" 5 up to one .B search line containing the combined domain search list from all "domain" and "search" input lines, also ordered according to .IR interface\-order (5); .IP " 3)" 5 all other non-comment input lines. .PP To make the resolver use this dynamically generated resolver configuration file the administrator should ensure that .I /etc/resolv.conf is a symbolic link to .IR /run/resolvconf/resolv.conf . This link is normally created on installation of the resolvconf package. The link is never modified by the .B resolvconf program itself. If you find that .I /etc/resolv.conf is not being updated, please check to make sure that the link is intact. .PP The GNU C Library resolver library isn't the only resolver library available. However, any resolver library that reads .I /etc/resolv.conf (and most of them do, in order to be compatible) should work fine with resolvconf. .PP Subscriber packages that need to know only when the resolver configuration file has changed should install a script in .I /etc/resolvconf/update\-libc.d/ rather than in .IR /etc/resolvconf/update.d/ . (For example, two packages that install .I update\-libc.d/ hook scripts are .B fetchmail and .BR squid .) This is important for synchronization purposes: scripts in .I update\-libc.d/ are run .I after .I resolv.conf has been updated; the same is not necessarily true of scripts in .IR update.d/ . .SH OPTIONS .TP \fB\-a\fR \fIIFACE.PROG\fR Add or overwrite the record .I IFACE.PROG then run the update scripts if updating is enabled. When this option is used the information must be provided to .B resolvconf on its standard input in the format of the .IR resolv.conf (5) file. Each line in the file must be terminated by a newline. .TP \fB\-d\fR \fIIFACE.PROG\fR Delete the record .I IFACE.PROG then run the update scripts if updating is enabled. .PP The string .I IFACE.PROG may not contain spaces, slashes, an initial dot, an initial hyphen or an initial tilde. It is conventionally formed from .IR IFACE , the name of the interface involved, a dot, and .IR IPROG , the name of the interface configuration program, e.g., "eth0.dhclient". .TP \fB\-u\fR Just run the update scripts (if updating is enabled). .TP With \fB\-a\fR, \fB\-d\fR or \fB\-u\fR: if updating is not enabled, schedule a delayed update. The delayed update will be carried out when updates are enabled. .TP \fB\-\-enable\-updates\fR Set the flag indicating that .B resolvconf should run update scripts when invoked in the future with \fB\-a\fR, \fB\-d\fR or \fB\-u\fR. If a delayed update was scheduled then run update scripts. .TP \fB\-\-disable\-updates\fR Clear the flag. .TP \fB\-\-updates\-are\-enabled\fR Return 0 if the flag is set, otherwise return 1. .TP \fB\-\-create\-runtime\-directories\fR Create the directories where resolver information records and other run-time files are stored. .TP \fB\-\-wipe\-runtime\-directories\fR Delete everything in the directories where resolver information records and other run-time files are stored. .SH ENVIRONMENT VARIABLES The following variables can be set in the configuration file .IR /etc/default/resolvconf . If the file does not exist you will have to create it. .TP .B REPORT_ABSENT_SYMLINK If set to "yes" then .B resolvconf will print a message when .I /etc/resolv.conf is not a symbolic link to the .BR resolvconf -generated resolver configuration file. Set to "no" to prevent the printing of this message. The default is "yes". .TP .B TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS If set to "yes" then the .I libc script will include no more nameserver addresses after the first nameserver address that is a loopback address. (In IPv4 a loopback address is any one that starts with "127.". In IPv6 the loopback address is "::1".) .IP The advantage of truncating the nameserver list after a loopback address is that doing so inhibits unnecessary changes to .I resolv.conf and thus reduces the number of instances in which the .I update\-libc.d/ scripts have to be run. When an interface is brought up or down the local caching nameserver that listens on the loopback address is still informed of the change and adapts accordingly; the clients of the resolver which use the local caching nameserver do not need to be notified of the change. A disadvantage of this mode of operation is that applications have no secondary or tertiary nameserver address to fall back on should the local caching nameserver crash. Insofar as a local nameserver crash can be regarded as an unlikely event, this is a relatively minor disadvantage. Set to "no" to disable truncation. The default is "yes". .IP A deprecated synonym for this variable is .BR TRUNCATE_NAMESERVER_LIST_AFTER_127 . .SH FILES .TP .I /etc/default/resolvconf See the ENVIRONMENT VARIABLES section. .TP .I /etc/resolvconf/interface\-order Determines the order of precedence of nameserver addresses and search domain names. See above and .BR interface\-order (5). .TP .I /etc/resolvconf/resolv.conf.d/base File containing basic resolver information. The lines in this file are included in the resolver configuration file even when no interfaces are configured. .TP .I /etc/resolvconf/resolv.conf.d/head File to be prepended to the dynamically generated resolver configuration file. Normally this is just a comment line. .TP .I /etc/resolvconf/resolv.conf.d/tail File to be appended to the dynamically generated resolver configuration file. To append nothing, make this an empty file. This file is a good place to put a resolver .B options line if one is needed, e.g., .EX options inet6 .EE .TP .I /etc/resolvconf/resolv.conf.d/original Copy of the .I /etc/resolv.conf file before the resolvconf package was installed. This file has no effect on the functioning of resolvconf; it is retained so that .I /etc/resolv.conf can be restored to its original state if the resolvconf package is removed. Note also that a copy of this file is included in the database until the first reboot after installation of the resolvconf package; this ensures that nameservers reachable before installation of resolvconf are still reachable after installation of resolvconf even though at that point not all suppliers of nameserver information may have supplied their information to .BR resolvconf (8). Note also that the administrator can choose to create a symbolic link in .I /etc/resolvconf/resolv.conf.d/ from .I tail to .I original so that the contents of .I original are always added to the end of the dynamically generated file. .SH BUGS Currently .B resolvconf does not check the sanity of the information provided to it. .SH AUTHOR Written by Thomas Hood with contributions by Nathan Stratton Treadway. .SH COPYRIGHT Copyright \(co 2004-2012 Thomas Hood. .br This is free software; see the source for copying conditions. .SH "SEE ALSO" .BR interface\-order (5), .BR resolv.conf (5), .BR resolver (3). .PP Read the resolvconf package .I README file for more in-depth information. resolvconf-1.69ubuntu1/man/interface-order.50000644000000000000000000000326112062416774015770 0ustar .TH INTERFACE\-ORDER "5" "18 May 2011" "resolvconf" "resolvconf" .SH NAME interface-order \- resolvconf configuration file .SH DESCRIPTION The file .I /etc/resolvconf/interface-order is used to control the order in which resolvconf nameserver information records are processed by those resolvconf update scripts that consult this file. (The name of the file is apt because a resolvconf nameserver information record is named after the interface with which it is associated.) .PP The file contains a sequence of shell glob patterns, one per line. The position of a record in the order is the point at which its name first matches a pattern. .PP Patterns may not contain whitespace, slashes or initial dots or tildes. Blank lines and lines beginning with a '#' are ignored. .PP Resolvconf update scripts in .I /etc/resolvconf/update.d/ that consult this file include the current default versions of .IR dnsmasq , .IR pdnsd and .IR libc . (Actually they don't read the file directly; they call the utility program .I /lib/resolvconf/list-records which lists records in the specified order and omits the names of empty records.) .SH EXAMPLE .nf # /etc/resolvconf/interface-order # Use nameservers on the loopback interface first. lo* # Next use records for Ethernet interfaces eth* # Next use records for Wi-Fi interfaces wlan* # Next use records for PPP interfaces ppp* # Last use other interfaces * .fi .SH AUTHOR Resolvconf was written by Thomas Hood . .SH COPYRIGHT Copyright \(co 2004, 2011 Thomas Hood .br This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. .SH "SEE ALSO" .BR resolvconf (8) resolvconf-1.69ubuntu1/COPYING0000644000000000000000000004310512062416774013112 0ustar GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. resolvconf-1.69ubuntu1/debian/0000755000000000000000000000000012076277005013273 5ustar resolvconf-1.69ubuntu1/debian/resolvconf.upstart0000644000000000000000000000071112062416774017101 0ustar # upstart script for resolvconf description "Initialize or finalize resolvconf" start on mounted MOUNTPOINT=/run stop on runlevel [06] pre-start script mkdir -p /run/resolvconf/interface # Request a postponed update (needed in case the base file has content). touch /run/resolvconf/postponed-update # Enable updates and perform the postponed update. resolvconf --enable-updates end script post-stop script resolvconf --disable-updates end script resolvconf-1.69ubuntu1/debian/copyright0000644000000000000000000000163612062416774015237 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Files: * Copyright: Copyright 2003-2012 Thomas Hood License: GPL-2+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. . This package is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. . You should have received a copy of the GNU General Public License along with this program. If not, see . . On Debian systems, the complete text of the GNU General Public License version 2 can be found in "/usr/share/common-licenses/GPL-2". resolvconf-1.69ubuntu1/debian/resolvconf.000resolvconf.ppp.ip-up0000755000000000000000000000102712076274066021633 0ustar #!/bin/sh # # PPP up hook script for resolvconf # # Reconfigures resolver to take into account # the appearance of the ppp interface. # # This file is part of the resolvconf package. # [ -x /sbin/resolvconf ] || exit 0 [ "$USEPEERDNS" ] || exit 0 case "$6" in nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*) # NetworkManager handles it exit 0 ;; esac R="" if [ "$DNS1" ] ; then R="${R}nameserver $DNS1 " fi if [ "$DNS2" ] ; then R="${R}nameserver $DNS2 " fi echo -n "$R" | /sbin/resolvconf -a "${PPP_IFACE}.pppd" resolvconf-1.69ubuntu1/debian/postrm0000755000000000000000000000553512076274066014561 0ustar #!/bin/sh set -e . /usr/share/debconf/confmodule MYNAME=resolvconf.postrm report() { echo "${MYNAME}: $*" ; } report_info() { report "$*" >&2 ; } OLD_RUN_DIR=/var/run is_installed() { # Same function in preinst, postinst, postrm [ "$1" ] || return 1 dpkg-query -W -f='${Status}\n' "$1" 2>/dev/null | grep -siq '^[[:alpha:]]\+ [[:alpha:]]\+ installed$' >/dev/null 2>&1 } #DEBHELPER# case "$1" in remove) if [ -L /etc/resolv.conf ] \ && [ "$(readlink -m /etc/resolv.conf)" = "/run/resolvconf/resolv.conf" ] then # /etc/resolv.conf is a resolvconf symlink # # Remove the symlink # rm -f /etc/resolv.conf # # Put a file at /etc/resolv.conf with best available content # # Best is latest dynamic content # if [ -f /run/resolvconf/resolv.conf ] ; then # (Remove "generated by resolvconf" comment which is no longer true) grep -sv '^#' /run/resolvconf/resolv.conf > /etc/resolv.conf || : rm -f /run/resolvconf/resolv.conf # If nothing is left over, remove the file entirely [ -s /etc/resolv.conf ] || rm -f /etc/resolv.conf fi # # Second best is "original" content # if [ ! -f /etc/resolv.conf ] \ && [ -f /etc/resolvconf/resolv.conf.d/original ] then cp -a /etc/resolvconf/resolv.conf.d/original /etc/resolv.conf fi fi report_info "Reboot recommended" db_input high resolvconf/reboot-recommended-after-removal || : db_go || : # Notify packages of the removal of resolvconf if [ -d /usr/lib/resolvconf/dpkg-event.d ] ; then NOTIFICATION_HOOK_SCRIPTS="$(cd /usr/lib/resolvconf/dpkg-event.d >/dev/null ; run-parts --test .)" for SCRPT in $NOTIFICATION_HOOK_SCRIPTS ; do PKG="${SCRPT#./}" if is_installed "$PKG" ; then SCRPT="/usr/lib/resolvconf/dpkg-event.d/$PKG" if [ -x "$SCRPT" ] ; then "$SCRPT" remove || : fi fi done fi ;; purge) # # Remove all remaining cruft # if [ -L /etc/resolvconf/run ] ; then rm -f /etc/resolvconf/run elif [ -d /etc/resolvconf/run ] ; then rm -rf /etc/resolvconf/run fi rm -f /etc/resolvconf/resolv.conf.d/tail rm -f /etc/resolvconf/resolv.conf.d/original rm -f /etc/resolvconf/update.d/bind rm -f /etc/resolvconf/update.d/bind.dpkg-old rm -f /etc/default/resolvconf rm -f /etc/dhcp3/dhclient-enter-hooks.d/resolvconf rm -f /etc/init.d/resolvconf.dpkg-old rm -rf "${OLD_RUN_DIR}/resolvconf" || : rm -rf /run/resolvconf || : ;; # disappear|upgrade) # Don't do anything on upgrade # ;; # failed-upgrade) # Don't do anything because we don't do anything here (in the postrm) on upgrade # ;; abort-install) rm -f /run/resolvconf/packages-to-notify # In the preinst we create directories # but there is no immediate need to remove them if there is an error. ;; # abort-upgrade) # Don't do anything. # In the preinst we create directories # but there is no immediate need to remove them if there is an error. # ;; esac exit 0 resolvconf-1.69ubuntu1/debian/control0000644000000000000000000000251512076274066014705 0ustar Source: resolvconf Section: net Priority: optional Maintainer: Ubuntu Developers XSBC-Original-Maintainer: resolvconf maintainers Uploaders: Thomas Hood , Marco Nenciarini Build-Depends: debhelper (>= 8) Homepage: http://alioth.debian.org/projects/resolvconf/ Vcs-Git: git://git.debian.org/git/resolvconf/resolvconf.git Vcs-Browser: http://git.debian.org/?p=resolvconf/resolvconf.git DM-Upload-Allowed: yes Standards-Version: 3.9.4.0 Package: resolvconf Architecture: all Enhances: isc-dhcp-client, dhcpcd, pump, udhcpc, ppp, ifupdown, network-manager, dnsmasq, pdnsd, totd, libc6, nscd Depends: lsb-base, ${misc:Depends} Pre-Depends: initscripts (>= 2.88dsf-13.10) Breaks: dnscache-run, dhcp3-client (<< 4.1.1-P1-15+squeeze1) Description: name server information handler Resolvconf is a framework for keeping up to date the system's information about name servers. It sets itself up as the intermediary between programs that supply this information (such as ifup and ifdown, DHCP clients, the PPP daemon and local name servers) and programs that use this information (such as DNS caches and resolver libraries). . This package may require some manual configuration. Please read the README file for detailed instructions. resolvconf-1.69ubuntu1/debian/changelog0000644000000000000000000022712612076276673015171 0ustar resolvconf (1.69ubuntu1) raring; urgency=low * Merge from Debian. Remaining changes: (LP: #1085756) - Make /etc/resolv.conf a relative symlink so that it works when setting up chroots. - Instead of throwing an error that aborts the upgrade when /etc/resolv.conf is immutable, pop a debconf error message to let the user know what's happening, then clear the immutable flag and continue with the installation. LP: #989585. - debian/config, debian/templates, debian/postinst: if we don't know that /etc/resolv.conf was being dynamically managed before install (in at least some cases), link the original contents of /etc/resolv.conf to /etc/resolvconf/resolv.conf.d/tail so that any statically configured nameservers aren't lost. LP: #923685. - Use an upstart job instead of sysvinit script. - Pre-Depend on the /run-providing version of initscripts instead of depending, so that the preinst does the right thing when creating /run/resolvconf/interfaces instead of getting clobbered later by a bind mount on initscripts upgrade. LP: #922491. - Completely drop the standard_run_subdirs_created helper function from debian/postinst, since it serves no purpose here. - postinst: Set resolvconf/linkify-resolvconf to false after initial conversion, ensuring upgrades won't convert /etc/resolv.conf to a symlink if the user manually converted it back to plain text. (LP: #922677) - Move the #DEBHELPER# token in debian/postinst to after the resolv.conf symlink is set, so the init script can actually start (since it expects /etc/resolv.conf to be a symlink). - Eliminate all references to /etc/resolvconf/run. This should all be done directly in /run, there is no reason to support making any of this configurable with a symlink since we already have a versioned dependency on the version of initscripts that introduces the /run transition. - Also remove debian/triggers to avoid needlessly calling resolvconf's postinst. (LP: #931335) * Fix previous mis-merge of debian/postinst as well as the few other comments from the bug report. (LP: #1085862) -- Stéphane Graber Fri, 18 Jan 2013 11:52:10 -0500 resolvconf (1.69) unstable; urgency=low * [276fc24] Bump Standards-Version; no changes required * [6982da6] README: Name packages that clobber /etc/resolv.conf * [4cb082a] README: Update * [044e9a3] ip-up.d/000resolvconf: Do nothing if USEPEERDNS not set * [d988a9e] if-up.d/000resolvconf: Silently (for now) accept option name 'dns-nameserver' as a synonym for 'dns-nameservers' in anticipation of support in ifupdown (no sooner than wheezy+1) for duplicate options in a stanza, after which it will make sense to specify multiple nameserver addresses on equally many "dns-nameserver" lines * [e0db2cb] Deal with obsolete conf files (Closes: #687507, #681623) -- Thomas Hood Mon, 17 Dec 2012 12:00:00 +0100 resolvconf (1.68ubuntu1) raring; urgency=low * Merge from Debian. Remaining changes: - Make /etc/resolv.conf a relative symlink so that it works when setting up chroots. - Instead of throwing an error that aborts the upgrade when /etc/resolv.conf is immutable, pop a debconf error message to let the user know what's happening, then clear the immutable flag and continue with the installation. LP: #989585. - debian/config, debian/templates, debian/postinst: if we don't know that /etc/resolv.conf was being dynamically managed before install (in at least some cases), link the original contents of /etc/resolv.conf to /etc/resolvconf/resolv.conf.d/tail so that any statically configured nameservers aren't lost. LP: #923685. - Use an upstart job instead of sysvinit script. - Pre-Depend on the /run-providing version of initscripts instead of depending, so that the preinst does the right thing when creating /run/resolvconf/interfaces instead of getting clobbered later by a bind mount on initscripts upgrade. LP: #922491. - Completely drop the standard_run_subdirs_created helper function from debian/postinst, since it serves no purpose here. - postinst: Set resolvconf/linkify-resolvconf to false after initial conversion, ensuring upgrades won't convert /etc/resolv.conf to a symlink if the user manually converted it back to plain text. (LP: #922677) - Move the #DEBHELPER# token in debian/postinst to after the resolv.conf symlink is set, so the init script can actually start (since it expects /etc/resolv.conf to be a symlink). - Eliminate all references to /etc/resolvconf/run. This should all be done directly in /run, there is no reason to support making any of this configurable with a symlink since we already have a versioned dependency on the version of initscripts that introduces the /run transition. - Also remove debian/triggers to avoid needlessly calling resolvconf's postinst. (LP: #931335) -- Stéphane Graber Thu, 25 Oct 2012 13:59:30 +0200 resolvconf (1.68) unstable; urgency=low * [1527598] Add sk.po. Thanks to Slavko (Closes: #683672) * [7713764] Update resolvconf's ppp hook also to exit when passed /org/freedesktop/NetworkManager/PPP/* (LP: #994575, LP: #1046154) -- Thomas Hood Mon, 10 Sep 2012 11:46:05 +0200 resolvconf (1.67ubuntu2) quantal; urgency=low * Apply patch by MarianoAbsatz to remove remaining reference to /etc/resolvconf/run (LP: #1035076) * Update ppp hooks to also exit when passed /org/freedesktop/NetworkManager/PPP/* (LP: #994575) -- Stéphane Graber Fri, 07 Sep 2012 18:01:59 -0400 resolvconf (1.67ubuntu1) quantal; urgency=low * Merge from Debian. Remaining changes: (LP: #994575, LP: #999337, LP: #1012355) - Make /etc/resolv.conf a relative symlink so that it works when setting up chroots. - Instead of throwing an error that aborts the upgrade when /etc/resolv.conf is immutable, pop a debconf error message to let the user know what's happening, then clear the immutable flag and continue with the installation. LP: #989585. - debian/config, debian/templates, debian/postinst: if we don't know that /etc/resolv.conf was being dynamically managed before install (in at least some cases), link the original contents of /etc/resolv.conf to /etc/resolvconf/resolv.conf.d/tail so that any statically configured nameservers aren't lost. LP: #923685. - Use an upstart job instead of sysvinit script. - Pre-Depend on the /run-providing version of initscripts instead of depending, so that the preinst does the right thing when creating /run/resolvconf/interfaces instead of getting clobbered later by a bind mount on initscripts upgrade. LP: #922491. - Completely drop the standard_run_subdirs_created helper function from debian/postinst, since it serves no purpose here. - postinst: Set resolvconf/linkify-resolvconf to false after initial conversion, ensuring upgrades won't convert /etc/resolv.conf to a symlink if the user manually converted it back to plain text. (LP: #922677) - Move the #DEBHELPER# token in debian/postinst to after the resolv.conf symlink is set, so the init script can actually start (since it expects /etc/resolv.conf to be a symlink). - Eliminate all references to /etc/resolvconf/run. This should all be done directly in /run, there is no reason to support making any of this configurable with a symlink since we already have a versioned dependency on the version of initscripts that introduces the /run transition. - Also remove debian/triggers to avoid needlessly calling resolvconf's postinst. (LP: #931335) -- Stéphane Graber Fri, 22 Jun 2012 17:29:50 -0400 resolvconf (1.67) unstable; urgency=low [ Thomas Hood ] * [5e645ac] Use more conventional name for record created by resolvconf's pppd hook script * [58da88f] Change resolvconf's pppd hook script such that it does not call resolvconf if pppd was run by nm-pptp-service (See LP#994575) * [16b4ae5] Bump Standards-Version; no changes -- Thomas Hood Tue, 19 Jun 2012 13:17:56 +0200 resolvconf (1.66) unstable; urgency=low [ Thomas Hood ] * [ed8ab34] Silence lsattr error message in postinst * [23217c3] resolvconf(8): List allowed dns-* interfaces(5) options * [b69c873] and describe more verbosely how the libc update script generates the dynamic resolv.conf file (Fixes LP##990660 and LP#999337). Thanks to Nathan Stratton Treadway. * [aa99b9b] update.d/libc: Only run hook scripts if /etc/resolv.conf is a symbolic link to the updated dynamic file. -- Thomas Hood Fri, 08 Jun 2012 10:26:53 +0200 resolvconf (1.65ubuntu4) quantal; urgency=low * Also remove debian/triggers to avoid needlessly calling resolvconf's postinst. (LP: #931335) -- Stéphane Graber Mon, 14 May 2012 16:40:55 -0400 resolvconf (1.65ubuntu3) quantal; urgency=low [ Stéphane Graber ] * Call db_go after the db_input command so that the debconf error message is actually shown to the user. [ Thomas Hood ] * Remove redundant code from resolvconf postinst (LP: #931335) -- Stéphane Graber Mon, 14 May 2012 12:49:42 -0400 resolvconf (1.65ubuntu2) quantal; urgency=low [ Stéphane Graber ] * In is_immutable_file, if lsattr doesn't return anything on stdout, return 1 and hide stderr. This fixes lsattr failing on non-ext filesystems. (LP: #994539) [ Steve Langasek ] * Fix syntax of db_input command, which is part of why we're seeing failures in bug #994539. -- Stéphane Graber Mon, 07 May 2012 16:01:08 -0700 resolvconf (1.65ubuntu1) quantal; urgency=low * Merge from debian unstable. Remaining changes: - Make /etc/resolv.conf a relative symlink so that it works when setting up chroots. - Instead of throwing an error that aborts the upgrade when /etc/resolv.conf is immutable, pop a debconf error message to let the user know what's happening, then clear the immutable flag and continue with the installation. LP: #989585. - debian/config, debian/templates, debian/postinst: if we don't know that /etc/resolv.conf was being dynamically managed before install (in at least some cases), link the original contents of /etc/resolv.conf to /etc/resolvconf/resolv.conf.d/tail so that any statically configured nameservers aren't lost. LP: #923685. - Use an upstart job instead of sysvinit script. - Pre-Depend on the /run-providing version of initscripts instead of depending, so that the preinst does the right thing when creating /run/resolvconf/interfaces instead of getting clobbered later by a bind mount on initscripts upgrade. LP: #922491. - Completely drop the standard_run_subdirs_created helper function from debian/postinst, since it serves no purpose here. - postinst: Set resolvconf/linkify-resolvconf to false after initial conversion, ensuring upgrades won't convert /etc/resolv.conf to a symlink if the user manually converted it back to plain text. (LP: #922677) - Make resolvconf exit 0 when /etc/resolv.conf isn't a symlink (instead of exit 1) and update the error message. - Move the #DEBHELPER# token in debian/postinst to after the resolv.conf symlink is set, so the init script can actually start (since it expects /etc/resolv.conf to be a symlink). - Eliminate all references to /etc/resolvconf/run. This should all be done directly in /run, there is no reason to support making any of this configurable with a symlink since we already have a versioned dependency on the version of initscripts that introduces the /run transition. -- Stéphane Graber Thu, 03 May 2012 21:17:35 -0400 resolvconf (1.65) unstable; urgency=low [ Thomas Hood ] * [3f0a1a1] Create /etc/resolvconf/run and its target and subdir in the postinst as well as in the preinst (Closes: #662724) * [ae16ea8] In postinst, as last resort, create /run/resolvconf/ even if /run isn't a tmpfs. * [25711bf] ifupdown hook scripts: Don't return error to ifupdown (Addresses #661591 so far as resolvconf is concerned) * [8da29c3] Document that list-records doesn't list empty records. Add patterns for biosdevnames (See LP#949473) * [a998de3] Update default interface order patterns in list-records * [94baf61] resolvconf(8): Update ref to dhclient hook script (See LP#953257) -- Thomas Hood Tue, 13 Mar 2012 09:09:35 +0100 resolvconf (1.64) unstable; urgency=low [ Thomas Hood ] * [da2bfa4] Wipe more selectively (Closes: #657259) * [e5fbaef] Ubuntu backport: on enable-updates, exit with nonzero status if and only if updates could not be enabled (i.e., ignore update script errors). * [e1cb96e] Bump Standards-Version -- Marco Nenciarini Sun, 04 Mar 2012 17:44:13 +0100 resolvconf (1.63ubuntu12) precise-proposed; urgency=low * Instead of throwing an error that aborts the upgrade when /etc/resolv.conf is immutable, pop a debconf error message to let the user know what's happening, then clear the immutable flag and continue with the installation. LP: #989585. -- Steve Langasek Wed, 02 May 2012 12:51:50 -0700 resolvconf (1.63ubuntu11) precise; urgency=low * debian/config: Update regexp to allow multiple DNS servers on a single dns-nameservers line. -- Stéphane Graber Thu, 29 Mar 2012 16:38:31 -0400 resolvconf (1.63ubuntu10) precise; urgency=low * debian/config: handle 'inet6 dhcp' interfaces the same as 'inet dhcp' ones for detecting dynamic DNS information. * bin/list-records, etc/resolvconf/interface-order: cherry-pick upstream support for biosdevname-style interface names. Thanks, Thomas! LP: #949473. * man/resolvconf.8: point to the right directory for dhcp hooks. LP: #953257. -- Steve Langasek Sat, 17 Mar 2012 12:13:34 -0700 resolvconf (1.63ubuntu9) precise; urgency=low * debian/config: dns-nameservers lines are only valid if they take an ipv4 or ipv6 value, and earlier bugs in netcfg may spit out lines with garbage values instead. If we find one of these on initial configuration, don't consider it an example of valid dynamically-provided DNS information. LP: #932275. -- Steve Langasek Fri, 24 Feb 2012 13:01:08 -0800 resolvconf (1.63ubuntu8) precise; urgency=low * Use a post-stop script for disabling resolvconf, not a pre-stop script, since upstart seems to be silently ignoring pre-stop when there's no main process. LP: #933566. * debian/postinst: mkdir -p /run/resolvconf/interface again, just in case there's been a reboot between the preinst and postinst which would wipe out /run. May or may not address LP 933035. * debian/config, debian/templates, debian/postinst: if we don't know that /etc/resolv.conf was being dynamically managed before install (in at least some cases), link the original contents of /etc/resolv.conf to /etc/resolvconf/resolv.conf.d/tail so that any statically configured nameservers aren't lost. LP: #923685. * when called with --enable-updates, ignore failures from the hooks. LP: #927803. -- Steve Langasek Mon, 20 Feb 2012 19:17:32 +0000 resolvconf (1.63ubuntu7) precise; urgency=low [ Stéphane Graber ] * Revert change from 1.63ubuntu5 where /etc/resolv.conf would be linkified by the upstart/sysvinit job. This wasn't working as / wasn't necessarily writable at the time. Instead, make the link at package install time but make it a relative link which should take care of the chroot usecase where you want to copy /etc/resolv.conf from outside the chroot into the chroot. Detect old flag file (/var/lib/resolvconf/convert) and re-run the conversion code if it's present (to try and fix broken systems). Use readlink -m when checking the link's destination. (LP: #924836) [ Steve Langasek ] * Use readlink -m also in the postrm, to account for our relative links -- Stéphane Graber Thu, 02 Feb 2012 14:28:45 -0500 resolvconf (1.63ubuntu6) precise; urgency=low * Pre-Depend on the /run-providing version of initscripts instead of depending, so that the preinst does the right thing when creating /run/resolvconf/interfaces instead of getting clobbered later by a bind mount on initscripts upgrade. LP: #922491. * Completely drop the standard_run_subdirs_created helper function from debian/postinst, since it serves no purpose here. -- Steve Langasek Fri, 27 Jan 2012 14:14:53 -0800 resolvconf (1.63ubuntu5) precise; urgency=low [ Stéphane Graber ] * Instead of creating the symlink in debian/postinst, create a flag at /var/lib/resolvconf/convert and create the symlink in the upstart or sysvinit job. On regular machines this will convert it immediately but on chroots that'll keep the old resolv.conf file. (LP: #922578) [ Steve Langasek ] * Call dh_installinit with -r, to not stop/start resolvconf on upgrade; that just leaves a window when updates aren't happening, which doesn't benefit us. -- Stéphane Graber Fri, 27 Jan 2012 14:19:22 -0500 resolvconf (1.63ubuntu4) precise; urgency=low * dhclient hook: Only trigger if /etc/resolv.conf is a symlink. * postinst: Set resolvconf/linkify-resolvconf to false after initial conversion, ensuring upgrades won't convert /etc/resolv.conf to a symlink if the user manually converted it back to plain text. (LP: #922677) * Make resolvconf exit 0 when /etc/resolv.conf isn't a symlink (instead of exit 1) and update the error message. -- Stéphane Graber Fri, 27 Jan 2012 12:23:34 -0500 resolvconf (1.63ubuntu3) precise; urgency=low * Move the #DEBHELPER# token in debian/postinst to after the resolv.conf symlink is set, so the init script can actually start (since it expects /etc/resolv.conf to be a symlink). -- Mathieu Trudel-Lapierre Sun, 08 Jan 2012 21:12:34 +0100 resolvconf (1.63ubuntu2) precise; urgency=low * Adjust the upstart job to run as soon as /run is mounted, instead of right before udev starts. * Fix obfuscated call in upstart job to 'resolvconf --create-runtime-directories'; this should mkdir -p directly. * Eliminate all references to /etc/resolvconf/run. This should all be done directly in /run, there is no reason to support making any of this configurable with a symlink since we already have a versioned dependency on the version of initscripts that introduces the /run transition. * Further reduce the calls to resolvconf in the upstart job, there's no reason to call out to another shell script for a 'touch' command. * Add missing #DEBHELPER# token in debian/postinst, replacing by-hand munging of /etc/rc?.d symlinks. * Correct wrong use of dh_installinit --upstart-only, which is only for upstart jobs that were never init scripts before; and don't pass --noscripts, because we really do want the upstart job run on install. -- Steve Langasek Wed, 04 Jan 2012 15:40:59 -0800 resolvconf (1.63ubuntu1) precise; urgency=low [ Thomas Hood ] * Debian fixed bugs (LP: #797339, #871058, #471975, #378844, #894417) * Differences from Debian: - /sbin/resolvconf: + Exit if /etc/resolv.conf is not a symlink - debian/rules: + Install upstart script rather than initscript (LP: #366967, #750423) - debian/{pre,post}inst + Migrate (to /run) from /var/run, not from /lib/init/rw. + [0706f28] Remove old Sys V init scripts and symlinks * Thanks to Sander van Grieken for his assistance with this release. -- Thomas Hood Tue, 20 Dec 2011 22:00:00 +0100 resolvconf (1.63) unstable; urgency=low [ Thomas Hood ] * [a83fce3] Depend on a later version of the initscripts package * [cfc8349] Use variable instead of hard-coded path for old run dir in maintainer scripts, to help shrink the Ubuntu diff. * [9921902] Update and improve resolvconf(8) * [719dc9b] Run update on boot (Closes: #651801, #651827) * [5fc985c] Don't trigger on reconfigure (Closes: #651803) -- Marco Nenciarini Sat, 17 Dec 2011 23:25:04 +0100 resolvconf (1.62) unstable; urgency=low [ Thomas Hood ] * [0352a85] postrm: On removal restore original resolv.conf if current (dynamic) resolv.conf has no content. (Closes: #644956) Thanks to Josep Lladonosa Capell. * [7cdfa73] Move logic details from initscript to /sbin/resolvconf; for this purpose add new options to /sbin/resolvconf: --enable-updates, --disable-updates, --updates-are-enabled, --create-runtime-directories. * [7cdfa73] Eliminate "-i" option supplied to update scripts and the code in /etc/resolvconf/update.d/libc that made use of this. [ Marco Nenciarini ] * [e175b76] Remove hardcoded path from resolvconf's invocation in maintainer scripts. Thanks to lintian -- Marco Nenciarini Wed, 30 Nov 2011 19:05:04 +0100 resolvconf (1.61) unstable; urgency=low * [cbb5105] list-records: Add comment re: extglob; speed up final loop * [4492943] Eliminate bashisms from /sbin/resolvconf. (Other scripts in this package still use bash, though, so this does not close wish #519364.) Thanks to Stefan Monnier * [63da54b] update.d/libc: Only run-parts update-libc.d/ if the latter exists. (Closes: #642965) -- Thomas Hood Mon, 26 Sep 2011 09:42:11 +0200 resolvconf (1.60) unstable; urgency=low [ Marco Nenciarini ] * [c30024e] Switch vcs fields to git * [4041409] Add debian/gbp.conf to make easy the usage of git-buildpackage [ Thomas Hood ] * [18e2fac] Update es.po thanks to Javier Fernández-Sanguino (Closes: #642360) * [18e2fac] Include resolv.conf.d/base information in resolv.conf *after* dynamic information, rather than before (Closes: #642222) -- Marco Nenciarini Fri, 23 Sep 2011 09:31:53 +0200 resolvconf (1.59) unstable; urgency=low * dhclient-enter-hooks.d/resolvconf: Add support for dhclient DHCPv6 (Closes: #635470) * postinst: Fail with message if /etc/resolv.conf is immutable (Closes: #635775) * Mention in resolvconf(8) that /etc/default/resolvconf has to be created if it is to be used to set resolvconf environment variables (Closes: #633014) * Drop outdated id.po -- Thomas Hood Tue, 23 Aug 2011 10:00:00 +0200 resolvconf (1.58) unstable; urgency=low [ Thomas Hood ] * Update README * Update debconf template translations: * da.po thanks to Joe Dalton (Closes: #630241) * cs.po thanks to Miroslav Kure (Closes: #630669) * nl.po thanks to Jeroen Schot (Closes: #631499) * pt.po thanks to Pedro Ribeiro (Closes: #631569) [ Marco Nenciarini ] * Update italian debconf translation * debian/rules: Add build-arch and build-indep target, as required by policy. -- Marco Nenciarini Wed, 29 Jun 2011 00:37:58 +0200 resolvconf (1.57) unstable; urgency=low [ Marco Nenciarini ] * Update debconf template translations: * fr.po thanks to Christian Perrier (Closes: #629560) * Fix typo in prerm script -- Marco Nenciarini Wed, 08 Jun 2011 12:22:33 +0200 resolvconf (1.56) unstable; urgency=low [ Thomas Hood ] * Create /etc/resolvconf/run as a directory if no tmpfs is available into which it can symlink. (Closes: #629186) * Eliminate warning brought to light by piuparts: * Grep /etc/network/interfaces only if it exists * Run dpkg-trigger with --no-await * Update README * Update debconf template translations: * sv.po thanks to Martin Bagge (Closes: #629022) * ru.po thanks to Yuri Kozlov (Closes: #629165) * de.po thanks to Helge Kreutzmann (Closes: #629201) * eu.po thanks to Iñaki Larrañaga Murgoitio (Closes: #629411) -- Thomas Hood Mon, 06 Jun 2011 15:00:00 +0200 resolvconf (1.55) unstable; urgency=medium [ Thomas Hood ] * Include old update.d/bind script for illustration purposes as /usr/share/doc/resolvconf/resolvconf-update-bind. * Use /usr/lib/resolvconf/dpkg-event.d instead of a /etc/... path for dpkg event hook scripts. The scripts don't need to be configuration files. * In postrm print a message and put up debconf note recommending reboot. (Closes: #628524) * Remove comments from /etc/resolv.conf on removal. * Remove /lib/init/rw/resolvconf on purge. (Closes: #628669) * Update debconf template translation: * eu.po thanks to Iñaki Larrañaga Murgoitio (Closes: #628719) * Clean up many .po headers * Update README -- Thomas Hood Thu, 31 May 2011 12:00:00 +0200 resolvconf (1.54) unstable; urgency=low [ Thomas Hood ] * Put "exit 0" at the end of each maintainer script -- Thomas Hood Wed, 25 May 2011 13:00:00 +0200 resolvconf (1.53) unstable; urgency=low [ Thomas Hood ] * Dpkg trigger is now called 'resolvconf-enable-updates' and is now intended only for internal use. * Other packages are notified of the installation of resolvconf via hook scripts as described in the "Usage information for maintainers" section of the resolvconf README file. (Closes: #567059, #627691) * Update my e-mail address in various places * Update debconf template translation: * cs.po thanks to Miroslav Kure (Closes: #627440) * Remove /etc/resolvconf/update.d/bind (Closes: #608933, #268073). Instead of this, the bind9 package should include a hook script /etc/resolvconf/update.d/bind9 as has been requested in #483098. * Due to changes in Debian infrastructure change debian/control fields Vcs-Svn and Vcs-Browser. Ref: http://lists.debian.org/debian-devel-announce/2011/05/msg00009.html -- Thomas Hood Wed, 20 May 2011 12:00:00 +0200 resolvconf (1.52) unstable; urgency=low [ Thomas Hood ] * Add debian/source/format at lintian's suggestion * Update debconf template translations: * ru.po thanks to Yuri Kozlov (Closes: #625623) * sv.po thanks to Martin Bagge (Closes: #625786) * nl.po thanks to Vincent Zweije (Closes: #625896) * de.po thanks to Helge Kreutzmann (Closes: #626030) * da.po thanks to Joe Dalton (Closes: #626302) * fr.po thanks to Christian PERRIER, Steve Petruzzello and David Prévot * pt.po thanks to Pedro Ribeiro (Closes: #626675) * Remove long outdated pt_BR.po * Don't run mkdir with -v in debian/p*inst -- Thomas Hood Wed, 13 May 2011 12:00:00 +0200 resolvconf (1.51) experimental; urgency=low [ Thomas Hood ] * Rename 'TRUNCATE_NAMESERVER_LIST_AFTER_127' to 'TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS' and make it cause the nameserver list to be truncated also after an IPv6 loopback address. (Closes: #568820) * Normalize contents of records -- i.e., strip out comments and whitespace and shorten IPv6 nameserver addresses. This makes it easier to implement the change above. * Add debian/test-normalization script to test the normalization code. * Update resolvconf/downup-interfaces template again. -- Thomas Hood Tue, 03 May 2011 12:00:00 +0200 resolvconf (1.50) experimental; urgency=low [ Thomas Hood ] * Also migrate non-symlinked directory /etc/resolvconf/run to /run/resolvconf. * Be interested in own trigger and enable updates only when triggered. This could eliminate some superfluous updates on installation. (Evidence that a package is allowed trigger itself: http://lists.debian.org/debian-dpkg/2007/10/msg00175.html) * Add section "Usage information for maintainers" to the README file discussing the new trigger. * Document the "original" file in resolvconf(8). (Closes: #414692) * Improve markup of resolvconf(8). -- Thomas Hood Wed, 27 Apr 2011 12:00:00 +0200 resolvconf (1.49) experimental; urgency=low [ Thomas Hood ] * Standardly keep run-time data in /run instead of /lib/init/rw; migrate from /lib/init/rw to /run in the postinst. (Closes: #621503). Thanks to Roger Leigh for his help. * Create run-time data directories in the preinst instead of in the postinst. (Closes: #551999, #563386). (Do this in /run if that is already already available, otherwise in /lib/init/rw, otherwise in /etc/resolvconf.) Now when other packages call resolvconf before resolvconf's postinst runs, the data are not lost and no error message is printed. * If someone has run resolvconf while updates were disabled, update when updates are enabled. * Include the contents of the original resolv.conf file in the database until the first reboot after installation. The old behavior was to omit these contents unless link-tail-to-original was selected with the result that information was missing from resolv.conf until ifdown-ifup cycles. The new behavior is not correct either, since nameserver addresses are not removed when corresponding interfaces are deconfigured, but should have less unpleasant consequences than the old behavior. * Update the debconf template that discusses the problem just described. Whereas before it was recommended that the administrator down and up network interfaces, it is now recommended that the administrator reboot the system. * Add da.po. (Closes: #623079) Thanks to Joe Dalton. * Run debconf-updatepo. * Add Depends on initscripts >= 2.88dsf-13.3 which enables /run in its postinst, ensuring that /run is available to our postinst. * Activate the "resolvconf-event" trigger in postinst and in postrm in order to induce other packages to take notice of resolvconf being installed (configured) or removed. When triggered and resolvconf is installed, interested packages possessing name server information should send it to resolvconf. See README for details. (Closes: #567059) * Remove /etc/dhcp3/dhclient-enter-hooks.d/resolvconf which is obsolete; remove it on purge and declare a Breaks: old versions of dhcp3-client which used it. (Closes: #591022). * Use dh_installifupdown to install ifupdown hook scripts and, consequently, Build-Depend on newer debhelper. * Update debian/compat to 8. * Bump Standards-Version to 3.9.2.0. * Tidy up all maintainer scripts. [ Marco Nenciarini ] * debian/control: updated Thomas Hood's email address. -- Marco Nenciarini Tue, 19 Apr 2011 22:30:30 +0200 resolvconf (1.48ubuntu1) natty; urgency=low * Merge from debian unstable. Remaining changes: - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. + make sure all run files are sent to /var/run, not /lib/init/rw + update regex to check that /var/run is a tmpfs (LP: #386822) + fix typo in comments - debian/rules: + don't install the init script in runlevels 0 and 6. - debian/postrm: + remove /var/run/resolvconf, not /lib/init/rw/resolvconf + also purge /var/run/resolvconf/interface -- Bhavani Shankar Thu, 13 Jan 2011 19:22:32 +0530 resolvconf (1.48) unstable; urgency=low [ Thomas Hood ] * README: + Drop support for old bind package and update instructions for configuring bind9 to work with resolvconf. (Closes: #586326) * /etc/resolvconf/update.d/bind + Allow NAMED_RUN_DIR to be overridden in /etc/default/resolvconf. (Closes: #602204) * debian/control: + Drop obsolete dependency constraints from Breaks + Update Uploaders -- Marco Nenciarini Wed, 12 Jan 2011 20:15:47 +0100 resolvconf (1.47ubuntu1) natty; urgency=low * Merge from debian unstable. Remaining changes: - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. + make sure all run files are sent to /var/run, not /lib/init/rw + update regex to check that /var/run is a tmpfs (LP: #386822) + fix typo in comments - debian/rules: + don't install the init script in runlevels 0 and 6. - debian/postrm: + remove /var/run/resolvconf, not /lib/init/rw/resolvconf + also purge /var/run/resolvconf/interface -- Bhavani Shankar Sat, 04 Dec 2010 00:54:18 +0530 resolvconf (1.47) unstable; urgency=low [ Thomas Hood ] * Cause ifdown to delete ${IFACE}.udhcpc (Closes: #605215) * Remove workaround for #196865 which was fixed in ifupdown << oldstable [ Marco Nenciarini ] * Bump Standards-Version to 3.9.1.0; no changes required -- Marco Nenciarini Wed, 01 Dec 2010 16:21:54 +0100 resolvconf (1.46ubuntu1) maverick; urgency=low * Merge from debian unstable (LP: #605116), remaining changes: - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. + make sure all run files are sent to /var/run, not /lib/init/rw + update regex to check that /var/run is a tmpfs (LP: #386822) + fix typo in comments - debian/rules: + don't install the init script in runlevels 0 and 6. - debian/postrm: + remove /var/run/resolvconf, not /lib/init/rw/resolvconf + also purge /var/run/resolvconf/interface -- Lorenzo De Liso Tue, 13 Jul 2010 19:35:38 +0200 resolvconf (1.46) unstable; urgency=low [ Thomas Hood ] * Add hook script for dhclient from the new isc-dhcp-client package (Closes: #583991, #570896). The new script, in /etc/dhcp/, has the same contents as the old one in /etc/dhcp3/. Please note that any local changes made to the old one should be made to the new script as well. * Reiterate the latter advice in a NEWS item. * Update the status of many TODO items in the README file. There has been some progress in the past five years. * Drop all dependencies on package versions older than those in oldstable. * Add Breaks: dnscache-run which overwrites /etc/resolv.conf. See #582755 for my request that dnscache-run be modified to be compatible with resolvconf. * Bump Standards-Version to 3.9.0.0. As advised, demote remaining Conflicts to Breaks. * Drop Enhances: for obsolete packages dhcp-client and bind * Add Enhances: isc-dhcp-client * Add some lintian overrides. [ Marco Nenciarini ] * Depend on debhelper >= 6.0.7~ to have dh_lintian * Update copyright file to refer to GPL-2 instead of GPL which is actually a symlink to GPL-3 * Add lintian overrides for breaks-without-version. -- Marco Nenciarini Mon, 12 Jul 2010 12:41:37 +0200 resolvconf (1.45ubuntu1) lucid; urgency=low * Merge from debian unstable, remaining changes (LP: #495998): - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. - debian/rules: + don't install the init script in runlevels 0 and 6. * debian/postinst: - make sure all run files are sent to /var/run, not /lib/init/rw - update regex to check that /var/run is a tmpfs (LP: #386822) - fix typo in comments * debian/postrm: - remove /var/run/resolvconf, not /lib/init/rw/resolvconf - also purge /var/run/resolvconf/interface -- Mathieu Trudel Wed, 30 Dec 2009 16:17:58 -0500 resolvconf (1.45) unstable; urgency=low [ Thomas Hood ] * Bump standards version * Add note to man page that tail file is a good place for a resolver "options" line (Closes: #533297) * Add eu.po (Closes: #534558) -- Marco Nenciarini Thu, 13 Aug 2009 20:01:51 +0200 resolvconf (1.44ubuntu1) karmic; urgency=low * Merge from debian unstable, remaining changes (LP: #384131): - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. - debian/rules: + don't install the init script in runlevels 0 and 6. -- Nick Ellery Thu, 04 Jun 2009 16:38:43 -0700 resolvconf (1.44) unstable; urgency=low [ Thomas Hood ] * Add "hso*" pattern to interface-order file (Closes: #516357) * Don't include duplicate domain names (both with and without the root domain suffix) in search list. Thanks to Tom Carroll. (Closes: #522814) * Remove /lib/init/rw/resolvconf on purge (Closes: #531283) Thanks to Holger Levsen. [ Daniel Kahn Gillmor ] * debian/control: Update my e-mail address in Uploaders * Fix typo in initscript. Thanks, Peter Eisentraut (Closes: #525681) * Add status function to initscript for LSB compliance. Thanks, Peter Eisentraut (Closes: #525680) -- Daniel Kahn Gillmor Tue, 02 Jun 2009 18:02:23 -0400 resolvconf (1.43ubuntu1) jaunty; urgency=low * Merge from debian unstable, remaining changes (LP: #306092): - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. - debian/rules: + don't install the init script in runlevels 0 and 6. -- Nick Ellery Sun, 07 Dec 2008 15:12:34 -0800 resolvconf (1.43) unstable; urgency=low [ Thomas Hood ] * No longer #! bash in postrm and config since (as of policy 3.7.3.0) we are now entitled to assume that /bin/sh supports the "local" feature * initscript: Don't declare Should-Stop dependency on networking and ifupdown (because what is really required is a X-Stop-Before dependency) * In resolvconf(8), for explanation of dns-* options refer the reader to resolv.conf(5). (Closes: #507086) * [Debconf translation updates] * Swedish (Closes: #503353) -- Marco Nenciarini Sat, 06 Dec 2008 10:17:36 +0100 resolvconf (1.42ubuntu2) intrepid; urgency=low * bin/resolvconf: fail with non-zero exit code when /etc/resolv.conf is not a symlink. This allows network-manager to recognize such an error and fallback to default behaviour when resolvconf is installed, but is not used. -- Alexander Sack Wed, 10 Sep 2008 10:08:56 +0200 resolvconf (1.42ubuntu1) intrepid; urgency=low * Merge from debian unstable, remaining changes: + debian/postinst: - use default /var/run. + debian/rules: - don't install the init script in runlevels 0 and 6 + debian/control: - Update Standards-Version. -- Emanuele Gentili Wed, 20 Aug 2008 02:32:47 +0200 resolvconf (1.42) unstable; urgency=high [ Thomas Hood ] * init script: Add X-Start-Before and Should-Stop dependencies on ifupdown and networking (Closes: #493501, #494084, #494872) * [Debconf translation updates] * Japanese (Closes: #493608) * Swedish (Closes: #491780) -- Thomas Hood Sun, 03 Aug 2008 21:27:56 +0200 resolvconf (1.41ubuntu1) intrepid; urgency=low * Merge from Debian unstable. Remaining Ubuntu changes: (LP: #241328) + debian/postinst: use default /var/run. + Update maintainer field in debian/control. -- Emanuele Gentili Thu, 19 Jun 2008 16:26:51 +0200 resolvconf (1.41) unstable; urgency=low [ Thomas Hood ] * postinst: Do not remove existing runlevel configuration. (Releases 1.12 and up did so in order to correct the error made in earlier releases, of installing at S39 instead of S38. The correction will already have been performed on all systems upgraded to sarge.) (Closes: #477752) * No longer #! bash in postinst [ Daniel Kahn Gillmor] * don't try to manipulate forwarding dnscaches which are marked as "down" (Thanks, Soeren Sonnenburg!) (Closes: #479867) * since both runit and daemontools now use /etc/service, use availability of executables to select supervising service instead (Thanks, Alec Berryman!) (Closes: #485523) * Fixed my published e-mail address in the Uploaders: line. * debian/control: added Vcs-Svn, Vcs-Browser, and Homepage fields * debian/control: added Dm-Upload-Allowed: yes -- Daniel Kahn Gillmor Tue, 17 Jun 2008 16:51:15 -0400 resolvconf (1.40ubuntu1) intrepid; urgency=low * Merge from debian unstable, Ubuntu remaining changes (LP: #226679): + debian/postinst: use default /var/run. + Update maintainer field in debian/control. -- Emanuele Gentili Mon, 05 May 2008 00:23:04 +0200 resolvconf (1.40) unstable; urgency=low [ Daniel Kahn Gillmor ] * update.d/dnscache: moved runit service directory from /var/service to /etc/service, tracking #461478. Added Conflicts: runit (<< 1.8.0-3) to make sure the system uses the same path. * update.d/dnscache: changing directories back from $SERVICEDIR after scanning so that list-records works properly. [ Thomas Hood ] * Overwrite /etc/resolvconf/run symlink by means of "ln -nsf" rather than by means of "ln -sf" since the latter just (uselessly) puts a new symlink _in_ the run directory. Thanks to Karl Chen for pointing out the error. (Closes: #475528) * [Debconf translation updates] * Italian (Closes: #471889) * Spanish (Closes: #473470) -- Marco Nenciarini Thu, 24 Apr 2008 17:56:50 +0200 resolvconf (1.39) unstable; urgency=low [ Daniel Kahn Gillmor ] * Removed bashism from dnscache script (Closes: #459566) Thanks, Jeff King! [ Thomas Hood ] * Add a variable giving the admin the ability to disable the not-always- so-popular "truncate the nameserver list after 127.*" feature (Closes: #339418, #404041, #425444, #462946) * Change dhcp3 dhclient hook script so that it sends domain name and domain search strings separately to resolvconf preceded by the "domain" and "search" keywords, respectively. (Closes: #460609) * Add information about dns- options to resolvconf.8 (Closes: #305884) * Clean up dnscache script * Add pere to Uploaders list * Check before migrating files from /dev/shm/resolvconf/* (Closes: #463463) * Add debian/compat, make lintian happy * Debconf templates and debian/control reviewed by the debian-l10n-english team as part of the Smith review project. (Closes: #464499) * [Debconf translation updates] * Galician. Closes: #465305 * Indonesian. Closes: #465411 * Vietnamese. Closes: #465436 * German. Closes: #466099 * Czech. Closes: #466307 * Portuguese. Closes: #466464 * Finnish. Closes: #466607 * Russian. Closes: #467443 * French. Closes: #467530 * Dutch. Closes: #468249 -- Marco Nenciarini Thu, 13 Mar 2008 12:48:18 +0100 resolvconf (1.38ubuntu1) hardy; urgency=low * Merge from debian unstable, remaining changes (LP: #182433): - use /var/run instead of /dev/shm - debian/rules: don't install the init script in runlevels 0 and 6 -- Emanuele Gentili Sun, 13 Jan 2008 01:36:43 +0100 resolvconf (1.38) unstable; urgency=low [ Thomas Hood ] * Remove ru versions of man pages which failed lexgrog check * Add initscript lsb header (Closes: #451751) * Eliminate obsolete checks for old bad hook scripts (Addresses but does not close # 388956) * New nscd pidfile location is /var/run/nscd/nscd.pid (Closes: #415783) Thanks to Bob Knock. * Add gl.po, thanks to Jacobo Tarrio (Closes: #412511) * Add pt.po, thanks to Miguel Figueiredo (Closes: #413752) [ Daniel Kahn Gillmor ] * Use /lib/init/rw instead of /dev/shm (Closes: #431181) Thanks, Roger Leigh! -- Thomas Hood Tue, 31 Dec 2007 12:00:00 +0100 resolvconf (1.37ubuntu1) feisty; urgency=low * Merge from debian unstable, remaining changes: - use /var/run instead of /dev/shm - debian/rules: don't install the init script in runlevels 0 and 6 -- Michael Bienia Tue, 19 Dec 2006 14:19:02 +0100 resolvconf (1.37) unstable; urgency=high [ Thomas Hood ] * initscript: Don't do anything if resolvconf is removed (Closes: #393323) * Update ja.po thanks to Hideki Yamane (Closes: #391953) * Add es.po thanks to Javier Fernández-Sanguino Peña (Closes: #402678) [ Marco Nenciarini ] * Urgency set to high due to RC bug fix. -- Marco Nenciarini Wed, 13 Dec 2006 15:13:02 +0100 resolvconf (1.36ubuntu1) edgy; urgency=low [ William Alexander Grant ] * Readded patch to use /var/run rather than /dev/shm (it was lost in a sync a while back) (Closes Ubuntu: #61310). [ Daniel T. Chen ] * debian/rules: Follow multiuser semantics for dh_installinit(1) -- that is, we don't need to save anything for runlevels 0 or 6, so don't create those symlinks. -- Daniel T Chen Wed, 20 Sep 2006 03:12:20 -0400 resolvconf (1.36) unstable; urgency=low [ D.K. Gillmor / TH ] * Update dnscache update script to handle runit too. (Closes: #380119) [ Marco Nenciarini / TH ] * Modified postinst and prerm scripts to use invoke-rc.d if available * Bumped standards version to 3.7.2.1 -- Marco Nenciarini Wed, 9 Aug 2006 16:50:50 +0200 resolvconf (1.35) unstable; urgency=low [ Daniel Nylander / TH ] * Add sv.po [ Yuri Kozlov / TH ] * Add ru.po; add ru translations of manpages (Closes: #350383) [ Thomas Hood ] * DH_COMPAT=5 * Relicense with GPL version option * Remove /lib/init from initscript PATH since standard readlink program with -f option now works as required * Depend on coreutils >= 5.93 to get revised readlink program -- Thomas Hood Wed, 11 Jan 2006 23:53:47 +0100 resolvconf (1.34) unstable; urgency=low [ Thomas Hood ] * Tweak README * Update cs.po thanks to Miroslav Kure (Closes: #322430) * Update FSF address * Use latest lsb init-functions in initscript -- Marc Haber Sun, 18 Dec 2005 16:15:29 +0000 resolvconf (1.33) unstable; urgency=medium * debian/control: + Limit Conflict with totd to versions << 1.4-4 because totd now (as of 1.4-4) refrains from writing to /etc/resolv.conf and refrains from altering /etc/dhclient-enter-hooks if resolvconf is installed (Closes: #320536) + Enhances totd (>= 1.4-4) which includes a resolvconf update script * Update README info re: totd * Update debconf message to say that original resolv.conf file will be restored on _removal_ (rather than on purge, as in versions prior to 1.30). Update de, fr, nl pt_BR; update vi thanks to Clytie Siddall. (cs and ja still need updating.) -- Thomas Hood Sat, 31 Jul 2005 16:00:00 +0200 resolvconf (1.32) unstable; urgency=low * /etc/resolvconf/update.d/libc: + Truncate nameserver list after 127.* and limit to three items This reduces the number of client notifications when a local caching nameserver is running * Report missing /etc/resolv.conf symlink with a warning rather than with an error message * README: Document the REPORT_ABSENT_SYMLINK environment variable -- Thomas Hood Thu, 21 Jul 2005 09:37:01 +0200 resolvconf (1.31) unstable; urgency=medium * Re-add 'lo' to interface-order because #252232 is still not fixed. (Closes: #319067) * Enable updates on restart as well as start * Fix typo in vi.po * initscript: Use lsb init-functions if present * Add update script for djbdns dnscache (Closes: #318464, #294208) Thanks to Daniel Kahn Gillmor and martin krafft. -- Thomas Hood Thu, 20 Jul 2005 11:00:00 +0200 resolvconf (1.30) unstable; urgency=low * On removal, replace the symlink at /etc/resolv.conf with a file (Closes: #318073) * Improve error message re: invalid option * Bump Standards-Version to 3.6.2.1; no changes required * Add vi.po. Thanks to Clytie Siddall. (Closes: #317771) -- Thomas Hood Wed, 15 Jun 2005 11:18:18 +0200 resolvconf (1.29) unstable; urgency=low * /lib/resolvconf/list-records: Enable extglob and clean up a tad * Add ja.po (Closes: #310211) Thanks to Hideki Yamane * Fix typos in de.po (Closes: #313818) Thanks to Jens Seidel * Eliminate preinst. We now support upgrades only from the sarge (1.28) or later versions. * Reject initial hyphen in record name (Closes: #309153) * /etc/resolvconf/interface-order: + Don't match lo.pdns and lo.pdns-recursor prior to the catch-all line (See #308677 for background.) -- Thomas Hood Mon, 14 Jun 2005 20:00:00 +0200 resolvconf (1.28) unstable; urgency=low * /etc/resolvconf/update.d/bind: + Eliminate stray colon from otherwise empty forwarders list (Closes: #304994) * /sbin/resolvconf: Add -u option * /etc/init.d/resolvconf: Don't report creation of /dev/shm/resolvconf * README: Mention pdns-server and pdns-recursor * debian/control: Enhances: pdns-recursor (>= 2.9.17-11) since the latter lets resolvconf know that it is available * In various scripts, invoke run-parts with exec if it is the script's last action -- Thomas Hood Sun, 17 Apr 2005 02:30:56 +0200 resolvconf (1.27) unstable; urgency=low * Don't Conflict with udhcpc versions 0.9.8cvs20050124-3 or later, since resolvconf support has been added * Disjoin Dependency on initscripts with one on coreutils (>= 5.3.0) since the latter will include a readlink program that implements the -f option in the way that we require * README: + Talk about using resolvconf with ifrename et al. + Update information about udhcpc which is now compatible with us. Thanks to Eric Van Buggenhaut for taking care of this. -- Thomas Hood Fri, 1 Apr 2005 16:16:21 +0200 resolvconf (1.26) unstable; urgency=medium * README: Update status of bug reports * Begin description synopsis with lower case letter * Add Czech translation of debconf templates. Thanks to Miroslav Kure (Closes: #292466) -- Thomas Hood Sat, 29 Jan 2005 23:26:30 +0100 resolvconf (1.25) unstable; urgency=low * config, postinst, postrm: + Use bash because confmodule uses "local" which is non-POSIX (See #252094) * Conflict with webmin-wvdial << 1.160-3. Version 1.160-3 no longer trashes /etc/resolv.conf if the latter is a symlink (see #288481). * Remove Suggestions (Closes: #277617) * README: Update information about webmin-wvdial -- Thomas Hood Fri, 21 Jan 2005 17:46:14 +0100 resolvconf (1.23) unstable; urgency=low * resolvconf.8: Explain difference between /etc/resolvconf/update.d/ and /etc/resolvconf/update-libc.d/. (Closes: #281797) * debian/control: Conflict with webmin << 1.150-2 and webmin-wvdial * README: Update and add information about webmin-wvdial -- Thomas Hood Sun, 21 Nov 2004 14:35:59 +0100 resolvconf (1.22) unstable; urgency=low * Treat the domain option just like the search option (Closes: #276960) * Tweak README (Closes: #277158) -- Thomas Hood Tue, 19 Oct 2004 08:14:56 +0200 resolvconf (1.21) unstable; urgency=medium * postinst: Clean up -- Thomas Hood Thu, 9 Sep 2004 09:06:51 +0200 resolvconf (1.20) unstable; urgency=medium * postinst: + configure: Don't put /etc/resolvconf/run/ at /dev/shm/resolvconf/ if /dev/ is devfs (Closes: #270673) * postrm: + remove: Don't fail on if /etc/resolvconf/run/ not accessible. (Closes: #270694) -- Thomas Hood Wed, 8 Sep 2004 20:44:25 +0200 resolvconf (1.19) unstable; urgency=high * debian/control: + Downgrade Recommendations to Suggestions so that installing resolvconf doesn't pull in packages such as bind9 if the user has configured her package manager to install all Recommended packages. Thanks to LaMont Jones for pointing out this problem. (Closes: #266027) -- Thomas Hood Mon, 16 Aug 2004 22:37:24 +0200 resolvconf (1.18) unstable; urgency=high * README update * /etc/resolvconf/update.d/libc: + Redirect stderr of sed pipe to /dev/null (Closes: #258495) Otherwise the script fails when run by pump -- Thomas Hood Tue, 29 Jun 2004 13:38:54 +0200 resolvconf (1.17) unstable; urgency=medium * /etc/resolvconf/interface-order + Match "lo" early for compatibility with existing bind9 (and bind) packages which register their nameserver information under "lo". This is necessary because #252232 hasn't been implemented yet. (Closes: #256799) * debian/control: + Also Enhances: nscd + Recommend dnsmasq version 2.9-2 which supports the new method of specifying the interface priority order * debian/config: + Don't ask link-tail-to-original question if /e/n/i already contains dns-nameservers entries. This begins to addresses #256316. * README: + Update various bug stati -- Thomas Hood Wed, 16 Jun 2004 09:29:37 +0200 resolvconf (1.15) unstable; urgency=low * /sbin/resolvconf: + Tweak -d case * /lib/resolvconf/list-records + Only return names of nonempty files * /etc/resolvconf/update.d/bind: + Try to reload both bind9 and bind * /etc/resolvconf/update.d/libc: + Support nscd. If nscd is installed and running and /etc/resolv.conf has changed then restart nscd and run update-libc.d/ scripts with an '--nscd' option which will allow some of them (e.g., fetchmail) to decide not to do anything. (Closes: #48976, #60771, #69256, #252251, #252283) * /etc/resolvconf/interface-order + Order lo for the different nameservers in case more than one of them is running * README: + Add note about -n * debian/control: + Remove unused '${shlibs:Depends}' from Depends: line * debian/po/de.po + Added. Thanks to Helge Kreutzmann! (Closes: #253587) -- Thomas Hood Fri, 4 Jun 2004 09:33:39 +0200 resolvconf (1.14) unstable; urgency=low * Check everything for POSIXal correctness + Where possible eliminate non-POSIX code such as the use of test's -a and -o options + Otherwise name bash on the shebang line and say why bash is required * /sbin/resolvconf + Don't run update scripts if record was not changed (Closes: #251255) + Remove -n option * /lib/resolvconf/list-records: + New script. Prints out the names of interface records in the pwd. Uses patterns from /etc/resolvconf/interface-order, if available, to determine the order in which interface record names are printed. Thanks to Christian Weeks for the suggestion. (Closes: #250967) * /etc/resolvconf/update.d/libc: * /etc/resolvconf/update.d/bind: + Use /lib/resolvconf/list-records + Clean up a bit while I'm at it * /etc/resolvconf/interface-order: + New conffile + Add 'tun*' and 'tap*' before 'eth*' since people who use VPNs probably want to use the private nameservers * README: + Mention that pdnsd >= 1.1.10par-4 has working resolvconf support + Mention in the TODO section: - nameservers: djbdns dnscache, maradns, nscd - resolver libraries: adns, ares, djbdns, FireDNS, Net::DNS + Resolvconf record name for bind should be named 'lo.named'. * interface-order.5: + New manpage. My thanks to Dan Jacobson for his help. * resolvconf.8: + Tweak + Mention nonstandard resolver libraries + Mention interface-order(5) * debian/control: + Recommend pdnsd >= 1.1.10par-4 which now supports resolvconf + Update other Recommendations + Conflict with pdnsd << 1.1.10par-4 + Improve description * debian/config, debian/postinst + Don't regard as "rogue" any hook scripts such as the one in pppoeconf 1.0.2 which consists exclusively of "#!/bin/sh" (Closes: #252088) -- Thomas Hood Tue, 3 Jun 2004 17:00:00 +0200 resolvconf (1.13) unstable; urgency=low * Instead of /etc/resolvconf/run/disable-updates flag file use /etc/resolvconf/run/enable-updates and change the sense of tests. That way, if the run dir is on a tmpfs then updates are disabled from boot time until the initscript enables them. (This feature is intended for resolvconf's internal use only.) * Eliminate use of test's -a option from maintainer scripts * debian/postinst: enable updates * debian/prerm: disable updates * debian/control: + Recommend dhcp-client (>= 2.0pl5-17) which now supports resolvconf Thanks to Eloy A. Paris for applying the patch in #248399. * /etc/init.d/resolvconf + Add enable-updates and disable-updates methods (This feature is intended for resolvconf's internal use only.) * /sbin/resolvconf: + Add -n option + Disallow spaces, slashes and initial dots and tildes in interface names * resolvconf(8): + Tweak + Warn about changing symlink /etc/resolv.conf + Document -n * Eliminate examples/downup.sh * README: + Describe head, base and tail files + Mention that 0000usepeerdns scripts are harmless + Mention that dhcp-client >= 2.0pl5-17 has resolvconf support * debian/config + Set priority of resolvconf/linkify-resolvconf to low + Only ask resolvconf/link-tail-to-original if tail file does not exist * templates: + pt_BR.po update thanks to Gleydson Mazioli da Silva * /etc/resolvconf/resolv.conf.d/head + Make warning sterner (Closes: #248964) * /etc/dhcp3/dhclient-enter-hooks.d/resolvconf: + Handle STOP (Closes: #246558) + On TIMEOUT don't always run resolvconf -d -- Thomas Hood Sun, 18 May 2004 10:00:00 +0200 resolvconf (1.12) unstable; urgency=low * Move rcS sequence number from S39 to S38 so that resolvconf is initialized _before_ ifupdown is initialized (and thus before ifupdown can be used and thus before ifupdown can call resolvconf). [See entry for release 1.41] -- Thomas Hood Sat, 24 Apr 2004 16:55:39 +0200 resolvconf (1.11) unstable; urgency=low * README: Improve bits about pppconfig and pppoeconf -- Thomas Hood Mon, 19 Apr 2004 15:13:46 +0200 resolvconf (1.10) unstable; urgency=low * postrm: Don't rm conffile resolv.conf.d/head on purge * postinst: Tighten up test for presence of tmpfs at /dev/shm/ -- Thomas Hood Sun, 18 Apr 2004 21:39:27 +0200 resolvconf (1.9) unstable; urgency=low * fr.po update (Closes: #244075) * Update pppconfig dependencies -- Thomas Hood Thu, 15 Apr 2004 14:16:52 +0200 resolvconf (1.8) unstable; urgency=low * Eliminate update-resolv and its man page since pppconfig will detect /sbin/resolvconf in the future * README + Update information about pppconfig * /etc/network/if-down.d/resolvconf: + No longer delete static|manual records with old-style names * /etc/init.d/resolvconf: + Clean up + Improve start method's creation of the run dir. This requires use of the /lib/init/readlink program that ships in initscripts 2.85-15. * debian/postinst: + Simplify hook script disabling code. This eliminates the lintian warning about using debconf in postinst + Remove old code that moved run directory out of /var/run, which is what experimental versions of this package used for a while + Replace this with new code that makes resolvconf use /dev/shm if possible and /etc/resolvconf/run/ otherwise. (Closes: #213594) * debian/config: + Simplify hook script disabling code * debian/control: + Depend on initscripts >= 2.85-15 + Suggest pppconfig >> 2.3 + Conflict with pppconfig <= 2.3 since version 2.3 hook scripts futz with /etc/resolv.conf again * templates and their translations + Update to reflect the fact that not only versions prior to 2.2.0 but also version 2.3 of pppconfig contains a rogue ppp hook script. While making changes to the French and Dutch translations I fixed several errors. I don't speak Portuguese so that translation now contains fuzzies. -- Thomas Hood Sat, 27 Mar 2004 13:23:01 +0100 resolvconf (1.7) unstable; urgency=low * Remove characters from changelog of which lintian disapproves * Conflict with ifupdown << 0.6.4-4.1 because earlier versions didn't pass environment variables to "up" and "down" scripts. (Closes: #236999) Thanks to Marius Gedminas for finding the bug. * Minor changes to initscript, /sbin/resolvconf, resolv.conf.d/head * Update README + Mention that pppd's usepeerdns option should be used. Thanks to jgmbenoit@wanadoo.fr for the suggestion. (Closes: #237570) * /etc/resolvconf/update.d/libc + Don't put an argumentless search option in /etc/resolv.conf . Thanks to Wouter van Heyst for the fix. -- Thomas Hood Sun, 21 Mar 2004 11:41:16 +0100 resolvconf (1.6) unstable; urgency=low * /etc/init.d/resolvconf * The start method now creates /etc/resolvconf/run/ and /etc/resolvconf/run/interface/ if they do not exist. It also works if /etc/resolvconf/run/ is a symlink. These changes allow resolvconf to work properly if /etc/resolvconf/run is a symlink to /dev/shm/resolvconf/, for example. * debian/control: * Conflict with whereami << 0.3.3 since version 0.3.3 is less incompatible with resolvconf than earlier versions were * README * Update info about whereami -- Thomas Hood Sat, 17 Jan 2004 13:34:05 +0100 resolvconf (1.5) unstable; urgency=low * /etc/resolvconf/update.d/libc * Rewrite so that it eliminates all duplicate nameserver addresses and search domains. (Closes: #215232) Thanks to Marcus C. Gottwald for his help. * /sbin/resolvconf * Eliminate comments from records before storing. Safety measure. * /etc/network/if-*.d/*resolvconf * Allow dns-* options in all methods of inet and inet6 interfaces * README: Minor updates * resolvconf(8): Updates * pt_BR.po: Update thanks to Andre Luis Lopes * fr.po, nl.po: Minor wording fixes -- Thomas Hood Sat, 14 Jan 2004 19:00:00 +0100 resolvconf (1.4) unstable; urgency=medium * /etc/network/if-down.d/resolvconf: * Delete lo.inet record too (Closes: #226687) * Delete $IFACE record for dhcp method too. This works around bug #196865. (Closes: #226675) * debian/control: * Update Description * Update Recommended dnsmasq version -- Thomas Hood Tue, 10 Jan 2004 13:00:00 +0100 resolvconf (1.3) unstable; urgency=medium * all shell scripts: * Add lots of double quotation marks around variables for consistency's sake. No functional changes (I hope!) * debian/control: * Adjust package relationship versions: Recommend or Suggest those versions of packages that have the best resolvconf support; Conflict with those versions of packages that don't work cleanly with resolvconf. Note that bind9 is now to be preferred over bind because resolvconf support has been added to bind9's initscript. Thanks to LaMont Jones for fulfilling this wish (#199255)! * Update Description and remove double spaces * debian/postinst: * Remove downup code (Closes: #221954, #220159) * debian/rules * ... and put it in /usr/share/doc/resolvconf/examples/downup.sh * debian/templates: * Change prompts (English, French) re: downupping interfaces * /etc/resolvconf/update.d/libc * Add semicolon. Thanks to Mike. This should allow the script to work with the woody version of sed. (Closes other part of #221954) * Redirect stderr of sed pipe to /dev/null (Closes: #222727) Otherwise the script fails when run by pump * Some minor bugfixes thanks to Marcus C. Gottwald * /etc/network/if-up.d/000resolvconf, /etc/network/if-down.d/resolvconf * Include address family name in the nameserver data set identifier (Closes: #223745) * README * Update info, especially re: bind9 * debian/po/nl.po * Added, thanks to Tim Dijkstra (Closes: #224041) * I tweaked it to bring it up to date * /etc/network/if-up.d/000resolvconf * Clean up * Allow dns-* options in loopback lifaces too -- Thomas Hood Fri, 3 Jan 2004 13:00:00 +0100 resolvconf (1.2) unstable; urgency=medium * debian/po/fr.po * Added, thanks to Frederic ZULIAN (Closes: #219403, #217680) * debian/preinst * Create /etc/resolvconf/resolv.conf.d if necessary before moving resolv.conf backup file -- Thomas Hood Thu, 9 Nov 2003 10:00:00 +0100 resolvconf (1.1) unstable; urgency=low * debian/control: * Build-Depends on debhelper instead of Build-Depends-Indep. This is necessary because the clean rule uses debhelper commands. See policy 7.6 and #178809 and #191411. Ignore the lintian warning -- it is erroneous. * Suggest pcmcia-cs >= 3.2.5-1 * Conflict with pcmcia-cs << 3.2.5-1 * debian/rules * Install ifup hook script as "000resolvconf" (Closes: #217389) * debian/config * Re-ask questions on reconfigure * debian/templates: * Corrections and clarifications. My since apologies to translators for once again moving the target. * debian/po/pt_BR.po * Added, thanks to Andre Luis Lopes (Closes: #216601) * debian/preinst * Rename already installed ifup hook script to "000resolvconf" * Delete /var/lib/resolvconf more carefully * debian/postinst * Generate up and down scripts with a sed script from Michael Weber. One advantage is that the interfaces are downed in the order that is the reverse of the order in which they were upped. * Delete /etc/resolvconf/run more carefully * Re-do configuration on every configure or reconfigure * Do debconf notification at high priority * /etc/network/if-up.d/000resolvconf * Work also with inet6 and manual ifaces * README * Update info re: pcmcia-cs * Fix some typos * /etc/resolvconf/update.d/libc * Sort and uniq lines in the resolver configuration file (Partially addresses #215232) * Merge search lines (Closes: #212670) The comment header of the dynamically generated resolv.conf file is now located in /etc/resolvconf/resolv.conf.d/head. /etc/resolvconf/resolv.conf.d/base is to be used for base (static) entries that may be sorted and merged with other entries. /etc/resolvconf/resolv.conf.d/tail may be a symlink to ./original on initial installation but the admin can point this somewhere else or replace it with a real file as he or she wishes. To "disable" it, point it at /dev/null. Many improvements in this release arose from comments by Michael Weber. -- Thomas Hood Wed, 1 Nov 2003 18:23:00 +0100 resolvconf (1.0) unstable; urgency=medium * 1.0 Release * debian/rules: * Variable name change * debian/templates: * Wording improvements thanks to suggestions from Joey Hess (Closes: #215035) -- Thomas Hood Wed, 8 Oct 2003 20:02:44 +0200 resolvconf (0.47) unstable; urgency=medium Translators can now go ahead and translate the debconf messages. I will minimize unnecessary changes. * debian/init * Make restart do reload instead of stop;start * debian/templates * Remove redundant questions from each description * Clarify what "disabling rogue hook scripts" is (Closes: #214146) * debian/postinst * Disable rogue hook scripts by removing execute permission. Do not rename them. * Also check for rogue pppconfig hook script * README * Merge ANNOUNCE * Add table of contents * Re-order sections * Improve explanation of how to edit /etc/network/interfaces ... per suggestions by Osamu Aoki and Manoj Srivastava. * debian/postinst * Use "ln -nsf" instead of "ln -sf" for safety -- Thomas Hood Fri, 3 Oct 2003 21:52:34 +0200 resolvconf (0.46) unstable; urgency=medium * /etc/resolvconf/update.d/bind: * Remove semicolon from end of existing forwarders statement in named.conf.options (Closes: #213698) Thanks to Manoj Srivastava for reporting this. * Use temporary file name with $$ and clean up on signal to exit * /etc/resolvconf/update.d/libc: * Print message on stderr if /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf . This can be shut off by changing the value of an environment variable. * debian/control: * Conflict with xisp which also futzes with /etc/resolv.conf * Conflict with totd which does unpleasant things to /etc/resolv.conf and dhclient-enter-hooks * Add warning to the Description that the admin may have to do some manual configuration * debian/rules: * initscript stop at K89 -- this may fix #212780 * remove binary-arch rule * debian/init: * Set disable-updates flag on stop * Don't update if flag is set * sbin/resolvconf: * Don't update if disable-updates flag is set * Update using exactly the same update() as in initscript * README: * Add very short "Usage" section * Explain how to make pcmcia-cs use resolvconf instead of altering /etc/resolv.conf directly. Thanks to Manoj Srivastava for this. * Re-order instructions. Thanks to Osamu Aoki for good suggestions. * Miscellaneous minor updates * debian/config, debian/templates: * Post a debconf note if any of the following rogue hook scripts is still present, nonempty and executable: /etc/ppp/ip-up.d/000usepeerdns /etc/ppp/ip-up.d/0xisp-dns /etc/ppp/ip-down.d/0xisp-dns Ask for permission to disable scripts like these * Rewrite templates to increase clarity * debian/postinst: * Downup interfaces and restart DNS caches on reconfigure too * Disable (or remind the user to disable) rogue hook scripts * Copy original /etc/resolv.conf to /etc/resolvconf/run/resolv.conf so that there is some resolv.conf file at the target of the link if there is some failure in the postinst (Closes: #212668) * debian/changelog: * Truncate -- include only the entries for non-experimental releases -- Thomas Hood Fri, 26 Sep 2003 11:27:45 +0200 resolvconf (0.45) unstable; urgency=high * README * Update * debian/init: * Arguments are passed through run-parts using --arg=. (Closes: #212801) Thanks to Martin Dickopp for reporting this. * debian/templates: * Tweak * debian/control: * Change ppp recommendation to >= 2.4.1.uus2-4 * Conflict with pppoeconf << 1.0 since earlier versions still contain a /etc/ppp/ip-up.d/000usepeerdns script that overwrites /etc/resolv.conf unless the pppconfig package also happens to be installed. * debian/config, debian/templates * Post a debconf note if /etc/ppp/ip-up.d/000usepeerdns is still present, nonempty and executable * debian/postinst * Remind user to delete or modify 000usepeerdns -- Thomas Hood Thu, 25 Sep 2003 20:50:33 +0200 resolvconf (0.44) unstable; urgency=low * debian/rules: * Install ppp hook scripts as /etc/ppp/ip-up.d/000resolvconf /etc/ppp/ip-down.d/000resolvconf (Closes: #212548) * debian/preinst: * On upgrade rename /etc/ppp/ip-up.d/resolvconf /etc/ppp/ip-down.d/resolvconf to /etc/ppp/ip-up.d/000resolvconf /etc/ppp/ip-down.d/000resolvconf respectively. * debian/templates: * Tweak -- Thomas Hood Wed, 24 Sep 2003 10:23:56 +0200 resolvconf (0.43) unstable; urgency=low * initscript: * Rework so that it calls update functions on start with "-i" option * /etc/resolvconf/update.d/libc: * Prepend /etc/resolvconf/resolv.conf.d/head and append /etc/resolvconf/resolv.conf.d/tail if they are present. This makes it easy for the user to prepend or append, respectively, an arbitrary file to the dynamically generated resolv.conf file. The immediate use for this feature is to allow the user to symlink /etc/resolvconf/resolv.conf.d/tail to ./original. * Don't reload things if given the "-i" option * /etc/resolvconf/update.d/bind: * Don't reload things if given the "-i" option * resolv.conf backup file: * It is now stored at /etc/resolvconf/resolv.conf.d/original . This makes possible "ln -s original /etc/resolvconf/resolv.conf.d/tail" as discussed above. * debian/preinst * Move the old backup file to the new location * Delete /var/lib/resolvconf which is no longer used * debian/config, debian/templates, debian/postinst: * Add installation option to symlink /e/r/r/tail to /e/r/r/original * debian/postrm * Remove /etc/resolvconf/run symlink or directory on purge * man/resolvconf.8 * Update thanks to suggestions by Eduard Bloch -- Thomas Hood Thu, 21 Sep 2003 15:12:31 +0200 resolvconf (0.42) unstable; urgency=low * Eliminate /var/run/resolvconf * debian/config, debian/templates: * Change configuration process so that there is only one question. The question asks whether the package should linkify /etc/resolv.conf _and_ downup all interfaces _and_ restart all DNS caches. The alternative is to do none of these things. The debconf description now provides a lot more information about the alternatives. The priority of the question is now high. (Closes: #210283) * etc/resolvconf/update.d/libc: * Use temporary file name with $$ and clean up on signal to exit -- Thomas Hood Fri, 12 Sep 2003 19:34:53 +0200 resolvconf (0.41) unstable; urgency=low * /sbin/resolvconf, /etc/resolvconf/update.d/bind, /etc/resolvconf/update.d/libc, man/resolvconf.8: * Cleanups thanks to code auditing by Michael Weber * man/resolvconf.8: * Don't say that /etc/resolvconf/run is usually a symlink * /etc/resolv.conf/update.d/bind * Ignore chown errors because bind (version 8) does not create a "bind" group (Closes: #209284). Thanks to Dylan Thurston for reporting this bug. -- Thomas Hood Tue, 9 Sep 2003 16:48:41 +0200 resolvconf (0.40) unstable; urgency=low * First upload to unstable * README * Fix typo -- Thomas Hood Sun, 7 Sep 2003 16:47:47 +0200 resolvconf (0.39) experimental; urgency=high * debian/control: * Version the dependency on ppp * Shorten the long Description * debian/prerm * Add quotation marks around: "$(readlink ...)" to fix test if /etc/resolv.conf does not exist. * debian/postinst * Create /etc/resolvconf/run as a directory instead of as a symlink to /var/run/resolvconf/ . If /etc/resolvconf/run is a symlink to the latter directory then convert it into a directory. * Move confmodule to beginning of file because it reruns the script * Don't downup lo * Give dh_installinit the "--no-start" option since the meaning of the initscript "start" method has changed. * /etc/init.d/resolvconf * Start method now cleans /etc/resolvconf/run/ since it isn't in /var/run/ by any more. This means that the start method should never be called when resolvconf is in use. Use it only on boot. * README * Tweak * Change to reflect the fact that the run directory is now /etc/resolvconf/run/ . -- Thomas Hood Mon, 1 Sep 2003 11:16:34 +0200 resolvconf (0.38) experimental; urgency=low * Initial Debian release. Closes: #204677 -- Thomas Hood Wed, 27 Aug 2003 17:53:54 -0100 resolvconf-1.69ubuntu1/debian/gbp.conf0000644000000000000000000000023112062416774014711 0ustar [DEFAULT] cleaner = /bin/true pristine-tar = False sign-tags = True [git-buildpackage] export-dir = ../build-area/ [git-dch] meta = True id-length = 7 resolvconf-1.69ubuntu1/debian/resolvconf.lintian-overrides0000644000000000000000000000072012062416774021035 0ustar # We really only want the stop method to run in runlevels 0 and 6 resolvconf binary: init.d-script-possible-missing-stop # The use of debconf has been carefully considered resolvconf binary: possible-debconf-note-abuse # The link-tail-to-original description is only 21 lines resolvconf binary: too-long-extended-description-in-templates resolvconf/link-tail-to-original # Breaks is sufficient for these packages resolvconf: breaks-without-version dnscache-run resolvconf-1.69ubuntu1/debian/templates0000644000000000000000000001111712062416774015220 0ustar # These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # debian-l10n-english@lists.debian.org for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: resolvconf/linkify-resolvconf Type: boolean Default: true _Description: Prepare /etc/resolv.conf for dynamic updates? The resolvconf package contains the infrastructure required for dynamic updating of the resolver configuration file. Part of the necessary infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/resolv.conf. If you choose this option then this link will be created; the existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv.conf.d/original, and will be restored if this package is removed. . Declining this option will prevent future installations from recreating the symbolic link and therefore the resolver configuration file will not be dynamically updated. Dynamic updating can then be activated following instructions in the README file. . The presence of resolvconf can affect the behavior of other programs, so it should not be left installed if unconfigured. Template: resolvconf/downup-interfaces Type: note _Description: Reboot recommended Suppliers of name server information such as local caching name servers and interface configurers are expected to supply name server information to the resolvconf program. However, although installation of the resolvconf package triggers them to supply their information, some of them fail to do so. . This bug would lead to loss of valid name server information on installation of the resolvconf package if the following workaround were not adopted: resolvconf includes the full contents of the pre-installation /etc/resolv.conf in its database until reboot. This has the drawback that name server information is retained even if the associated interface is later deconfigured. (This incorrect behavior is judged to be less harmful than the alternative of losing valid information.) . Until the bug in question is fixed and the workaround removed, the only way to ensure that resolvconf has fully correct name server information after the resolvconf package has been installed on a running system is to reboot the system. Template: resolvconf/reboot-recommended-after-removal Type: note _Description: Reboot recommended The removal of the resolvconf package may have resulted in some information about name servers becoming unavailable. To correct this problem it is recommended that the system be rebooted. Template: resolvconf/link-tail-to-original Type: boolean Default: true _Description: Append original file to dynamic file? If the original static resolver configuration file (/etc/resolv.conf) contains name server addresses, those addresses should be listed on "dns-nameservers" lines in /etc/network/interfaces. For more information, please consult the resolvconf(8) man page and the README file. . Until /etc/network/interfaces has been edited and the affected interfaces brought down and up again, the name server addresses will not be included in the dynamically generated resolver configuration file. . If you choose this option, a temporary workaround will be put in place: a symbolic link will be created (if it does not already exist) from /etc/resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. This will cause the whole of that original resolver configuration file to be appended to the dynamically generated file. . After the required "dns-nameservers" lines have been added to /etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced by one to /dev/null. Template: resolvconf/fixing-immutable Type: error _Description: Removing immutable filesystem bit from /etc/resolv.conf The file /etc/resolv.conf was marked immutable on the filesystem with the 'chattr' command. You may have done this to avoid the file being managed by NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed by resolvconf in order to correctly support dynamic sources of DNS information. . The immutable flag on /etc/resolv.conf will be removed now, and the current file will be moved to /etc/resolvconf/resolv.conf.d/original. If the original file contained static resolver configuration, it is recommended that you copy the file to /etc/resolvconf/resolv.conf.d/head. . After upgrade you may remove the /etc/resolv.conf symlink and restore the original contents of this file, but this is not recommended. resolvconf-1.69ubuntu1/debian/resolvconf-update-bind0000755000000000000000000000723012062416774017600 0ustar #!/bin/bash # Need bash because we use ${foo//bar/baz} # # Example script illustrating updating a named options file # # This example was prepared for Bind version 8. For Bind 9 # the script should be modified so that it generates only the # forwarders{} substatement, not the whole options{} statement. # # Resolvconf may run this script even if named is not running. # If a bind package is installed then we go ahead and update # the named configuration in case named is started later. # # Assumption: On entry, PWD contains the resolv.conf-type files. # # Written by Thomas Hood # Licensed under the GNU GPL. See /usr/share/doc/resolvconf/copyright. set -e PATH=/sbin:/bin [ -x /usr/sbin/named ] || exit 0 [ -x /lib/resolvconf/list-records ] || exit 1 [ -f /etc/bind/named.conf.options ] || exit 0 # Defaults NAMED_RUN_DIR=/var/run/bind # Defaults overrides [ -r /etc/default/resolvconf ] && . /etc/default/resolvconf [ "$NAMED_RUN_DIR" ] || exit 0 [ -d "$NAMED_RUN_DIR" ] || mkdir --parents --mode=0755 "$NAMED_RUN_DIR" DYNAMIC_OPTS_FILE=named.options # Stores arguments (minus duplicates) in RSLT, separated by spaces # Doesn't work properly if an argument itself contains whitespace uniquify() { RSLT="" while [ "$1" ] ; do for E in $RSLT ; do [ "$1" = "$E" ] && { shift ; continue 2 ; } done RSLT="${RSLT:+$RSLT }$1" shift done } # Get list of records, excluding all those for the loopback interface RSLVCNFFILES="$(/lib/resolvconf/list-records | sed -e '/^lo$/d' -e '/^lo[.]/d')" ### Compile semicolon-separated list nameservers ### NMSRVRS="" if [ "$RSLVCNFFILES" ] ; then uniquify $(sed -n -e 's/^[[:space:]]*nameserver[[:space:]]\+//p' $RSLVCNFFILES) [ "$RSLT" ] && NMSRVRS="${RSLT// /; }; " fi # N.B.: After changing directory we no longer have access to the resolv.conf-type files cd "$NAMED_RUN_DIR" TMP_FILE="${DYNAMIC_OPTS_FILE}_new.$$" clean_up() { rm -f "${NAMED_RUN_DIR}/$TMP_FILE" ; } trap clean_up EXIT rm -f "$TMP_FILE" # We want to process named.conf.options such that the new forwarders # statement gets inserted but nothing else is corrupted in the process. # We want to do this using only commands available in /bin and /sbin, i.e., # with sh, sed and/or grep. Sed can be made to work -- with difficulty. # Even so, the following script does not work properly if comment # delimiters of one style of commenting appear inside another kind of # comment. (Named supports C, C++ and sh comment styles.) # # First, we do our best to delete all and only comments. # Then we delete any existing forwarders statement, taking into account # the fact that these can span several lines. Then we add a new # forwarders statement at the beginning of the options statement. # echo "// named.conf fragment automatically generated by $0" > "$TMP_FILE" echo "// DO NOT EDIT THIS FILE. Instead edit /etc/bind/named.conf.options ." >> "$TMP_FILE" cat /etc/bind/named.conf.options \ | sed -e 's%\*/%\*/\ %g' \ | sed -e '\%/\*%{ :x ; s%\*/%\*/% ; t y ; N ; b x ; :y ; s%/\*.*\*/%% ; }' \ | sed -e 's%//.*%%' -e 's%#.*%%' \ | sed -e '/forwarders/{ :x ; s/}/}/ ; t y ; N ; b x ; :y ; s/}[[:space:]]*;/};/ ; t z ; N ; b y ; :z s/forwarders[[:space:]]*{[^}]*};// ; }' \ | sed -e 's/options[[:space:]]*{/options {\ forwarders { '"${NMSRVRS}"'};/' | sed -e '/^[[:space:]]*$/{ d ; }' \ >> "$TMP_FILE" chown root:bind "$TMP_FILE" # Reload named unless we know its options haven't changed if [ -x /usr/bin/diff ] && [ -f "$DYNAMIC_OPTS_FILE" ] && /usr/bin/diff -q "$DYNAMIC_OPTS_FILE" "$TMP_FILE" > /dev/null ; then # No change rm -f "$TMP_FILE" else mv -f "$TMP_FILE" "$DYNAMIC_OPTS_FILE" [ -x /etc/init.d/bind9 ] && /etc/init.d/bind9 reload > /dev/null 2>&1 || : fi resolvconf-1.69ubuntu1/debian/postinst0000755000000000000000000001060312076276534015112 0ustar #!/bin/sh # # This file is part of the resolvconf package. # set -e . /usr/share/debconf/confmodule MYNAME=resolvconf.postinst report() { echo "${MYNAME}: $*" ; } report_err() { report "Error: $*" >&2 ; } report_warn() { report "Warning: $*" >&2 ; } report_info() { report "$*" >&2 ; } OLD_RUN_DIR=/var/run is_immutable_file() { [ "$1" ] || return 2 [ -e "$1" ] || return 1 [ ! -L "$1" ] || return 1 local ATTR="$(lsattr "$1" 2>/dev/null || :)" [ "$ATTR" ] || return 1 echo "$ATTR" | awk '$1 ~ /i/ { exit 0; }; { exit 1; }' } ### Deal with obsolete configuration files ### rm -f /etc/dhcp3/dhclient-enter-hooks.d/resolvconf [ -f /etc/resolvconf/update.d/bind ] && mv -f /etc/resolvconf/update.d/bind /etc/resolvconf/update.d/bind.dpkg-old ### Create run-time directories and linkify ### # # We create the run-time directories here, in the postinst, even though # we also do so in the preinst, because # * the system may have rebooted since the preinst ran, causing # everything on tmpfses to disappear; # * multistrap doesn't run the preinst at all. # case "$1" in configure) # Linkify /etc/resolv.conf if appropriate db_get resolvconf/linkify-resolvconf if [ "$RET" = "true" ] ; then if is_immutable_file /etc/resolv.conf ; then db_input critical resolvconf/fixing-immutable db_go || : chattr -i /etc/resolv.conf fi if [ -f /etc/resolv.conf ] \ && [ ! -L /etc/resolv.conf ] then # Back up original file if [ ! -e /etc/resolvconf/resolv.conf.d/original ] ; then cp -a /etc/resolv.conf /etc/resolvconf/resolv.conf.d/original db_get resolvconf/link-tail-to-original if [ "$RET" = "true" ]; then ln -s original /etc/resolvconf/resolv.conf.d/tail else : > /etc/resolvconf/resolv.conf.d/tail fi else cp -a /etc/resolv.conf /etc/resolv.conf.dpkg-old fi mkdir -p /run/resolvconf/interface # Before creating the link, make sure that the original file is # at the target of the link. /sbin/resolvconf will overwrite # this when it does an update, of course. if [ ! -e /run/resolvconf/resolv.conf ] ; then cp -a /etc/resolv.conf /run/resolvconf/resolv.conf fi # Add the original file to the database so that its contents # are included when resolvconf updates. # Yes, this is an ugly workaround for the problem that there # is no way to obtain nameserver information from interface # configurers after they have done their configuration work. cp -a /etc/resolv.conf /run/resolvconf/interface/original.resolvconf fi # Create the link and make sure we don't convert it again on upgrade # The link is relative to allow for cp from outside a chroot into a chroot # to work without overwriting the file outside the chroot (or failing) ln -nsf ../run/resolvconf/resolv.conf /etc/resolv.conf db_set resolvconf/linkify-resolvconf false fi # FHS violation; get rid of it, we use /run directly now. if [ -e /etc/resolvconf/run ]; then rm -rf /etc/resolvconf/run fi ;; # triggered) # Don't do anything here # ;; # abort-upgrade) # Don't do anything here since we don't do anything in the prerm on upgrade or on failed-upgrade # ;; # abort-remove) # Don't do anything extra here since we don't deconfigure anything in the prerm on remove # ;; # abort-deconfigure) # Don't do anything extra here since we don't do anything in the prerm on deconfigure # ;; esac db_stop ### Notify others of our installation ### is_installed() { # Same function in preinst, postinst, postrm [ "$1" ] || return 1 dpkg-query -W -f='${Status}\n' "$1" 2>/dev/null | grep -siq '^[[:alpha:]]\+ [[:alpha:]]\+ installed$' >/dev/null 2>&1 } case "$1" in configure) if [ -f /run/resolvconf/packages-to-notify ] ; then PACKAGES_TO_NOTIFY="$(cat /run/resolvconf/packages-to-notify)" rm -f /run/resolvconf/packages-to-notify for PKG in $PACKAGES_TO_NOTIFY ; do if is_installed "$PKG" ; then SCRPT="/usr/lib/resolvconf/dpkg-event.d/$PKG" if [ -x "$SCRPT" ] ; then "$SCRPT" install || : fi fi done fi ;; # triggered) # Don't do anything # ;; # abort-upgrade) # Don't do anything here since we don't do anything in the prerm on upgrade or on failed-upgrade # ;; # abort-remove) # Don't do anything extra here since we don't deconfigure anything in the prerm on remove # ;; # abort-deconfigure) # Don't do anything extra here since we don't do anything in the prerm on deconfigure # ;; esac #DEBHELPER# exit 0 resolvconf-1.69ubuntu1/debian/resolvconf.resolvconf.if-down0000755000000000000000000000064312062416774021130 0ustar #!/bin/sh # # ifdown hook script for resolvconf # # This file is part of the resolvconf package. # [ -x /sbin/resolvconf ] || exit 0 case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac case "$METHOD" in dhcp) # Delete record left behind by TERMinated udhcpc # This works around bug #605215 /sbin/resolvconf -d "${IFACE}.udhcpc" || : ;; esac /sbin/resolvconf -d "${IFACE}.${ADDRFAM}" || : resolvconf-1.69ubuntu1/debian/manpages0000644000000000000000000000004712062416774015015 0ustar man/resolvconf.8 man/interface-order.5 resolvconf-1.69ubuntu1/debian/po/0000755000000000000000000000000012076277005013711 5ustar resolvconf-1.69ubuntu1/debian/po/es.po0000644000000000000000000002330612062416774014667 0ustar # Spanish translation of resolvconf debconf templates # Copyright (C) 2006-2011 Javier Fernndez-Sanguino # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.59\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-09-21 23:44+0200\n" "Last-Translator: Javier Fernndez-Sanguino \n" "Language-Team: Spanish \n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ISO-8859-15\n" "Content-Transfer-Encoding: 8bit\n" "X-POFile-SpellExtra: dns run DNS nameservers null resolv dev cachs tail\n" "X-POFile-SpellExtra: resolvconf conf README network\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "" "Preparar /etc/resolv.conf para poder tener actualizaciones dinmicas?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "El paquete resolvconf incluye la infraestructura necesaria para poder " "actualizar de forma dinmica el fichero de configuracin de resolucin. Un " "enlace simblico de /etc/resolv.conf a /run/resolvconf/resolv.conf es " "parte de la infraestructura necesaria. Si elije esta opcin se crear este " "enlace. Se preservarn los contenidos del fichero /etc/resolv.conf actual " "en el fichero /etc/resolvconf/resolv.conf.d/original y se restaurar este " "archivo si elimina el paquete." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Si rechaza esta opcin futuras instalaciones de este paquete no volvern a " "crear el enlace simblico, lo que significa que le fichero de configuracin " "de resolucin no se actualizar de forma dinmica. Puede activar la " "actualizacin dinmica siguiendo las instrucciones que encontrar en el " "fichero README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "No debera dejar resolvconf instalado si no est configurado ya que el hecho " "de que est instalado afectar al comportamiento de otros programas." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Se recomienda reiniciar" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Se espera que los proveedores de informacin de servidores de nombres, como " "puedan ser servidores de nombres con cach local y los sistemas que " "configuran las interfaces, de informacin al programa resolvconf. Sin " "embargo, aunque la instalacin del paquete resolvconf hace que stos " "proporcionen esta informacin, algunos de stos pueden no darla." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Este error puede dar lugar a la prdida de la informacin de servidores de " "nombres vlidos al instalar el paquete resolvconf si no se adoptar las " "siguientes medidas de para evitar el problema: resolvconf incluye los " "contenidos completos del fichero /etc/resolv.conf antes de la instalacin " "en su base de datos hasta un reinicio del sistema. Esto tiene el " "inconveniente de que la informacin de servidores de nombres se mantiene an " "cuando la interfaz asociada se desconfigure (se considera que este " "comportamiento invlido es menos perjuidicial que la alternativa de perder " "informacin vlida)." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Hasta que este error no se haya arreglado y se haya eliminado este arreglo " "transitorio, la nica forma de asegurarse que resolvconf tiene la " "informacin correcta de los servidores de nombres despus de su instalacin " "es reiniciar el sistema." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Es posible que la eliminacin del paquete resolvconf haya tenido como " "resultado la prdida de alguna informacin sobre los servidores de nombres. " "Se recomienda reiniciar el sistema para corregir este problema." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Aadir el fichero original al final del fichero dinmico?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Si su fichero de configuracin de resolucin esttica original (/etc/resolv." "conf) contiene direcciones de servidores de nombres, deber incluir estas " "direcciones en las lneas dns-nameservers en el fichero /etc/network/" "interfaces. Para ms informacin consulte la pgina de manual de resolvconf" "(8) y el fichero README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "No se incluirn las direcciones de los servidores de nombres en el fichero " "de configuracin de resolucin que se genera de forma dinmica hasta que no " "haya editado el fichero /etc/network/interfaces y haya parado y arrancado " "de nuevo las interfaces afectadas." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Se introducir una solucin temporal si escoge esta opcin: se crear un " "enlace simblico (si no existe todava) en /etc/resolvconf/resolv.conf/" "tail a /etc/resolvconf/resolv.conf.d/original. Esto har que se aada el " "contenido completo del fichero de configuracin de resolucin original al " "fichero generado de forma dinmica." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Debera reemplazar el enlace simblico /etc/resolvconf/resolv.conf.d/tail " "para que sea un enlace a /dev/null una vez haya aadido las lneas dns-" "nameservers necesarias a /etc/network/interfaces." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/it.po0000644000000000000000000002262312062416774014675 0ustar # Italian translation of resolvconf debconf templates # Copyright (C) 2008 Luca Monducci , # 2011 Marco Nenciarini # This file is distributed under the same license as the resolvconf package # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.57\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-28 11:03+0200\n" "Last-Translator: Marco Nenciarini \n" "Language-Team: Italian \n" "Language: it\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Preparare /etc/resolv.conf per l'aggiornamento dinamico?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Il pacchetto resolvconf contiene l'infrastruttura necessaria per aggiornare " "dinamicamente il file di configurazione della risoluzione dei nomi. Parte " "fondamentale dell'infrastruttura è il collegamento simbolico /etc/resolv." "conf verso /run/resolvconf/resolv.conf. Se si accetta verrà creato questo " "collegamento; il file /etc/resolv.conf esistente viene preservato come /etc/" "resolvconf/resolv.conf.d/original e verrà ripristinato alla rimozione di " "questo pacchetto." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Il rifiuto di questa opzione impedisce alle prossime installazioni di " "ricreare il collegamento simbolico e quindi la configurazione della " "risoluzione dei nomi non verrà aggiornata dinamicamente. L'aggiornamento " "dinamico può essere attivato seguendo le istruzioni nel file README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "La presenza di resolvconf può influenzare il funzionamento di altri " "programmi, quindi non deve essere lasciato non configurato." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Riavvio consigliato" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "I fornitori di informazioni sui name server, come i name server di cache e i " "configuratori di interfacce, sarebbero tenuti a fornire informazioni sui " "name server a resolvconf. Comunque, sebbene l'installazione del pacchetto " "resolvconf attivi in essi le procedure per comunicare tali informazioni, " "alcuni non riescono a farlo correttamente." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Questo bug potrebbe portare a una perdita di informazioni sui name server " "durante l'installazione del pacchetto resolvconf se non si adotta la " "seguente soluzione temporanea: resolvconf includerà il contenuto completo " "del file /etc/resolv.conf come era prima della sua installazione nel suo " "database fino al prossimo riavvio. Questo ha lo svantaggio che le " "informazioni sui name server saranno mantenute anche se l'interfaccia " "associata venisse disattivata. (Questo comportamento scorretto è giudicato " "meno dannoso dell'alternativa di perdere informazioni valide.)" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Fino a che il bug in questione non sarà corretto e non sarà rimossa la " "soluzione temporanea, il solo modo di assicurarsi che resolvconf abbia le " "informazioni corrette sui name server dopo che è stato installato su un " "sistema in esecuzione è riavviare il sistema." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "La rimozione del pacchetto resolvconf potrebbe aver reso indisponibili " "alcune informazioni sui name server. Per correggere questo problema si " "consiglia un riavvio del sistema." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Aggiungere il file originale al file dinamico?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Se il file di configurazione della risoluzione dei nomi (/etc/resolv.conf) " "contiene gli indirizzi del name server, questi indirizzi devono essere " "elencati nelle righe \"dns-nameservers\" in /etc/network/interfaces. Per " "ulteriori informazioni consultare la pagina man di resolvconf(8) e il file " "README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Finché non viene modificato /etc/network/interfaces e le interfacce non sono " "disattivate e poi riattivate, gli indirizzi del name server non verranno " "inseriti nel file di configurazione della risoluzione dei nomi generato " "dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Se si accetta, viene realizzata un soluzione temporanea: viene creato (se " "non esiste) un collegamento simbolico da /etc/resolvconf/resolv.conf.d/tail " "a /etc/resolvconf/resolv.conf.d/original. Questo comporta che il file " "originale di configurazione per la risoluzione dei nomi viene aggiunto in " "coda a quello generato dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Una volta aggiunte le righe obbligatorie \"dns-nameservers\" a /etc/network/" "interfaces, il collegamento /etc/resolvconf/resolv.conf.d/tail deve essere " "sostituito con uno verso /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/cs.po0000644000000000000000000002201512062416774014661 0ustar # Czech translation of resolvconf debconf templates # Copyright (C) 2008, 2011 Miroslav Kure # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.56\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-15 15:02+0200\n" "Last-Translator: Miroslav Kure \n" "Language-Team: Czech \n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Připravit /etc/resolv.conf pro dynamické aktualizace?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Balík resolvconf obsahuje infrastrukturu vyžadovanou pro dynamické " "aktualizace konfiguračního souboru resolveru. Součástí infrastruktury je i " "symbolický odkaz z /etc/resolv.conf na /run/resolvconf/resolv.conf. Pokud " "budete souhlasit, odkaz se vytvoří automaticky. Stávající /etc/resolv.conf " "bude zachován jako /etc/resolvconf/resolv.conf.d/original a při odstranění " "balíku bude obnoven." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Zamítnutí této volby zabrání budoucím instalacím, aby vytvářely symbolický " "odkaz, v důsledku čehož nebude konfigurační soubor resolveru aktualizován " "dynamicky. Pro aktivování dynamických aktualizací postupujte dle instrukcí v " "souboru README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Přítomnost resolvconfu může ovlivnit chování ostatních programů, takže pokud " "balík nenastavíte, měli byste jej raději odinstalovat." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Doporučuje se restartovat systém" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "resolvconf očekává, že mu informace o jmenných serverech poskytnou programy " "k tomu určené, jako jsou lokální cachovací jmenné servery nebo programy pro " "konfiguraci síťových rozhraní. Přestože si od nich resolvconf při instalaci " "tyto informace vyžádá, některé programy bohužel neodpoví." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Tato chyba by při instalaci resolvconfu vedla ke ztrátě informací o platném " "jmenném serveru a proto existuje následující obezlička: resolvconf až do " "restartu ve své databázi uchová kompletní obsah souboru /etc/resolv.conf z " "doby před instalací resolvconfu. To má nevýhodu v tom, že pokud je příslušné " "síťové rozhraní vypnuto, informace o svázaném jmenném serveru v resolvconfu " "zůstává, což je považováno za menší zlo, než ztráta platné informace." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Dokud se zmíněná chyba nevyřeší, je restart systému jediným způsobem jak " "zajistit, aby měl resolvconf po čerstvé instalaci správné informace o " "jmenném serveru." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Odstranění balíku resolvconf může způsobit, že některé informace o jmenných " "serverech nebudou dostupné. Pro nápravu tohoto problému se doporučuje " "restartovat systém." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Připojit původní soubor k dynamickému souboru?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Pokud váš původní statický konfigurační soubor (/etc/resolv.conf) obsahuje " "adresy jmenných serverů, pak by měly být tyto adresy vypsány na řádcích „dns-" "nameservers“ v souboru /etc/network/interfaces. Více informací naleznete v " "manuálové stránce resolvconf(8) a souboru README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Dokud neupravíte /etc/network/interfaces a znovu nenakonfigurujete postižená " "rozhraní, neobjeví se adresy jmenných serverů v dynamicky generovaném " "konfiguračním souboru souboru resolveru." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Vyberete-li tuto možnost, použije se dočasné řešení: vytvoří se symbolický " "odkaz z /etc/resolvconf/resolv.conf.d/tail na /etc/resolvconf/resolv.conf.d/" "original (pokud již neexisuje). To způsobí, že se na konec dynamicky " "generovaného souboru připojí celý původní konfigurační soubor resolveru." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Až do souboru /etc/network/interfaces přidáte požadované řádky „dns-" "nameservers“, měli byste přesměrovat symbolický odkaz /etc/resolvconf/resolv." "conf.d/tail na /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/templates.pot0000644000000000000000000001353712062416774016447 0ustar # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: resolvconf\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/eu.po0000644000000000000000000002237012062416774014671 0ustar # Basque translation of resolvconf debconf templates # Copyright (C) 2009 Piarres Beobide EGaña , # 2011 Iñaki Larrañaga Murgoitio # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.55\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-06 15:34+0200\n" "Last-Translator: Iñaki Larrañaga Murgoitio \n" "Language-Team: Basque \n" "Language: eu\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.4\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Prestatu /etc/resolv.conf eguneraketa dinamikoentzat?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Resolvconf paketeak ebazlearen konfigurazioko fitxategia automatikoki " "eguneratzeko beharrezkoa den azpiegitura du. Beharrezko azpiegitura horren " "zati bat /etc/resolv.conf fitxategiaren /run/resolvconf/resolv.conf arteko " "esteka sinboliko bat da. Aukera hau hautatzean, esteka hori sortuko da; " "aurretik dagoen /etc/resolv.conf fitxategia /etc/resolvconf/resolv.conf.d/" "original izenarekin gordeko da, eta berriz leheneratuko da paketea kentzean." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Aukera hau baztertzeak hurrengo instalazioetan esteka sortzea desgaituko du, " "eta ondorioz, ebazlearen konfigurazioko fitxategia ez da dinamikoki " "eguneratuko. Eguneraketa dinamikoa README fitxategiko argibideak jarraituz " "gaitu daiteke." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Resolvconf egoteak beste programa batzuen portamoldea aldatu dezake, beraz " "ez litzateke konfiguratu gabe instalaturik utzi beharko." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Berrabiaraztea gomendatzen da" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Izen-zerbitzarien informazioaren hornitzaileak, hala nola cache lokaleko " "izen-zerbitzariak eta konfiguratzaileen interfazeak, espero dira izen-" "zerbitzarien informazioa resolvconf programari emateko. Hala ere, nahiz eta " "resolvconf paketearen instalazioak haiek abiarazi beraien informazioa " "emateko, haietariko batzuk huts egin dezakete." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Akats honek resolvconf paketearen instalazioko baliozko izen-zerbitzariaren " "informazioa galtzea eragin dezake honako konponbidea ez bada lantzen: " "resolvconf-ek aurre-instalazioko /etc/resolv.conf fitxategiaren eduki osoa " "edukitzen du bere datu-basean berrabiarazi arte. Honek badu bere eragozpena, " "izen-zerbitzariaren informazioa mantenduko baita nahiz eta esleitutako " "interfazea beranduago deskonfiguratua izan. Portaera desegoki honek baliozko " "informazioa galtzea baino kalte gutxiago sortzen duela suposatzen da." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Akats hori konpondu eta konponbidea kendu arte, resolvconf-k baliozko izen-" "zerbitzariaren informazio osoa duela ziurtatzeko era bakarra resolvconf " "paketea instalatu ondoren exekutatzen ari den sistema batean sistema " "berrabiaraztea da." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "resolvconf paketea kentzeak izen-zerbitzariei buruzko informazio batzuk " "eskuragarri ez egotea eragin dezake. Arazo hau konpontzeko, sistema " "berrabiaraztea gomendatzen da." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Erantsi jatorrizko fitxategia fitxategi dinamikora?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Jatorrizko ebazpen 'finko' konfigurazio fitxategiak (etc/resolv.conf) izen-" "zerbitzariak baditu, helbide horiek /etc/network/interfaces fitxategiko " "\"dns-nameservers\" lerroetan gehitu beharko dira. Argibide gehiagorako " "irakurri itzazu resolvconf(8) manual orrialdea eta README fitxategia." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Behin /etc/network/interfaces editatua izan denean eta dagozkion interfazeak " "desgaitu eta gaitu arte izen-zerbitzari helbideak ez dira gehituko " "dinamikoki sortutako ebazte konfigurazio fitxategian." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Aukera hau hautatzen baduzu aldiroko portamolde bat erabiliko da, lotura " "sinboliko bat sortuko da (dagoeneko ez badago) /etc/resolvconf/resolv.conf.d/" "tail eta /etc/resolvconf/resolv.conf.d/original artean. Honela jatorrizko " "ebazte konfigurazio fitxategia dinamikoki sortutakoari erantsiko zaio." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Behin beharrezko \"dns-nameservers\" lerroak /etc/network/interfaces " "fitxategira gehitu direnean, /etc/resolvconf/resolv.conf.d/tail lotura /dev/" "null-erako batez ordeztu beharko zen." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/sk.po0000644000000000000000000002353112062416774014675 0ustar # Slovak translation of resolvconf debconf templates # Copyright (C) 2012 Slavko # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.67\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2012-08-02 18:35+0200\n" "Last-Translator: Slavko \n" "Language-Team: slovenčina \n" "Language: sk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" "X-POFile-SpellExtra: tail network interfaces resolv dns-nameservers etc\n" "X-POFile-SpellExtra: resolvconf conf README null original kešovacie\n" "X-POFile-SpellExtra: resolvera\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Pripraviť /etc/resolv.conf na dynamické aktualizácie?" #. Type: boolean #. Description #: ../templates:2001 #, fuzzy #| msgid "" #| "The resolvconf package contains the infrastructure required for dynamic " #| "updating of the resolver configuration file. Part of the necessary " #| "infrastructure is a symbolic link from /etc/resolv.conf to /etc/" #| "resolvconf/run/resolv.conf. If you choose this option then this link will " #| "be created; the existing /etc/resolv.conf file will be preserved as /etc/" #| "resolvconf/resolv.conf.d/original, and will be restored if this package " #| "is removed." msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Balík resolvconf obsahuje infraštruktúru, ktorá je potrebná na dynamickú " "aktualizáciu konfiguračného súboru resolvera. Časťou potrebnej " "infraštruktúry je symbolický odkaz z /etc/resolv.conf do /etc/resolvconf/run/" "resolv.conf. Ak zvolíte túto možnosť, bude tento odkaz vytvorený; existujúci " "súbor /etc/resolv.conf bude zachovaný ako /etc/resolvconf/resolv.conf.d/" "original a bude obnovený pri odstránení balíka." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Odmietnutie tejto možnosti zabráni budúcim inštaláciám v opätovnom vytváraní " "symbolického odkazu, a tak nebude konfiguračný súbor resolvera automaticky " "aktualizovaný. Dynamické aktualizácie môžu byť potom aktivované podľa " "inštrukcií v súbore README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Prítomnosť resolvconf môže ovplyvniť správanie sa ostatných programov, tak " "by nemal ostať nainštalovaný, ak nie je nastavený." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Odporúčame reštart" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Na poskytnutie informácií menného servera programu resolvconf sú očakávaný " "poskytovatelia informácií menného servera, ako napr. lokálne kešovacie menné " "servery a konfigurátory rozhrania. Avšak, hoci ich inštalácia balíka o " "poskytnutie informácií požiada, niektoré z nich pri tom zlyhávajú." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Táto chyba môže mať za následok stratu informácií o platnom mennom serveri " "pri inštalácii balíka resolvconf, ak nebude prijatá nasledujúca oprava: " "resolvconf zahŕňa vo svojej databáze úplný obsah pôvodného /etc/resolv.conf " "až do reštartu. Je to nevýhoda, keď informácie menného servera sú zachované, " "dokonca i keď je priradené rozhranie neskôr vypnuté (toto nesprávne " "správanie je posúdené ako menej škodlivá alternatíva straty informácií)." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Kým nebude táto chyba opravená a táto oprava odstránená, jediným spôsobom " "ako zaistiť, že resolvconf má úplné a správne informácie o mennom serveri po " "nainštalovaní balíka resolvconf na bežiacom systéme je reštartovať systém." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Odstránenie balíka resolvconf môže mať za následok, že niektoré informácie o " "menných serveroch nebudú dostupné. Na nápravu tohoto problému je odporúčané " "reštartovať systém." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Pripojiť pôvodný súbor k dynamickému súboru?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Ak pôvodný statický konfiguračný súbor resolvera (/etc/resolv.conf) obsahuje " "adresy menného servera, tieto adresy musia byť vypísané v riadkoch \"dns-" "nameservers\" v súbore /etc/network/interfaces. ďalšie podrobnosti hľadajte " "v manuálovej stránke resolvconf(8) a v súbore README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Ak bol súbor /etc/network/interfaces zmenený, kým nebudú dotknuté rozhrania " "vypnuté a znova zapnuté, adresy menného servera nebudú zahrnuté v dynamicky " "generovanom konfiguračnom súbore resolvera." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Ak zvolíte túto možnosť, bude použitá dočasná oprava: bude vytvorený " "symbolický odkaz (ak ešte neexistuje) z /etc/resolvconf/resolv.conf.d/tail " "do /etc/resolvconf/resolv.conf.d/original. Takýmto spôsobom bude celý obsah " "pôvodného konfiguračného súboru resolvera pripojený k dynamicky generovanému " "súboru." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Po pridaní požadovaných riadkov \"dns-nameservers\" do /etc/network/" "interfaces, bude odkaz /etc/resolvconf/resolv.conf.d/tail nahradený odkazom " "do /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/POTFILES.in0000644000000000000000000000004412062416774015467 0ustar [type: gettext/rfc822deb] templates resolvconf-1.69ubuntu1/debian/po/ja.po0000644000000000000000000002054212062416774014651 0ustar # Japanese translation of resolvconf debconf templates # Copyright (C) 2008 Hideki Yamane # This file is distributed under the same license as the resolvconf package # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.41\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2008-08-03 21:04+0900\n" "Last-Translator: Hideki Yamane (Debian-JP) \n" "Language-Team: Japanese \n" "Language: ja\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "/etc/resolv.conf を動的更新するようにしますか?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "resolvconf パッケージは、リゾルバ設定ファイルの動的更新に必要とされる仕組みを" "含んでいます。必要となる仕組みの一つは /etc/resolv.conf から /run/resolvconf/" "resolv.conf へのシンボリックリンクです。このオプションを選ぶとこのリンクが作" "成されます。すでにある /etc/resolv.conf ファイルは /etc/resolvconf/resolv." "conf.d/original として保存されます (このファイルは、パッケージが削除される際" "に元に戻されます)。" #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "このオプションの利用を断ると、今後のインストール時にシンボリックリンクの再生" "成を行わないようになります。そのため、リゾルバの設定ファイルは動的に更新され" "なくなります。そのような場合、動的更新を可能にするには README ファイルにある" "指示に従ってください。" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "resolvconf の存在によって他のプログラムの動作に影響が与える可能性があるので、" "インストールしたのにも関わらず未設定のままにはしていけません。" #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "更新されるファイルにオリジナルのファイルを追加しますか?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "元々の静的な名前解決ファイル (/etc/resolv.conf) がネームサーバのアドレスを含" "んでいる場合、これらのアドレスは、/etc/network/interfaces の \"dns-" "nameservers\" 行に記述されている必要があります。詳細に付いては、resolvconf" "(8) の man ページと README ファイルを参照してください。" #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "/etc/network/interfaces を編集し、関連するインターフェイスをダウンして再度" "アップするようになるまで、ネームサーバのアドレスは動的に生成される名前解決" "ファイルに含まれません。" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "この選択を選んだ場合、一時的な回避方法があります。(まだファイルが存在していな" "い場合) /etc/resolvconf/resolv.conf.d/tail から /etc/resolvconf/resolv.conf." "d/original へシンボリックリンクが作られます。これによって、元々のリゾルバ設定" "ファイルが丸ごと動的に生成されるファイルに追加されます。" #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "/etc/network/interfaces に必要な \"dns-nameservers\" 行を加えた後、/etc/" "resolvconf/resolv.conf.d/tail へのシンボリックリンクを /dev/null へのリンクに" "変更する必要があります。" #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/fi.po0000644000000000000000000001767312062416774014670 0ustar # Finnish translation of resolvconf debconf templates # Copyright (C) 2011 Esko Arajärvi # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.38\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2008-02-20 00:13+0200\n" "Last-Translator: Esko Arajärvi \n" "Language-Team: Finnish \n" "Language: fi\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Finnish\n" "X-Poedit-Country: FINLAND\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Valmistele /etc/resolv.conf dynaamisia päivityksiä varten?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Paketti resolvconf sisältää tarvittavat rakenteet selvittäjän " "asetustiedoston dynaamiseksi päivittämiseksi. Yksi tarpeellinen osa on " "symbolinen linkki nimeltä /etc/resolv.conf tiedostoon /run/resolvconf/resolv." "conf. Jos valitset tämän vaihtoehdon, linkki luodaan. Olemassa oleva " "tiedosto /etc/resolv.conf talletetaan nimelle /etc/resolvconf/resolv.conf.d/" "original ja palautetaan, jos tämä paketti poistetaan." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Jos et valitse tätä vaihtoehtoa, tulevat asennukset eivät voi luoda " "uudelleen kyseistä symbolista linkkiä ja siksi selvittäjän asetustiedostoa " "ei päivitetä dynaamisesti. Dynaaminen päivitys voidaan aktivoida seuraamalla " "tiedostossa README olevia ohjeita." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Paketin resolvconf oleminen järjestelmässä saattaa vaikuttaa toisten " "ohjelmien toimintaan, joten sitä ei tulisi jättää asennetuksi, jos sen " "asetuksia ei ole tehty." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Lisätäänkö alkuperäinen tiedosto dynaamiseen tiedostoon?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Jos alkuperäinen staattinen selvittäjän asetustiedosto (/etc/resolv.conf) " "sisältää nimipalvelimien osoitteita, osoitteet tulisi listata ”dns-" "nameservers”-riveillä tiedostossa /etc/network/interfaces. Lisätietoja " "löytyy man-ohjesivulta resolvconf(8) ja README-tiedostosta." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Nimipalvelimien osoitteet sisällytetään dynaamisesti luotuun selvittäjän " "asetustiedostoon vasta, kun tiedostoa /etc/network/interfaces on muokattu ja " "muutetut liitynnät on käynnistetty uudelleen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Jos valitset tämän vaihtoehdon, ongelma kierretään väliaikaisesti " "seuraavasti: Sijainnista /etc/resolvconf/resolv.conf.d/tail luodaan " "symbolinen linkki tiedostoon /etc/resolvconf/resolv.conf.d/original (jos " "sitä ei jo ole olemassa). Tällöin koko alkuperäinen selvittäjän " "asetustiedosto lisätään dynaamisesti luotuun tiedostoon." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Kun vaaditut ”dns-nameservers”-rivit on lisätty tiedostoon /etc/network/" "interfaces, Linkki /etc/resolvconf/resolv.conf.d/tail tulisi muuttaa " "osoittamaan sijaintiin /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/gl.po0000644000000000000000000001763112062416774014666 0ustar # Galician translation of resolvconf debconf templates # Copyright (C) 2007, 2008 Jacobo Tarrio # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.37\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2008-02-11 19:03+0000\n" "Last-Translator: Jacobo Tarrio \n" "Language-Team: Galician \n" "Language: gl\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "¿Preparar /etc/resolv.conf para actualizacións dinámicas?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "O paquete \"resolvconf\" contén a infraestrutura necesaria para actualizar " "dinamicamente o ficheiro de configuración do resolvedor. Parte dela é unha " "ligazón simbólica de /etc/resolv.conf a /run/resolvconf/resolv.conf. Se " "escolle esta opción, hase crear esa ligazón; o ficheiro /etc/resolv.conf " "existente hase conservar coma /etc/resolvconf/resolv.conf.d/original , e " "hase restaurar se se elimina este paquete." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Se rexeita esta opción, as futuras instalacións non han poder volver crear a " "ligazón simbólica e, polo tanto, non se ha actualizar dinamicamente o " "ficheiro de configuración do resolvedor. A actualización dinámica hase poder " "activar seguindo as instruccións do ficheiro README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "A presencia de resolvconf pode afectar ao comportamento de outros programas, " "así que non se debería deixar instalado sen configurar." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "¿Engadir o ficheiro orixinal ao ficheiro dinámico?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Se o ficheiro de configuración do resolvedor estático orixinal (/etc/resolv." "conf) contén enderezos de servidores de nomes, eses enderezos deberían " "figurar en liñas \"dns-nameservers\" do ficheiro /etc/network/interfaces. " "Para máis información, consulte a páxina de manual de resolvconf(8) e o " "ficheiro README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Ata que edite o ficheiro /etc/network/interfaces e as interfaces afectadas " "se baixen e volvan erguer, non se han incluír os enderezos dos servidores de " "nomes no ficheiro de configuración do resolvedor xerado dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Se escolle esta opción, hase establecer unha solución temporal: hase crear " "unha ligazón simbólica (se non existe xa) de /etc/resolvconf/resolv.conf.d/" "tail a /etc/resolvconf/resolv.conf.d/original . Isto ha facer que todo o " "contido dese ficheiro de configuración orixinal se engada ao ficheiro xerado " "dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Despois de engadir as liñas \"dns-nameserver\" necesarias ao ficheiro /etc/" "network/interfaces , deberíase substituír a ligazón /etc/resolvconf/resolv." "conf.d/tail por unha ligazón a /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/pt.po0000644000000000000000000002241012062416774014676 0ustar # Portuguese translation of resolvconf debconf templates # Copyright (C) 2008, 2011 Pedro Ribeiro # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf_1.56\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-24 23:33+0000\n" "Last-Translator: Pedro Ribeiro \n" "Language-Team: Portuguese \n" "Language: pt\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Preparar /etc/resolv.conf para actualizações dinâmicas?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "O pacote resolvconf contém a infraestrutura requerida para actualizar " "dinamicamente o ficheiro de configuração do resolver. Parte da " "infraestrutura necessária é uma ligação simbólica de /etc/resolv.conf para /" "run/resolvconf/resolv.conf. Se concordar, esta ligação será criada. O " "ficheiro /etc/resolv.conf existente será mantido como /etc/resolvconf/resolv." "conf.d/original; será reposto se este pacote for removido." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Não aceitar esta opção irá prevenir futuras instalações de recriar a ligação " "simbólica e portanto o ficheiro de configuração do resolver não será " "dinamicamente actualizado. A actualização dinâmica pode então ser activada " "seguindo as instruções do ficheiro README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "A presença do resolvconf pode afectar o comportamento de outros programas, " "por isso não deve ser deixado instalado se não-configurado." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Re-início do sistema recomendado" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Os fornecedores de informação de servidor de nomes, tais como servidores de " "nome com cache local e configuradores de interfaces, devem fornecer essa " "informação ao resolvconf. No entanto, embora a instalação do pacote " "resolvconf despolete a entrega dessa informação, alguns deles não o fazem." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Esta falha levaria à perda de informação válida do servidor de nomes após a " "instalação do resolvconf se o seguinte procedimento não fosse adoptado: o " "resolvconf inclui todo o conteúdo do /etc/resolv.conf pré-existente na sua " "base de dados até ao re-início seguinte. Isto tem a desvantagem da " "informação do servidor de nomes ser retida mesmo que a interface associada " "seja desconfigurada. (Este comportamento incorrecto é julgado menos " "prejudicial que a alternativa de perder informação válida.)" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Até que esta falha esteja resolvida e o procedimento removido, a única " "maneira de assegurar que o resolvconf tem informação completamente correcta " "dos servidores de nome após a instalação do pacote resolvconf num sistema é " "reiniciar o sistema." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "A remoção do pacote resolvconf pode ter resultado na indisponibilidade de " "alguma informação acerca de servidores de nomes. Para corrigir este problema " "é recomendável que o sistema seja reiniciado." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Acrescentar o ficheiro original ao ficheiro dinâmico?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Se o ficheiro original de configuração estática do resolver (/etc/resolv." "conf) contém endereços de servidores de nomes, esses endereços devem estar " "listados em linhas \"dns-nameservers\" em /etc/network/interfaces.Para mais " "informação, por favor consulte a página de manual resolvonf(8) e o ficheiro " "README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Até /etc/networks/interfaces ter sido editado e as interfaces afectadas re-" "iniciadas, os endereços dos servidores de nomes não serão incluídos no " "ficheiro de configuração do resolver gerado dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Se escolher esta opção, uma resolução temporária será posta em " "funcionamento: uma ligação simbólica será criada (se não existir) de /etc/" "resolvconf/resolv.conf.d/tail para /etc/resolvconf/resolv.conf.d/original. " "Isto irá fazer com que toda a configuração estática seja acrescentada ao " "ficheiro gerado dinamicamente." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Após as linhas \"dns-nameserver\" necessárias terem sido acrescentadas ao " "ficheiro /etc/network/interfaces, a ligação simbólica /etc/resolvconf/resolv." "conf.d/tail deve ser substituída por uma para /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/nl.po0000644000000000000000000002250312062416774014667 0ustar # Dutch translation of resolvconf debconf templates # Copyright (C) 2011 Vincent Zweije # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.56\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-24 14:04+0200\n" "Last-Translator: Vincent Zweije \n" "Language-Team: Dutch \n" "Language: nl\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "/etc/resolv.conf klaar maken voor automatische bijwerkingen?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Het resolvconf-pakket bevat de infrastructuur om automatisch bijwerken van " "het resolver-configuratiebestand mogelijk te maken. Een gedeelte van de " "noodzakelijke infrastructuur is een symbolische koppeling van /etc/resolv." "conf naar /run/resolvconf/resolv.conf. Als u deze optie accepteert zal deze " "koppeling gemaakt worden; het bestaande /etc/resolv.conf-bestand zal worden " "bewaard als /etc/resolvconf/resolv.conf.d/original en zal worden " "teruggeplaatst als het pakket wordt verwijderd." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Het weigeren van deze optie voorkomt dat toekomstige installaties de " "symbolische koppeling terug aanmaken; bijgevolg zal het resolver-" "configuratiebestand niet dynamisch worden bijgewerkt. Dynamisch bijwerken " "kan alsnog worden geactiveerd door de instructies in de README te volgen." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "De aanwezigheid van resolvconf kan het gedrag van andere programma's " "beïnvloeden. Het is dus af te raden om dit pakket ongeconfigureerd, maar wel " "geïnstalleerd te laten." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Herstart aanbevolen" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Van programma's die naamserver-informatie leveren, zoals lokale naamservers " "en interface-configuratieprogramma's, wordt verwacht dat zij naamserver-" "informatie aan het resolvconf programma doorgeven. Sommigen doen dit echter " "niet, hoewel de installatie van het resolvconf-pakket hun daartoe een " "signaal geeft." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Deze fout kan leiden tot verlies van geldige naamserver-informatie bij " "installatie van het resolvconf-pakket. Daarom is er de volgende maatregel: " "resolvconf neemt de volledige inhoud van /etc/resolv.conf van voor zijn " "installatie over tot aan de volgende herstart. Het nadeel van deze maatregel " "is dat naamserver-informatie wordt vastgehouden, zelfs als de bijbehorende " "interface later wordt gedeconfigureerd. Dit op zich onjuiste gedrag wordt " "beschouwd als minder schadelijk dan het alternatief waarbij geldige " "informatie verloren gaat." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Totdat de feitelijke fout is verholpen en de maatregel is verwijderd, is " "herstarten van het systeem de enige manier om te garanderen dat resolvconf " "na installatie volledig juiste naamserver-informatie heeft." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Door het verwijderen van het resolvconf-pakket is sommige informatie over " "naamservers mogelijk niet meer beschikbaar. Om dit probleem op te lossen " "wordt een herstart aanbevolen." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Originele bestand aan het eind van dynamische bestand toevoegen?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Als het originele statische resolver-configuratiebestand (/etc/resolv.conf) " "naamserver-adressen bevatte, dan dienen die adressen te worden genoemd op " "\"dns-nameservers\"-regels in /etc/network/interfaces. Zie voor nadere " "informatie de resolvconf(8) manpagina en de README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Tot op het moment waarop /etc/network/interfaces is aangepast en de " "betreffende netwerk-interfaces opnieuw zijn ingesteld, zullen deze adressen " "niet in het automatisch gegenereerde resolver-configuratiebestand zijn " "opgenomen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Indien u deze optie accepteert zal een tijdelijke oplossing worden " "neergezet: een symbolische koppeling zal worden aangemaakt (als deze nog " "niet bestaat) van /etc/resolvconf/resolv.conf.d/tail naar /etc/resolvconf/" "resolv.conf.d/original. Hierdoor zal het volledige oorspronkelijke " "configuratiebestand achter aan het dynamisch gegenereerde bestand worden " "toegevoegd." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Nadat de benodigde \"dns-nameservers\"-regels zijn toegevoegd aan /etc/" "network/interfaces, dient de symbolische koppeling /etc/resolvconf/resolv." "conf.d/tail te worden vervangen door één die naar /dev/null wijst." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/fr.po0000644000000000000000000002344112062416774014667 0ustar # French translation of resolvconf debconf templates # Copyright (C) 2008, 2011 Christian Perrier # This file is distributed under the same license as the resolvconf package. # # Relecteurs : # Philippe Batailler # Daniel Déchelotte # Nicolas Boullis # Frédéric ZULIAN # Christian Perrier # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.55\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-03 08:07+0200\n" "Last-Translator: Christian Perrier \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 1.2\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Faut-il préparer /etc/resolv.conf pour les mises à jour dynamiques ?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Le paquet resolvconf installe l'infrastructure permettant la mise à jour du " "fichier de configuration du résolveur. Une des modifications nécessaires est " "la mise en place d'un lien symbolique depuis /etc/resolv.conf vers /run/" "resolvconf/resolv.conf. Si vous choisissez cette option, ce lien sera créé. " "Le fichier /etc/resolv.conf sera conservé sous le nom de /etc/resolvconf/" "resolv.conf.d/original. Si ce paquet est enlevé, le fichier sera remis dans " "son état original." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Si vous ne choisissez pas cette option, les installations ultérieures ne " "tenteront pas de créer ce lien et le fichier de configuration ne sera pas " "mis à jour dynamiquement. Pour activer la mise à jour dynamique, il sera " "alors nécessaire de suivre les instructions du fichier README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "La présence de resolvconf peut modifier le comportement de certains " "programmes et il ne devrait pas être laissé en place s'il n'est pas " "configuré." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Redémarrage recommandé" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Les programmes en charge de la fourniture des informations de service de " "noms tels que les programmes locaux de cache de service de noms et les " "configurateurs d'interfaces doivent fournir les informations de service de " "noms au programme resolvconf. Cependant, bien que l'installation de celui-ci " "déclenche une demande de mise à jour de ces informations, certains échouent " "à l'effectuer." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Ce bogue pourrait conduire à la perte d'informations valables lors de " "l'installation du paquet resolvconf si les contournements suivants ne sont " "pas mis en œuvre : resolvconf inclut le contenu complet du fichier /etc/" "resolv.conf précédant l'installation jusqu'au redémarrage qui suit. Ce " "contournement a le défaut de conserver l'information de service de noms même " "si l'interface réseau en question est déconfigurée, ce qui est jugé moins " "ennuyeux que la perte possible d'informations." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "En attendant que ce bogue soit corrigé et le contournement retiré, la seule " "façon de garantir que resolvconf possède les informations entièrement " "correctes de service de noms après son installation sur un système est le " "redémarrage de ce système." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "La suppression du paquet resolvconf peut avoir eu comme conséquence " "l'indisponibilité d'informations sur les serveurs de noms. Pour corriger ce " "problème, il est recommandé de redémarrer le système." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Faut-il ajouter le fichier original au fichier dynamique ?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Si le fichier de configuration d'origine du résolveur (/etc/resolv.conf) " "contient des adresses de serveurs de noms, ces adresses peuvent être " "indiquées dans les lignes « dns-nameservers » du fichier /etc/network/" "interfaces. Pour plus d'informations, veuillez consulter la page de manuel " "de resolvconf et le fichier README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Tant que le fichier /etc/network/interfaces n'aura pas été modifié et que " "les interfaces concernées n'auront pas été redémarrées, les adresses des " "serveurs de noms ne seront pas ajoutées au fichier de configuration créé " "dynamiquement." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Si vous choisissez cette option, un contournement temporaire sera établi : " "un lien symbolique sera créé (s'il n'existe pas déjà), de /etc/resolvconf/" "resolv.conf.d/tail vers /etc/resolvconf/resolv.conf.d/original. Cela " "ajoutera l'ensemble du fichier initial de configuration du résolveur à la " "fin du fichier créé dynamiquement." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Après avoir modifié /etc/network/interfaces pour ajouter les lignes « dns-" "nameservers », vous devriez faire pointer le lien symbolique /etc/resolvconf/" "resolv.conf.d/tail vers /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/ru.po0000644000000000000000000002662312062416774014713 0ustar # Russian translation of resolvconf debconf templates # Copyright (C) 2006, 2008, 2011 Yuri Kozlov # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.55\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-04 10:55+0400\n" "Last-Translator: Yuri Kozlov \n" "Language-Team: Russian \n" "Language: ru\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 1.0\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Включить динамическое обновление /etc/resolv.conf?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Пакет resolvconf содержит инфраструктуру для динамического обновления файла " "настройки определителя имён. Одной из необходимых частей инфраструктуры " "является символическая ссылка /etc/resolv.conf на /run/resolvconf/resolv." "conf. Если вы ответите утвердительно, то такая ссылка будет создана. " "Существующий файл /etc/resolv.conf будет сохранён под именем /etc/resolvconf/" "resolv.conf.d/original, и будет восстановлен при удалении пакета." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "В случае отрицательного ответа символическая ссылка не будет создана при " "будущих установках и следовательно файл настройки определителя имён не будет " "динамически обновляться. Чтобы включить динамическое обновление, можно " "настроить resolvconf вручную следуя простым инструкциям из файла README." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Присутствие в системе ненастроенного пакета resolvconf может повлиять на " "другие программы, поэтому лучше его удалить." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Рекомендуется перезагрузка" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Ожидается, что информация о сервере имён для программы resolvconf будет " "получена от других программ, таких как локальные кэширущие серверы имён и " "настройщики интерфейсов. Однако, хотя процедура установки пакета resolvconf " "запросила эту информацию, некоторые из них не могут её выдать." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Этот дефект привёл бы к потере информации о сервере имён при установке " "пакета resolvconf, если не было применено следующее обходное решение: " "resolvconf включил всё содержимое /etc/resolv.conf, которое было до " "установки, в свою базу данных до перезагрузки. Но в этом решении есть " "недостаток: информация о сервере имён останется, даже если со связанного с " "ней интерфейса позднее будут удалены настройки (это некорректное поведение " "считается менее болезненным, чем потеря достоверной информации)." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Пока рассматриваемая ошибка не исправлена, и обходное решение не удалено, " "единственный путь гарантировать, что у resolvconf есть полностью корректная " "информация о сервере имён после установки пакета resolvconf пакет в рабочую " "систему, это перезагрузка системы." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Удаление пакета resolvconf может привести потере информации о серверах имён. " "Для устранения проблемы перезагрузите систему." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Добавить имеющийся файл в динамически обновляемый файл?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Если ваш статический файл настройки определителя имён (/etc/resolv.conf) " "содержит адреса серверов имён, то эти адреса должны быть записаны в строках " "«dns-nameservers» в файл /etc/network/interfaces. Подробней об этом написано " "на странице руководства resolvconf(8) и в файле README." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Пока файл /etc/network/interfaces не будет отредактирован и задействованные " "интерфейсы не будут перезапущены, адреса серверов имён не будут добавляться " "в динамически создаваемый файл настройки определителя." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Если вы ответите утвердительно, то будет активировано временное решение: " "будет создана символическая ссылка (если её ещё не было) /etc/resolvconf/" "resolv.conf.d/tail на файл /etc/resolvconf/resolv.conf.d/original. Это " "приведёт к добавлению всего содержимого имеющего файла настройки " "определителя в динамически создаваемый файл." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "После добавления в /etc/network/interfaces необходимых строк «dns-" "nameservers», нужно изменить символическую ссылку /etc/resolvconf/resolv." "conf.d/tail, чтобы она указывала на /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/sv.po0000644000000000000000000002214412062416774014707 0ustar # Swedish translation of resolvconf debconf templates # Copyright (C) 2008, 2011 Martin Bagge # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.55\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-03 03:44+0100\n" "Last-Translator: Martin Bagge / brother \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Swedish\n" "X-Poedit-Country: Sweden\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Förbered /etc/resolv.conf för dynamiska uppdateringar?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Detta paket innehåller infrastrukturen som krävs för dynamiska uppdateringar " "av filen för uppslagskonfigurationen. En del av den nödvändiga " "infrastrukturen är en symbolisk länk från /etc/resolv.conf till /run/" "resolvconf/resolv.conf. Om du godkänner kommer denna länk att skapas. Den " "existerande filen /etc/resolv.conf kommer att behållas som /etc/resolvconf/" "resolv.conf.d/original; den kommer att återställas om detta paket tas bort." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Negativt svar vid detta alternativ kommer att förhindra framtida " "installationer från att skapa symboliska länkar och därmed kan inte " "inställningsfilen uppdateras dynamiskt. Dynamiska uppdateringar kan " "återaktiveras genom att följa instruktionen i README-filen." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Närvaron av resolvconf kan påverka hur andra program uppträder så programmet " "ska inte finnas installerat utan att vara konfigurerat." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Omstart rekomenderas" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Programmet resolvconf ska få information namnserverinformation från " "gränssnittskonfiguratorer och lokala namncacheservrar. Trots att " "installationen av paketet resolvconf säger till dem att dela med sig av sin " "information så finns det vissa som inte gör detta." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Detta fel innebär att namnserverinformation vid installation av paketet " "resolvconf om inte följande lösning används för att gå runt problemet; " "resolvconf tar med sig all information från /etc/resolv.conf till databasen " "fram tills omstart av systemet. Detta är innebär i förlängningen att " "namnserverinformation som sparas undan finns kvar även om gränssnittet som " "det är associerat med avaktiveras. (Detta beteende bedöms mindre skadligt än " "att korrekt information försvinner.)" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Så länge felet ifråga finns kvar och speciallösningen inte tagits bort är " "enda sättet att säkerställa att resolvconf har rätt namnserverinformation " "efter installationen av resolvconfpaketet i ett körande system att starta om " "systemet." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "När paketet resolvconf togs bort kan information om namnserverar ha gått " "förlorad. För att korrigera detta problem bör systemet startas om." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Lägg till originalfil till dynamisk fil?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Om den vanliga statiska uppslagningskonfigurationen (vanligen /etc/resolv." "conf) innehåller adresser för namnservrar ska dessa flyttas till /etc/" "network/interfaces, raderna ska ha prefixen \"dns-nameservers\". Läs mer i " "manualsidan resolvconf(8) och README-filen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Så länge /etc/network/interfaces inte har ändrats och de påverkade " "gränssnitten stoppats och startats kommer namnservrarnas adresser inte att " "inkluderas i den dynamiskt skapade uppslagsningskonfigurationen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Om du väljer detta alternativ så kommer en temporär omväg att skapas, en " "symbolisk länk placeras i /etc/resolvconf/resolv.conf.d/tail och den pekar " "på /etc/resolvconf/resolv.conf.d/original. Detta kommer medföra att hela den " "ursprungliga uppslagningskonfigurationen läggs till sist i den dynamiskt " "skapade filen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Efter du har modifierat /etc/network/interfaces och lagt till raderna för " "\"dns-nameservers\" som krävs bör du peka en symbolisk länk från /etc/" "resolvconf/resolv.conf.d/tail till /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/vi.po0000644000000000000000000002113012062416774014667 0ustar # Vietnamese translation of resolvconf debconf templates # Copyright (C) 2005-2008 Clytie Siddall # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.39\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2008-02-12 22:24+1030\n" "Last-Translator: Clytie Siddall \n" "Language-Team: Vietnamese \n" "Language: vi\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: LocFactoryEditor 1.7b3\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Chuẩn bị tập tin « /etc/resolv.conf » để cập nhật động không?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Gói resolveconf chứa cơ sở hạ tầng cần thiết để cập nhật động tập tin cấu " "hình của phần mềm giải quyết. Một phần của cơ sở hạ tầng cần thiết là một " "liên kết tượng trưng từ « /etc/resolv.conf » đến « /run/resolvconf/resolv." "conf ». Bật tùy chọn này thì liên kết này sẽ được tạo; tập tin « /etc/resolv." "conf » đã tồn tại sẽ được bảo tồn dưới dạng « /etc/resolvconf/resolv.conf.d/" "original » và sẽ cũng được phục hồi nếu gói này bị gỡ bỏ." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Tắt tùy chọn này thì ngăn cản bản cài đặt tương lại tạo liên kết tượng " "trưng, do đó tập tin cấu hình phần mềm giải quyết sẽ không được cập nhật " "động. Tuy nhiên, vẫn còn có thể kích hoạt chức năng cập nhật đông tùy theo " "hướng dẫn trong tập tin Đọc Đi (README)." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Sự có mặt của resolvconf có thể ảnh hưởng đến ứng xử của các chương trình " "khác, vì vậy bạn không nên để lại bản cài đặt của nó nếu nó chưa được cấu " "hình." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Phụ thêm tập tin gốc vào tập tin động không?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Nếu tập tin cấu hình phần mềm giải quyết tĩnh gốc (/etc/resolv.conf) chứa " "địa chỉ của máy phục vụ tên thì các tên đó nên được liệt kê theo dòng « dns-" "nameservers » trong tập tin « /etc/network/interfaces ». Để tìm thêm thông " "tin, xem trang hướng dẫn (man) resolvconf(8) và tập tin Đọc Đi (README)." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Đến khi tập tin « /etc/network/interfaces » đã được chỉnh sửa, và các giao " "diện bị ảnh hưởng được tắt rồi bật lại, những địa chỉ máy phục vụ tên sẽ " "không được liệt kê trong tập tin cấu hình phần mềm giải quyết được tạo động." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Bật tùy chọn này thì dùng một sự khắc phục tạm thời: một liên kết tượng " "trưng sẽ được tạo (nếu chưa có) từ tập tin « /etc/resolvconf/resolv.conf.d/" "tail » đến tập tin « /etc/resolvconf/resolv.conf.d/original ». Liên kết này " "sẽ gây ra phụ thêm toàn bộ tập tin cấu hình phần mềm giải quyết gốc vào tập " "tin được tạo ra động." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Sau khi các dòng « dns-nameservers » cần thiết đã được thêm vào tập tin « /" "etc/network/interfaces », liên kết « /etc/resolvconf/resolv.conf.d/tail » " "nên bị thay thế bằng một liên kết tới « /dev/null »." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/de.po0000644000000000000000000002272212062416774014651 0ustar # German translation of resolvconf debconf templates # Copyright (C) 2004, 2008, 2011 Helge Kreutzmann # This file is distributed under the same license as the resolvconf package. # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.55\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-04 15:47+0200\n" "Last-Translator: Helge Kreutzmann \n" "Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ISO-8859-15\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "/etc/resolv.conf fr dynamische Aktualisierungen vorbereiten?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Das Paket Resolvconf enthlt die fr das dynamische Aktualisieren der " "Resolver-Konfigurationsdatei bentigte Infrastruktur. Teil der notwendigen " "Infrastruktur ist ein symbolischer Link von /etc/resolv.conf auf /run/" "resolvconf/resolv.conf. Falls Sie diese Option whlen, wird dieser Link " "angelegt. Die bestehende /etc/resolv.conf-Datei wird als /etc/resolvconf/" "resolv.conf.d/original erhalten; sie wird wiederhergestellt, falls dieses " "Paket entfernt wird." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Falls Sie diese Option ablehnen, werden zuknftige Installationen daran " "gehindert, diesen Link neu zu erstellen und die Konfigurationsdatei des " "Resolvers (Namensauflsers) wird somit nicht dynamisch aktualisiert. In der " "Datei README wird beschrieben, wie das dynamische Aktualisieren aktiviert " "werden kann." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Die Anwesenheit von Resolvconf kann das Verhalten anderer Programme " "beeinflussen, daher sollte es im unkonfigurierten Zustand nicht installiert " "bleiben." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Systemneustart empfohlen" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Anbieter von Name-Server-Informationen wie lokale, zwischenspeichernde Name-" "Server und Schnittstellenkonfiguratoren sollten dem Resolvconf-Programm Name-" "Server-Informationen bereitstellen. Obwohl die Installation des Pakets " "Resolvconf die Bereitstellung der Informationen auslst, schlgt dies bei " "einigen fehl." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Dieser Fehler wrde zum Verlust gltiger Name-Server-Information bei der " "Installation des Pakets Resolvconf fhren, falls die folgende " "Hilfskonstruktion nicht eingesetzt wrde: Resolvconf enthlt den gesamten " "Inhalt von /etc/resolv.conf im Zustand vor der Installation bis zum " "Systemneustart. Dies hat den Nachteil, dass die Name-Server-Information " "beibehalten wird, selbst wenn die Konfiguration der zugehrige Schnittstelle " "spter entfernt wird. (Dieses inkorrekte Verhalten wird als weniger " "schdlich als die Alternative des Verlusts gltiger Information angesehen)." #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Bis der besagte Fehler behoben ist und die Hilfskonstruktion entfernt wurde, " "ist die einzige Methode, um sicherzustellen, dass Resolvconf ber komplett " "korrekte Name-Server-Informationen verfgt, nachdem das Paket auf einem " "laufenden System installiert wurde, der Neustart des Systems." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Die Entfernung des Pakets resolvconf knnte dazu gefhrt haben, dass einige " "Informationen ber Name-Server nicht mehr verfgbar sind. Um dieses Problem " "zu beheben, wird ein Neustart des Systems empfohlen." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Die ursprngliche Datei an die dynamische Datei anhngen?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Falls die ursprngliche statische Resolver-Konfigurationsdatei (/etc/resolv." "conf) Nameserver-Adressen enthielt, sollten diese Adressen auf dns-" "nameservers-Zeilen in /etc/network/interfaces aufgefhrt werden. Fr " "weitere Informationen lesen Sie die Handbuchseite resolvconf(8) und die " "README-Datei." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Bis /etc/network/interfaces bearbeitet und die betroffenen Schnittstellen " "herunter- und wieder heraufgefahren wurden, wird die Adresse des Nameservers " "nicht in die dynamisch erstellte Resolver-Konfigurationsdatei aufgenommen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Falls Sie diese Option whlen, wird eine vorbergehende provisorische Lsung " "realisiert: Ein symbolischer Link von /etc/resolvconf/resolv.conf.d/tail " "nach /etc/resolvconf/resolv.conf.d/original wird erstellt (falls er nicht " "bereits existiert). Damit wird die gesamte ursprngliche Konfigurationsdatei " "des Resolvers an die dynamisch generierte Datei angehngt." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Nachdem bentigte dns-nameservers-Zeilen zu /etc/network/interfaces " "hinzugefgt wurden, sollte der symbolische Link von /etc/resolvconf/resolv." "conf.d/tail auf /dev/null gendert werden." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/po/da.po0000644000000000000000000002236512062416774014650 0ustar # Danish translation of resolvconf debconf templates # Copyright (C) 2011 Joe Hansen # This file is distributed under the same license as the resolvconf package. # # resolver -> klarlægger # msgid "" msgstr "" "Project-Id-Version: resolvconf 1.56\n" "Report-Msgid-Bugs-To: resolvconf@packages.debian.org\n" "POT-Creation-Date: 2012-05-02 12:49-0700\n" "PO-Revision-Date: 2011-06-12 17:30+01:00\n" "Last-Translator: Joe Hansen \n" "Language-Team: Danish \n" "Language: da\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Prepare /etc/resolv.conf for dynamic updates?" msgstr "Forbered /etc/resolv.conf for dynamiske opdateringer?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "The resolvconf package contains the infrastructure required for dynamic " "updating of the resolver configuration file. Part of the necessary " "infrastructure is a symbolic link from /etc/resolv.conf to /run/resolvconf/" "resolv.conf. If you choose this option then this link will be created; the " "existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv." "conf.d/original, and will be restored if this package is removed." msgstr "" "Pakken resolvconf indeholder infrastrukturen krævet for dynamisk opdatering " "af klarlæggerkonfigurationsfilen (»resolver«). En del af den nødvendige " "infrastruktur er en symbolsk henvisning fra /etc/resolv.conf til /run/" "resolvconf/resolv.conf. Hvis du vælger denne indstilling, vil denne " "henvisning blive oprettet; den eksisterende /etc/resolv.conf- fil vil blive " "bevaret som /etc/resolvconf/resolv.conf.d/original og vil blive gendannet, " "hvis pakken fjernes." #. Type: boolean #. Description #: ../templates:2001 msgid "" "Declining this option will prevent future installations from recreating the " "symbolic link and therefore the resolver configuration file will not be " "dynamically updated. Dynamic updating can then be activated following " "instructions in the README file." msgstr "" "Afslag af denne indstilling vil forhindre fremtidige installationer fra at " "genskabe den symbolske henvisning og derfor vil " "klarlæggerkonfigurationsfilen ikke blive dynamsik opdateret. Dynamisk " "opdatering kan så aktiveres ved at følge instruktionerne i README-filen." #. Type: boolean #. Description #: ../templates:2001 msgid "" "The presence of resolvconf can affect the behavior of other programs, so it " "should not be left installed if unconfigured." msgstr "" "Tilstedeværelsen af resolvconf kan påvirke opførelsen af andre programmer, " "så den bør ikke være installeret uden at være konfigureret." #. Type: note #. Description #. Type: note #. Description #: ../templates:3001 ../templates:4001 msgid "Reboot recommended" msgstr "Genstart anbefales" #. Type: note #. Description #: ../templates:3001 msgid "" "Suppliers of name server information such as local caching name servers and " "interface configurers are expected to supply name server information to the " "resolvconf program. However, although installation of the resolvconf package " "triggers them to supply their information, some of them fail to do so." msgstr "" "Leverandører af navneserverinformation såsom lokale navneservere for " "mellemlageret (caching) og opsættere af brugerflader forventes at angive " "navneserverinformation til resolvconf-programmet. Selvom installationen af " "pakken resolvconf beder dem om at angive deres informationer så fejler nogle " "af dem med hensyn til denne opgave." #. Type: note #. Description #: ../templates:3001 msgid "" "This bug would lead to loss of valid name server information on installation " "of the resolvconf package if the following workaround were not adopted: " "resolvconf includes the full contents of the pre-installation /etc/resolv." "conf in its database until reboot. This has the drawback that name server " "information is retained even if the associated interface is later " "deconfigured. (This incorrect behavior is judged to be less harmful than the " "alternative of losing valid information.)" msgstr "" "Denne fejl vil føre til tab af gyldig navneserverinformation ved " "installation af pakken resolvconf, hvis den følgende omgåelse ikke blev " "indarbejdet: resolvconf inkluderer det fulde indhold af den præinstallerede /" "etc/resolv.conf i sin database indtil genstart. Dette har den ulempe, at " "navneserverinformation bevares selv om den associerede brugerflade senere " "dekonfigureres. (Denne forkerte opførsel er bedømt til at være mindre " "skadelig end alternativet, der kan medføre tab af valid information.)" #. Type: note #. Description #: ../templates:3001 msgid "" "Until the bug in question is fixed and the workaround removed, the only way " "to ensure that resolvconf has fully correct name server information after " "the resolvconf package has been installed on a running system is to reboot " "the system." msgstr "" "Indtil den omtalte fejl er rettet og omgåelsen fjernet er den eneste måde at " "sikre sig, at resolvconf har fuld korrekt navneserverinformation, efter at " "pakken resolvconf er blevet installeret på et kørende system, at genstarte " "systemet." #. Type: note #. Description #: ../templates:4001 msgid "" "The removal of the resolvconf package may have resulted in some information " "about name servers becoming unavailable. To correct this problem it is " "recommended that the system be rebooted." msgstr "" "Fjernelsen af pakken resolvconf kan have medført, at information om " "navneservere er blevet utilgængelig. For at rette dette problem anbefales " "det, at systemet genstartes." #. Type: boolean #. Description #: ../templates:5001 msgid "Append original file to dynamic file?" msgstr "Tilføj oprindelig fil til dynamisk fil?" #. Type: boolean #. Description #: ../templates:5001 msgid "" "If the original static resolver configuration file (/etc/resolv.conf) " "contains name server addresses, those addresses should be listed on \"dns-" "nameservers\" lines in /etc/network/interfaces. For more information, please " "consult the resolvconf(8) man page and the README file." msgstr "" "Hvis den oprindelige statiske klarlæggerkonfigurationsfil (/etc/resolv.conf) " "indeholder adresser for navneservere, så bør disse adresser være anført på " "»dns-nameservers«-linjer i /etc/network/interfaces. For yderligere " "information så konsulter venligst manualsiden resolvconf(8) og README-filen." #. Type: boolean #. Description #: ../templates:5001 msgid "" "Until /etc/network/interfaces has been edited and the affected interfaces " "brought down and up again, the name server addresses will not be included in " "the dynamically generated resolver configuration file." msgstr "" "Indtil /etc/network/interfaces er blevet redigeret og de påvirkede " "grænseflader bragt ned og op igen, vil navneserveradresserne ikke være " "inkluderet i den dynamisk oprettede klarlæggerkonfigurationsfil." #. Type: boolean #. Description #: ../templates:5001 msgid "" "If you choose this option, a temporary workaround will be put in place: a " "symbolic link will be created (if it does not already exist) from /etc/" "resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. " "This will cause the whole of that original resolver configuration file to be " "appended to the dynamically generated file." msgstr "" "Hvis du vælger denne indstilling, vil en midlertidig omgåelse blive " "igangsat: En symbolsk henvisning vil blive oprettet (hvis den ikke allerede " "findes) fra /etc/resolvconf/resolv.conf.d/tail til /etc/resolvconf/resolv." "conf.d/original. Dette vil medføre, at hele den oprindelige " "klarlæggerkonfigurationsfil vil blive tilføjet til den dynamisk oprettede " "fil." #. Type: boolean #. Description #: ../templates:5001 msgid "" "After the required \"dns-nameservers\" lines have been added to /etc/network/" "interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced " "by one to /dev/null." msgstr "" "Efter de krævede »dns-nameservers«-linjer er blevet tilføjet til /etc/" "network/interfaces, bør henvisningen /etc/resolvconf/resolv.conf.d/tail " "erstattes med en i /dev/null." #. Type: error #. Description #: ../templates:6001 msgid "Removing immutable filesystem bit from /etc/resolv.conf" msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The file /etc/resolv.conf was marked immutable on the filesystem with the " "'chattr' command. You may have done this to avoid the file being managed by " "NetworkManager in the past. In Ubuntu 12.04 and above, this file is managed " "by resolvconf in order to correctly support dynamic sources of DNS " "information." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "The immutable flag on /etc/resolv.conf will be removed now, and the current " "file will be moved to /etc/resolvconf/resolv.conf.d/original. If the " "original file contained static resolver configuration, it is recommended " "that you copy the file to /etc/resolvconf/resolv.conf.d/head." msgstr "" #. Type: error #. Description #: ../templates:6001 msgid "" "After upgrade you may remove the /etc/resolv.conf symlink and restore the " "original contents of this file, but this is not recommended." msgstr "" resolvconf-1.69ubuntu1/debian/prerm0000755000000000000000000000053012062416774014347 0ustar #!/bin/sh set -e case "$1" in remove) resolvconf --disable-updates || : ;; # deconfigure) # This code path should not be used. # N.B.: Other packages should not declare "Breaks: resolvconf"; # they should declare "Conflicts: resolvconf" instead. # ;; # upgrade|failed-upgrade) # Don't do anything # ;; esac #DEBHELPER# exit 0 resolvconf-1.69ubuntu1/debian/test-normalization0000755000000000000000000001000112062416774017057 0ustar #!/bin/sh ### BEGIN FUNCTION COPIED FROM THE resolvconf SCRIPT ### # # Echo stdin with: # comments removed; # initial and terminal whitespace removed; # whitespace strings replaced by single blanks; # leading zeroes removed from nameserver address fields; # first set of zero fields in an IPv6 address collapsed to '::'; # empty lines removed. normalized_stdin() { sed \ -e 's/#.*$//' \ -e 's/[[:blank:]]\+$//' \ -e 's/^[[:blank:]]\+//' \ -e 's/[[:blank:]]\+/ /g' \ -e '/^nameserver/!b ENDOFCYCLE' \ -e 's/$/ /' \ -e 's/\([:. ]\)0\+/\10/g' \ -e 's/\([:. ]\)0\([123456789abcdefABCDEF][[:xdigit:]]*\)/\1\2/g' \ -e '/::/b ENDOFCYCLE; s/ \(0[: ]\)\+/ ::/' \ -e '/::/b ENDOFCYCLE; s/:\(0[: ]\)\+/::/' \ -e ': ENDOFCYCLE' \ - | \ sed \ -e 's/[[:blank:]]\+$//' \ -e '/^$/d' } ### END FUNCTION COPIED FROM THE resolvconf SCRIPT ### test_result() { [ "$1" = "$2" ] || { echo "Normalization test failed: actual '$1' != '$2' expected" ; exit 1 ; } } test_result "$(echo "" | normalized_stdin)" "" test_result "$(echo " " | normalized_stdin)" "" test_result "$(echo "nameserver 127.0.0.1" | normalized_stdin)" "nameserver 127.0.0.1" test_result "$(echo " nameserver 127.0.0.1 # foo " | normalized_stdin)" "nameserver 127.0.0.1" test_result "$(echo "nameserver 127.000.000.1" | normalized_stdin)" "nameserver 127.0.0.1" test_result "$(echo "nameserver 127.000.000.1" | normalized_stdin)" "nameserver 127.0.0.1" test_result "$(echo "nameserver ::1" | normalized_stdin)" "nameserver ::1" test_result "$(echo " nameserver ::1 # foo " | normalized_stdin)" "nameserver ::1" test_result "$(echo "nameserver 0:0:0:0:0:0:0:1" | normalized_stdin)" "nameserver ::1" test_result "$(echo " nameserver 0:0:0:0:0:0:0:1 # foo " | normalized_stdin)" "nameserver ::1" test_result "$(echo "nameserver 00:000:0:0000:0001" | normalized_stdin)" "nameserver ::1" test_result "$(echo " nameserver 00:000:0:0000:0001" | normalized_stdin)" "nameserver ::1" test_result "$(echo "nameserver 003:1020:0105:55:0000:1000:0000:0000" | normalized_stdin)" "nameserver 3:1020:105:55::1000:0:0" test_result "$(echo " nameserver 003:1020:0105:55:0000:1000:0000:0000" | normalized_stdin)" "nameserver 3:1020:105:55::1000:0:0" test_result "$(echo "nameserver 30:1020:0105:55:0500:1000:0000:0000" | normalized_stdin)" "nameserver 30:1020:105:55:500:1000::" test_result "$(echo " nameserver 30:1020:0105:55:0500:1000:0000:0000" | normalized_stdin)" "nameserver 30:1020:105:55:500:1000::" test_result "$(echo \ "#foo nameserver 30:1020:0105:55:0500:1000:0000:0000 nameserver ::1 nameserver 0000::1 # foo nameserver bwaa haa nameserver 0005::1 # foo bar nameserver 003:1020:0105:55:0000:1000:0000:0000 options nameserver anotherthing 1:2 03::4::0005 # Don't touch non-nameservers lines nameserver 127.0.0.1 #foo bar nameserver 0:0:00:0000000:0:0:0:1 bar search yoyodyne.biz yyy.xxx baz # foo " | normalized_stdin)" \ "nameserver 30:1020:105:55:500:1000:: nameserver ::1 nameserver 0::1 nameserver 5::1 nameserver 3:1020:105:55::1000:0:0 options nameserver anotherthing 1:2 03::4::0005 nameserver 127.0.0.1 nameserver ::1 bar search yoyodyne.biz yyy.xxx baz" # Check that we are actually testing something ( test_result "$(echo "nameserver 127.0.0.1" | normalized_stdin)" "bogusstring" ) > /dev/null [ "$?" = 1 ] || { echo "Normalization test script contains a programming error." ; exit 2 ; } echo "Normalization test passed." exit 0 resolvconf-1.69ubuntu1/debian/resolvconf.000resolvconf.ppp.ip-down0000755000000000000000000000074612062416774022164 0ustar #!/bin/sh # # PPP down hook script for resolvconf # # Reconfigures resolver to take into account # the disappearance of the ppp interface. # # This file is part of the resolvconf package. # [ -x /sbin/resolvconf ] || exit 0 /sbin/resolvconf -d "$PPP_IFACE" # Old name. Remove this line after next upgrade horizon. case "$6" in nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*) # NetworkManager handles it exit 0 ;; esac /sbin/resolvconf -d "${PPP_IFACE}.pppd" resolvconf-1.69ubuntu1/debian/NOTES0000644000000000000000000000327012076274066014114 0ustar MAINTAINER NOTES for resolvconf TODO ---- * File bug reports against all packages containing suppliers of nameserver information, asking each to add a resolvconf packaging-event hook script. Submitted: * #628003, #641717 dnsmasq [both DONE] * #628846 pdnsd * #641714 bind9 * #639803 network-manager To be submitted: * (nameservers:) pdns-recursor, totd + Easy to implement: just call initscript or add 127.0.0.1. * (DHCP clients:) isc-dhcp-client, dhcpcd, pump, udhcpc + Probably easiest and best to trigger DHCP lease renewals. * After the first Debian release to include an ifupdown that supports duplicated options in a stanza (not 0.7.5, despite a changelog entry implying otherwise, and thus not wheezy), document the fact that the option "dns-nameserver" can be given multiple times in a stanza. awk --- We mustn't use awk in any runtime code but we may use it in the maintainer scripts where convenient. piuparts -------- * Reports: ERROR: FAIL: After purging files have been modified: /etc/resolv.conf not owned but this is not a bug, since resolvconf can justifiably modify that file, which isn't an ordinary configuration file. Loop dangers ------------ Remember the interesting fact that postinst runs dpkg-event.d/foo which probably runs /sbin/resolvconf which probably runs update.d/foo. Things one tends to forget -------------------------- Remember to run debconf-updatepo after changing a template or po file. Famous quotations ----------------- As Ian Jackson says (http://lists.debian.org/debian-dpkg/2008/03/msg00091.html) > OH FOR FUCK'S SAKE WHAT DOES IT TAKE TO GET SOMETHING DONE AROUND HERE? resolvconf-1.69ubuntu1/debian/config0000644000000000000000000000226212062416774014470 0ustar #!/bin/sh set -e . /usr/share/debconf/confmodule db_input low resolvconf/linkify-resolvconf || : db_go db_get resolvconf/linkify-resolvconf # No need to ask about creating a 'tail' file if we've already asked # or if /etc/resolv.conf is already a symlink; this is only for initial # install. if [ "$RET" = true ] && db_fget resolvconf/link-tail-to-original seen \ && [ "$RET" = false ] && ! [ -L /etc/resolv.conf ] then if ! grep -q nameserver /etc/resolv.conf 2>/dev/null \ || grep -q '# Generated by NetworkManager' /etc/resolv.conf 2>/dev/null \ || grep -Eq '^[[:space:]]*(iface[[:space:]]+.*[[:space:]]+inet6?[[:space:]]+dhcp|dns[-_]nameservers[[:space:]]+[0-9A-Fa-f.:[:space:]]+[[:space:]]*(#.*)?$)' /etc/network/interfaces 2>/dev/null then # Either the /etc/resolv.conf is empty, or we've found # at least one indicator that it's dynamically managed # in at least some circumstances (via ifupdown dhcp, # ifupdown 'dns-nameserver' static rules, or NM). No point # in importing the existing nameservers. db_set resolvconf/link-tail-to-original false fi db_input low resolvconf/link-tail-to-original || : fi db_input medium resolvconf/downup-interfaces || : db_go resolvconf-1.69ubuntu1/debian/compat0000644000000000000000000000000212062416774014474 0ustar 8 resolvconf-1.69ubuntu1/debian/preinst0000755000000000000000000000365012062416774014714 0ustar #!/bin/sh set -e MYNAME=resolvconf.preinst report() { echo "${MYNAME}: $*" ; } report_warn() { report "Warning: $*" >&2 ; } report_info() { report "$*" >&2 ; } is_installed() { # Same function in preinst, postinst, postrm [ "$1" ] || return 1 dpkg-query -W -f='${Status}\n' "$1" 2>/dev/null | grep -siq '^[[:alpha:]]\+ [[:alpha:]]\+ installed$' >/dev/null 2>&1 } ### Create run-time directories ### # # We create the run-time directories here, in the preinst, so that even if # resolvconf is run before the postinst runs there is nevertheless a place # for resolvconf to store data. The latter can occur if resolvconf # is installed simultaneously with a caching nameserver package whose # postinst runs resolvconf to add its IP address. # case "$1" in install|upgrade) # Ensure that /run/resolvconf/interface exists. mkdir -p /run/resolvconf/interface # Ensure that /etc/resolvconf exists. mkdir -p /etc/resolvconf ;; # abort-upgrade) # Don't do anything because we don't anything in the postrm on upgrade or on failed-upgrade # ;; esac ### Prepare to notify already configured packages of our installation ### case "$1" in install) # Create list of packages that might need to be notified of the installation of resolvconf if [ -d /usr/lib/resolvconf/dpkg-event.d ] ; then NOTIFICATION_HOOK_SCRIPTS="$(cd /usr/lib/resolvconf/dpkg-event.d >/dev/null ; run-parts --test .)" PACKAGES_TO_NOTIFY="" for SCRPT in $NOTIFICATION_HOOK_SCRIPTS ; do PKG="${SCRPT#./}" if is_installed "$PKG" ; then PACKAGES_TO_NOTIFY="${PACKAGES_TO_NOTIFY:+$PACKAGES_TO_NOTIFY }$PKG" fi done rm -f /run/resolvconf/packages-to-notify if [ "$PACKAGES_TO_NOTIFY" ] ; then echo "$PACKAGES_TO_NOTIFY" > /run/resolvconf/packages-to-notify fi fi ;; # upgrade) # Don't do anything # ;; # abort-upgrade) # Don't do anything because we don't anything in the postrm on upgrade or on failed-upgrade # ;; esac #DEBHELPER# exit 0 resolvconf-1.69ubuntu1/debian/resolvconf.init0000755000000000000000000000554612062416774016360 0ustar #!/bin/sh # ### BEGIN INIT INFO # Provides: resolvconf # Required-Start: $local_fs # Required-Stop: $local_fs # X-Start-Before: networking ifupdown # Default-Start: S # Default-Stop: 0 6 # Short-Description: Nameserver information manager # Description: This service manages the list of nameserver addresses # used by the libc resolver and name service caches ### END INIT INFO # # This file is part of the resolvconf package. # # We really need "X-Stop-Before: networking ifupdown" too because # terminal ifdowns shouldn't update resolv.conf; # however there is unfortunately no such thing as "X-Stop-Before". # # This file is not used in Ubuntu. # # Don't use set -e; check return status instead. [ -x /sbin/resolvconf ] || exit 0 PATH=/sbin:/bin . /lib/lsb/init-functions # $1 EXITSTATUS # [$2 MESSAGE] log_action_end_msg_and_exit() { log_action_end_msg "$1" ${2:+"$2"} exit $1 } case "$1" in start) # The "start" method should only be used at boot time. # Don't run this on package upgrade, for example. log_action_begin_msg "Setting up resolvconf" # Wipe runtime directories in case they aren't on a tmpfs resolvconf --wipe-runtime-directories || log_action_end_msg_and_exit 1 "failed to delete the old contents of run-time directories" # Create runtime directories in case they are on a tmpfs resolvconf --create-runtime-directories || log_action_end_msg_and_exit 1 "failed to create run-time directories" # Request a postponed update (needed in case the base file has content). resolvconf -u || log_action_end_msg_and_exit 1 "failed requesting update" # Enable updates and perform the postponed update. resolvconf --enable-updates || log_action_end_msg_and_exit 1 "failed to enable updates" log_action_end_msg_and_exit 0 ;; stop) # The "stop" method should only be used at shutdown time. log_action_begin_msg "Stopping resolvconf" resolvconf --disable-updates || log_action_end_msg_and_exit 1 "failed to disable updates" log_action_end_msg_and_exit 0 ;; restart) log_action_begin_msg "Restarting resolvconf" resolvconf --enable-updates || log_action_end_msg_and_exit 1 "failed to enable updates" log_action_end_msg_and_exit 0 ;; reload|force-reload) resolvconf -u || log_action_end_msg_and_exit 1 "failed to update" exit 0 ;; enable-updates) resolvconf --enable-updates || log_action_end_msg_and_exit 1 "failed to enable updates" exit 0 ;; disable-updates) resolvconf --disable-updates || log_action_end_msg_and_exit 1 "failed to disable updates" exit 0 ;; status) if resolvconf --updates-are-enabled ; then log_success_msg "resolvconf updates are enabled" else log_failure_msg "resolvconf updates are disabled" fi exit 0 ;; *) echo "Usage: /etc/init.d/resolvconf {start|stop|restart|reload|force-reload|enable-updates|disable-updates|status}" >&2 exit 3 ;; esac # Don't reach here exit 99 resolvconf-1.69ubuntu1/debian/resolvconf.000resolvconf.if-up0000755000000000000000000000104512076274066021023 0ustar #!/bin/sh # # ifup hook script for resolvconf # # This file is part of the resolvconf package. # [ -x /sbin/resolvconf ] || exit 0 case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac R="" if [ "$IF_DNS_DOMAIN" ] ; then R="${R}domain $IF_DNS_DOMAIN " fi if [ "$IF_DNS_SEARCH" ] ; then R="${R}search $IF_DNS_SEARCH " fi if [ "$IF_DNS_SORTLIST" ] ; then R="${R}sortlist $IF_DNS_SORTLIST " fi for NS in $IF_DNS_NAMESERVER $IF_DNS_NAMESERVERS ; do R="${R}nameserver $NS " done echo -n "$R" | /sbin/resolvconf -a "${IFACE}.${ADDRFAM}" || : resolvconf-1.69ubuntu1/debian/rules0000755000000000000000000000177512062416774014370 0ustar #!/usr/bin/make -f # This script uses debhelper by Joey Hess export DH_VERBOSE=1 # enables magic below export DH_OPTIONS DESTDIR=debian/resolvconf clean: dh_testdir dh_testroot dh_clean build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp build-stamp: debian/test-normalization dh_testdir binary-arch: binary-indep: build dh_testroot dh_installdirs etc sbin lib/resolvconf etc/network/if-up.d etc/network/if-down.d cp -a etc $(DESTDIR) install -p --owner=root --group=root --mode=0755 bin/resolvconf $(DESTDIR)/sbin install -p --owner=root --group=root --mode=0755 bin/list-records $(DESTDIR)/lib/resolvconf dh_installdebconf dh_lintian dh_installdocs README dh_installman dh_installchangelogs dh_installinit -r dh_installppp --name=000resolvconf dh_installifupdown --name=resolvconf dh_installifupdown --name=000resolvconf dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb binary: binary-indep .PHONY: build clean binary-indep binary resolvconf-1.69ubuntu1/debian/docs0000644000000000000000000000003612062416774014150 0ustar debian/resolvconf-update-bind resolvconf-1.69ubuntu1/debian/source/0000755000000000000000000000000012076277005014573 5ustar resolvconf-1.69ubuntu1/debian/source/format0000644000000000000000000000001512062416774016005 0ustar 3.0 (native) resolvconf-1.69ubuntu1/etc/0000755000000000000000000000000012076277005012624 5ustar resolvconf-1.69ubuntu1/etc/resolvconf/0000755000000000000000000000000012076277005015004 5ustar resolvconf-1.69ubuntu1/etc/resolvconf/update.d/0000755000000000000000000000000012076277005016510 5ustar resolvconf-1.69ubuntu1/etc/resolvconf/update.d/dnscache0000755000000000000000000000612412062416774020214 0ustar #!/bin/sh # # Script to update every forwarding djbdns dnscache instance running # on the local machine # # this script sets up every FORWARDONLY dnscache managed by either # daemontools or runit on this machine to use the dynamically-offered # nameservers for the default '@' # # Assumption: On entry, PWD contains the resolv.conf-type files # # If no nameservers are offered, we ask the dnscache instances to fall # back to the root nameservers listed in /etc/dnsroots.global # # Licensed under the GNU GPL. See /usr/share/doc/resolvconf/copyright. # # Written by Daniel Kahn Gillmor # based on similar scripts by Thomas Hood set -e PATH=/usr/sbin:/usr/bin:/sbin:/bin [ -x /usr/bin/dnscache ] || exit 0 [ -x /lib/resolvconf/list-records ] || exit 1 ETC=/etc TMPFILE="/run/resolvconf/dnscache_new.$$" DEFAULTROOTS="${ETC}/dnsroots.global" CACHES="" # Which directories do we scan? # /var/lib/svscan: daemontools, built "the debian way" (LFS-compliant) # /service: daemontools, built "the djb way" # /var/service: runit for SERVICEDIR in /var/lib/svscan /service /etc/service ; do # We'll only manage caches actually managed by daemontools or runit. if [ -d "$SERVICEDIR" ] ; then OLDCWD=`pwd` cd "$SERVICEDIR" for SVC in * ; do SVC="$SERVICEDIR/$SVC" if \ [ -d "$SVC" ] \ && [ -f "$SVC/run" ] \ && [ ! -f "$SVC/down" ] \ && [ -d "$SVC/root" ] \ && [ -d "$SVC/root/servers" ] \ && [ -d "$SVC/root/ip" ] \ && [ -s "$SVC/env/FORWARDONLY" ] \ && grep -q dnscache "$SVC/run" then CACHES="$SVC $CACHES" fi done cd "$OLDCWD" fi done # Stores arguments (minus duplicates) in RSLT, separated by spaces # Doesn't work properly if an argument itself contain whitespace uniquify() { RSLT="" while [ "$1" ] ; do for E in $RSLT ; do [ "$1" = "$E" ] && { shift ; continue 2 ; } done RSLT="${RSLT:+$RSLT }$1" shift done } RSLVCNFFILES="$(/lib/resolvconf/list-records)" ### Compile list of nameservers ### NMSRVRS="" if [ "$RSLVCNFFILES" ] ; then uniquify $(sed -n 's/^[[:space:]]*nameserver[[:space:]]\+//p' $RSLVCNFFILES) NMSRVRS="$RSLT" fi clean_up() { rm -f "$TMPFILE" ; } trap clean_up EXIT clean_up # If no nameservers were present, use the default root nameservers # provided by the djbdns package: if [ -z "$NMSRVRS" ] && [ -e "$DEFAULTROOTS" ] ; then cp "$DEFAULTROOTS" "$TMPFILE" else : > "$TMPFILE" for N in $NMSRVRS ; do echo "$N" >> "$TMPFILE" done fi # svc is the daemontools service controller SVC_CMD="$(which svc)" || : [ ! "$SVC_CMD" ] && [ -x /command/svc ] && SVC_CMD=/command/svc # sv is the runit service controller SV_CMD="$(which sv)" || : for CACHE in $CACHES ; do cp "$TMPFILE" "$CACHE/root/servers/@" # Restart the cache if it's already running: if [ "$SV_CMD" ] && \ [ -e "$CACHE/supervise/pid" ] && \ [ -e "$CACHE/supervise/stat" ]; then # services managed by runit have supervise/{pid,stat} "$SV_CMD" restart "$CACHE" else # otherwise, it is probably managed by daemontools [ "$SVC_CMD" ] && "$SVC_CMD" -t "$CACHE" fi done resolvconf-1.69ubuntu1/etc/resolvconf/update.d/libc0000755000000000000000000001234712062416774017361 0ustar #!/bin/sh # # Script to update resolv.conf, the libc resolver configuration file, # and to notify users of the libc resolver of changes # # Assumption: On entry, PWD contains the resolv.conf-type files. # # This script is part of the resolvconf package. # # Set REPORT_ABSENT_SYMLINK=no to inhibit warning message that # /etc/resolv.conf is not a symbolic link # # Set TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no # to allow additional nameserver addresses to be listed in # resolv.conf after an initial loopback address 127.* or ::1. # set -e PATH=/sbin:/bin [ -x /lib/resolvconf/list-records ] || exit 1 # Default override [ -r /etc/default/resolvconf ] && . /etc/default/resolvconf ETC=/etc ETCRESOLVCONF="${ETC}/resolvconf" RESOLVCONFDIR="${ETCRESOLVCONF}/resolv.conf.d" BASEFILE="${RESOLVCONFDIR}/base" HEADFILE="${RESOLVCONFDIR}/head" TAILFILE="${RESOLVCONFDIR}/tail" DYNAMICRSLVCNFFILE="/run/resolvconf/resolv.conf" TMPFILE="${DYNAMICRSLVCNFFILE}_new.$$" # Set unset variables to their defaults if [ -z "$REPORT_ABSENT_SYMLINK" ] ; then # '..._ALTERED_...' is the old deprecated name for this variable if [ "$REPORT_ALTERED_SYMLINK" ] ; then REPORT_ABSENT_SYMLINK="$REPORT_ALTERED_SYMLINK" else # Set to default value REPORT_ABSENT_SYMLINK=y fi fi if [ -z "$TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS" ] ; then # '..._127' is the old deprecated name for this variable if [ "$TRUNCATE_NAMESERVER_LIST_AFTER_127" ] ; then TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS="$TRUNCATE_NAMESERVER_LIST_AFTER_127" else # Set to default value TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=y fi fi report_warning() { echo "$0: Warning: $*" >&2 ; } resolv_conf_is_symlinked_to_dynamic_file() { [ -L ${ETC}/resolv.conf ] && [ "$(readlink -m ${ETC}/resolv.conf)" = "$DYNAMICRSLVCNFFILE" ] } if ! resolv_conf_is_symlinked_to_dynamic_file ; then case "$REPORT_ABSENT_SYMLINK" in y|Y|yes|YES|Yes) report_warning "${ETC}/resolv.conf is not a symbolic link to $DYNAMICRSLVCNFFILE" ;; esac fi # Args are candidate items not containing spaces # Returns RSLT -- space-separated list of items without duplicates # # Stores arguments (minus duplicates) in RSLT, separated by spaces uniquify() { RSLT="" local D while [ "$1" ] ; do # Remove the root domain suffix D="${1%.}" for E in $RSLT ; do [ "$D" = "$E" ] && { shift ; continue 2 ; } done RSLT="${RSLT:+$RSLT }$D" shift done } # Args are candidate items not containing spaces # Returns NSMSRVS -- space-separate list of no more than 3 items, # without duplicates, # truncated after loopback address if TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS set affirmatively uniquify_nameserver_list() { NMSRVRS="" N=0 while [ "$1" ] ; do for E in $NMSRVRS ; do [ "$1" = "$E" ] && { shift ; continue 2 ; } done NMSRVRS="${NMSRVRS:+$NMSRVRS }$1" case "$TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS" in (y|Y|yes|YES|Yes) case "$1" in (127.*|::1) return 0 ;; esac ;; esac N=$(($N + 1)) [ "$N" = 3 ] && return 0 shift done } RSLVCNFFILES="$(/lib/resolvconf/list-records)" [ -f "$BASEFILE" ] && RSLVCNFFILES="$RSLVCNFFILES $BASEFILE" ### Compile list of nameservers ### NMSRVRS="" if [ "$RSLVCNFFILES" ] ; then uniquify_nameserver_list $(sed -n 's/^[[:space:]]*nameserver[[:space:]]\+//p' $RSLVCNFFILES) fi ### Compile search list ### SRCHS="" if [ "$RSLVCNFFILES" ] ; then uniquify $(sed -n 's/^[[:space:]]*\(\(search\)\|\(domain\)\)[[:space:]]\+//p' $RSLVCNFFILES) SRCHS="$RSLT" fi clean_up() { rm -f "$TMPFILE" ; } trap clean_up EXIT clean_up ### Make the file ### : > "$TMPFILE" [ -f "$HEADFILE" ] && cat "$HEADFILE" >> "$TMPFILE" for N in $NMSRVRS ; do echo "nameserver $N" >> "$TMPFILE" ; done [ "$SRCHS" ] && echo "search $SRCHS" >> "$TMPFILE" [ "$RSLVCNFFILES" ] && sed -e '/^[[:space:]]*$/d' -e '/^[[:space:]]*#/d' -e '/^[[:space:]]*\(\(nameserver\)\|\(search\)\|\(domain\)\)[[:space:]]/d' $RSLVCNFFILES >> "$TMPFILE" 2>/dev/null [ -f "$TAILFILE" ] && cat "$TAILFILE" >> "$TMPFILE" ### Put the file in place ### if [ -f "$DYNAMICRSLVCNFFILE" ] && [ "$(cat $TMPFILE)" = "$(cat $DYNAMICRSLVCNFFILE)" ] ; then # The file has not changed rm -f "$TMPFILE" exit 0 fi # The file has changed mv -f "$TMPFILE" "$DYNAMICRSLVCNFFILE" # Only notify users of /etc/resolv.conf if /etc/resolv.conf is actually # symlinked to the file we have just updated. resolv_conf_is_symlinked_to_dynamic_file || exit 0 # Restart nscd NSCD_RESTARTED="" NSCD_PIDFILE="" [ -s /var/run/nscd.pid ] && NSCD_PIDFILE="/var/run/nscd.pid" [ -s /var/run/nscd/nscd.pid ] && NSCD_PIDFILE="/var/run/nscd/nscd.pid" if \ [ "$NSCD_PIDFILE" ] \ && [ -x /usr/sbin/nscd ] \ && [ -x /etc/init.d/nscd ] \ && [ -s /etc/nscd.conf ] \ && grep -q '[[:space:]]*enable-cache[[:space:]]\+hosts[[:space:]]\+yes' /etc/nscd.conf \ && start-stop-daemon --stop --quiet --pidfile="$NSCD_PIDFILE" --exec /usr/sbin/nscd --retry=TERM/3/HUP/5 \ && start-stop-daemon --stop --quiet --oknodo --exec /usr/sbin/nscd --retry=0/5 then echo "Stopped Name Service Cache Daemon: nscd." /etc/init.d/nscd start && { sleep 0.1 ; NSCD_RESTARTED=yes ; } fi # Notify users of the resolver if [ -d "${ETCRESOLVCONF}/update-libc.d" ] ; then exec run-parts ${NSCD_RESTARTED:+--arg="--nscd"} "${ETCRESOLVCONF}/update-libc.d" fi exit 0 resolvconf-1.69ubuntu1/etc/resolvconf/interface-order0000644000000000000000000000025412062416774020004 0ustar # interface-order(5) lo.inet* lo.dnsmasq lo.pdnsd lo.!(pdns|pdns-recursor) lo tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* eth* ath* wlan* ppp* * resolvconf-1.69ubuntu1/etc/resolvconf/resolv.conf.d/0000755000000000000000000000000012076277005017464 5ustar resolvconf-1.69ubuntu1/etc/resolvconf/resolv.conf.d/head0000644000000000000000000000022712062416774020314 0ustar # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN resolvconf-1.69ubuntu1/etc/resolvconf/resolv.conf.d/base0000644000000000000000000000000012062416774020312 0ustar resolvconf-1.69ubuntu1/etc/dhcp/0000755000000000000000000000000012076277005013542 5ustar resolvconf-1.69ubuntu1/etc/dhcp/dhclient-enter-hooks.d/0000755000000000000000000000000012076277005020012 5ustar resolvconf-1.69ubuntu1/etc/dhcp/dhclient-enter-hooks.d/resolvconf0000644000000000000000000000543512062416774022127 0ustar # # Script fragment to make dhclient supply nameserver information to resolvconf # # Tips: # * Be careful about changing the environment since this is sourced # * This script fragment uses bash features # * As of isc-dhcp-client 4.2 the "reason" (for running the script) can be one of the following. # (Listed on man page:) MEDIUM(0) PREINIT(0) BOUND(M) RENEW(M) REBIND(M) REBOOT(M) EXPIRE(D) FAIL(D) RELEASE(D) STOP(D) NBI(-) TIMEOUT(M) # (Also used in master script:) ARPCHECK(0), ARPSEND(0) # (Also used in master script:) PREINIT6(0) BOUND6(M) RENEW6(M) REBIND6(M) DEPREF6(0) EXPIRE6(D) RELEASE6(D) STOP6(D) # (0) = master script does not run make_resolv_conf # (M) = master script runs make_resolv_conf # (D) = master script downs interface # (-) = master script does nothing with this if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in BOUND|RENEW|REBIND|REBOOT|TIMEOUT) # Define a resolvconf-compatible m_r_c() function # It gets run later (or, in the TIMEOUT case, MAY get run later) make_resolv_conf() { local R local nameserver R="" if [ "$new_domain_name_servers" ] && [ "$new_domain_name" ] ; then R="${R}domain $new_domain_name " fi if [ "$new_domain_name_servers" ] && [ "$new_domain_search" ] ; then R="${R}search $new_domain_search " fi for nameserver in $new_domain_name_servers ; do R="${R}nameserver $nameserver " done [ ! "$interface" ] || echo -n "$R" | /sbin/resolvconf -a "${interface}.dhclient" } ;; BOUND6|RENEW6|REBIND6) # Define a resolvconf-compatible m_r_c() function # It gets run later (or, in the TIMEOUT case, MAY get run later) make_resolv_conf() { local R local nameserver local zone_id R="" if [ "$new_dhcp6_name_servers" ] && [ "$new_dhcp6_domain_search" ] ; then R="${R}search $new_dhcp6_domain_search " fi shopt -s nocasematch for nameserver in $new_dhcp6_name_servers ; do # If the nameserver has a link-local address # then add a zone ID (interface name) to it. if [[ "$nameserver" =~ ^fe80:: ]] ; then zone_id="%$interface" else zone_id="" fi R="${R}nameserver $nameserver$zone_id " done shopt -u nocasematch [ ! "$interface" ] || echo -n "$R" | /sbin/resolvconf -a "${interface}.ip6.dhclient" } ;; EXPIRE|FAIL|RELEASE|STOP) # Delete resolv.conf info [ ! "$interface" ] || /sbin/resolvconf -d "${interface}.dhclient" ;; EXPIRE6|RELEASE6|STOP6) # Delete resolv.conf info [ ! "$interface" ] || /sbin/resolvconf -d "${interface}.ip6.dhclient" ;; esac fi