[Resolvconf-devel] [LCFC] templates://resolvconf/{templates}
Justin B Rye
jbr at edlug.org.uk
Mon Feb 4 14:10:07 UTC 2008
Christian Perrier wrote:
> 1) I finally did "s/nameserver/name server". That may be debatable, so
> please comment
There are some missed cases. In fact I'd be happy making it one
word throughout, but I'll go with the RFC.
> 2) I have a doubt for "configurers". ispell complains about it
"Configurator" gets twice as many Google hits, but both are
strangely low numbers.
> Template: resolvconf/downup-interfaces
[...]
> _Description: Network interfaces configuration mandatory
> Once resolvconf is installed, interface configurers supply name server
> information to it (which it then makes available to the C library resolver
MJ's "configuration helpers" seem plausible.
> Template: resolvconf/link-tail-to-original
[...]
> Until /etc/network/interfaces has been edited and the affected
> interfaces brought down and up again, the nameservers addresses will
> not be included in the dynamically generated resolver configuration
> file.
That's "name server_ addresses" (or a real possessive, "name
servers' addresses").
(Beware of the fixed string "dns-nameservers" used twice in this
template.)
> Package: resolvconf
[...]
> Description: nameservers information handler
That's "name server information handler". Writing it as two words
results in a taller, wobblier noun-pile; that's one of the reasons
compounds like this often gradually hyphenate or solidify.
> 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
> nameservers information and programs that use nameservers
> information. Examples of programs that supply nameservers
> information are: ifupdown, DHCP clients, the PPP daemon and
> local nameservers. Examples of programs that use this
> information are: DNS caches, resolver libraries and the
> programs that use them.
Where did all these nameserverses come from? It's "nameserver
information", or possibly "name server information". But now that
I've noticed how often the word occurs I'm going to have to rewrite
it to get rid of some of the repetitivitivity.
Also, "framework for keeping track" seems too weak. If you ask
resolvconf which DNS server you should be using, it doesn't reply
with detailed information about the balance of conflicting opinions,
it just gives an authoritative answer. How about:
Resolvconf is a framework for keeping the system's information about
currently available name servers up to date. It sets itself up as the
intermediary between programs that supply this information, such as
ifupdown, DHCP clients, the PPP daemon, and local name servers, and
programs that use this information, such as DNS caches and resolver
libraries.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
-------------- next part --------------
--- ../resolvconf.old/debian/templates 2008-01-05 17:18:40.000000000 +0000
+++ debian/templates 2008-02-04 13:10:37.000000000 +0000
@@ -2,55 +2,54 @@
Type: boolean
Default: true
_Description: Prepare /etc/resolv.conf for dynamic updates?
- This 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 agree then this link will be created. The existing /etc/resolv.conf
- file will be preserved as /etc/resolvconf/resolv.conf.d/original; it will
- be restored if this package is removed.
+ 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.
.
- If you wish to prevent future installations from recreating the symbolic
- link then you can run dpkg-reconfigure later to withdraw your agreement.
+ 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.
.
- If you do not agree then the necessary symbolic link will not be created
- and consequently your resolver configuration file will not be dynamically
- updated. In order to activate dynamic updating you will have to configure
- resolvconf manually following the straightforward instructions in the
- README file. If you choose not to configure resolvconf at all then you
- should remove the package because its presence causes some programs to
- deviate from their default behavior.
- .
- However you decide, you should read 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: Remember to reconfigure network interfaces
- Once resolvconf is installed, interface configurers supply nameserver
- information to it (which it then makes available to the C Library resolver
+_Description: Network interfaces configuration mandatory
+ Once resolvconf is installed, interface configuration helpers supply name server
+ information to it (which it then makes available to the C library resolver
and to DNS caches). However, they do this only when they bring up interfaces.
- Therefore for resolvconf's nameserver information to be up to date after
- initial installation it is necessary to reconfigure interfaces --
- that is, to take them down and then to bring them up again -- and to restart
+ Therefore for resolvconf's name server information to be up to date after
+ initial installation it is necessary to reconfigure interfaces (that is,
+ to take them down and then to bring them up again) and to restart
DNS caches.
Template: resolvconf/link-tail-to-original
Type: boolean
Default: false
_Description: Append original file to dynamic file?
- If your original static resolver configuration file (/etc/resolv.conf)
- contains nameserver addresses then those addresses should be listed on
+ 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 as described in the
- README. Until you have modified /etc/network/interfaces and reconfigured
- the affected interfaces resolvconf will not include those addresses in the
- dynamically generated resolver configuration file. Without those addresses
- you may have trouble resolving domain names. A TEMPORARY solution is to
- append the whole original resolver configuration file to the end of
- the dynamically generated file. This will be done if there is a symbolic
- link from /etc/resolvconf/resolv.conf.d/tail to
- /etc/resolvconf/resolv.conf.d/original. If you agree then this symbolic
- link will be created, provided that no /etc/resolvconf/resolv.conf.d/tail
- already exists.
+ 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 you have modified /etc/network/interfaces to add the required
- "dns-nameservers" lines you should point the
- /etc/resolvconf/resolv.conf.d/tail symbolic link to /dev/null.
+ 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.
--- ../resolvconf.old/debian/control 2006-08-09 15:23:20.000000000 +0100
+++ debian/control 2008-02-04 13:42:43.000000000 +0000
@@ -11,16 +11,13 @@
Enhances: dhcp3-client (>= 3.0+3.0.1rc11-5), dhcp-client (>= 2.0pl5-18), dhcpcd (>= 1:1.3.22pl4-9), pump (>= 0.8.19), udhcpc (>= 0.9.8cvs20050124-3), ppp (>= 2.4.2), ifupdown (>= 0.6.4-4.7), network-manager, bind9 (>= 1:9.2.3-1), bind (>= 1:8.4.1-2), dnsmasq (>= 2.9-2), pdnsd (>= 1.1.11par-1), totd (>= 1.4-4), libc6, nscd
Depends: coreutils (>= 5.93), lsb-base (>= 3.0-9), ${misc:Depends}
Conflicts: pppconfig (<< 2.3.1), pppoeconf (<< 1.0), xisp, webmin (<< 1.150-2), webmin-wvdial (<< 1.160-3), dhcp3-client (<< 3.0+3.0.1rc11-5), dhcp-client (<< 2.0pl5-18), dhcp-client (= 3.0.1betaRC4-1), dhcpcd (<< 1:1.3.22pl4-7), pump (<< 0.8.15-1), udhcpc (<< 0.9.8cvs20050124-3), pcmcia-cs (<< 3.2.5-1), ifupdown (<< 0.6.4-4.1), divine, laptop-net (<< 2.21-1), whereami (<< 0.3.3), bind9 (<< 1:9.2.1-7), bind (<< 1:8.3.4-1), dnsmasq (<< 1.13-2), pdnsd (<< 1.1.10par-4), totd (<< 1.4-4)
-Description: nameserver information handler
- 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 programs that use nameserver
- information. Examples of programs that supply nameserver
- information are: ifupdown, DHCP clients, the PPP daemon and
- local nameservers. Examples of programs that use this
- information are: DNS caches, resolver libraries and the
- programs that use them.
+Description: name server information handler
+ Resolvconf is a framework for keeping the system's information about
+ currently available name servers up to date. It sets itself up as the
+ intermediary between programs that supply this information, such as
+ ifupdown, 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
+ This package may require some manual configuration. Please
read the README file for detailed instructions.
-------------- next part --------------
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
/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.
.
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: Network interfaces configuration mandatory
Once resolvconf is installed, interface configuration helpers supply name server
information to it (which it then makes available to the C library resolver
and to DNS caches). However, they do this only when they bring up interfaces.
Therefore for resolvconf's name server information to be up to date after
initial installation it is necessary to reconfigure interfaces (that is,
to take them down and then to bring them up again) and to restart
DNS caches.
Template: resolvconf/link-tail-to-original
Type: boolean
Default: false
_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 as described in 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.
-------------- next part --------------
Source: resolvconf
Section: net
Priority: optional
Maintainer: resolvconf maintainers <resolvconf-devel at lists.alioth.debian.org>
Uploaders: Eric Evans <eevans at sym-link.com>, Daniel Kahn Gillmor <dkg at fifthhorseman.net>, Marc Haber <mh+debian-packages at zugschlus.de>, Thomas Hood <jdthood at yahoo.co.uk>, Marco Nenciarini <mnencia at debian.org>
Build-Depends: debhelper (>= 5)
Standards-Version: 3.7.2.1
Package: resolvconf
Architecture: all
Enhances: dhcp3-client (>= 3.0+3.0.1rc11-5), dhcp-client (>= 2.0pl5-18), dhcpcd (>= 1:1.3.22pl4-9), pump (>= 0.8.19), udhcpc (>= 0.9.8cvs20050124-3), ppp (>= 2.4.2), ifupdown (>= 0.6.4-4.7), network-manager, bind9 (>= 1:9.2.3-1), bind (>= 1:8.4.1-2), dnsmasq (>= 2.9-2), pdnsd (>= 1.1.11par-1), totd (>= 1.4-4), libc6, nscd
Depends: coreutils (>= 5.93), lsb-base (>= 3.0-9), ${misc:Depends}
Conflicts: pppconfig (<< 2.3.1), pppoeconf (<< 1.0), xisp, webmin (<< 1.150-2), webmin-wvdial (<< 1.160-3), dhcp3-client (<< 3.0+3.0.1rc11-5), dhcp-client (<< 2.0pl5-18), dhcp-client (= 3.0.1betaRC4-1), dhcpcd (<< 1:1.3.22pl4-7), pump (<< 0.8.15-1), udhcpc (<< 0.9.8cvs20050124-3), pcmcia-cs (<< 3.2.5-1), ifupdown (<< 0.6.4-4.1), divine, laptop-net (<< 2.21-1), whereami (<< 0.3.3), bind9 (<< 1:9.2.1-7), bind (<< 1:8.3.4-1), dnsmasq (<< 1.13-2), pdnsd (<< 1.1.10par-4), totd (<< 1.4-4)
Description: name server information handler
Resolvconf is a framework for keeping the system's information about
currently available name servers up to date. It sets itself up as the
intermediary between programs that supply this information, such as
ifupdown, 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.
More information about the Resolvconf-devel
mailing list