On Fri, 26 Sep 2003 21:37:21 +0200, Thomas Hood [EMAIL PROTECTED] said:
On Fri, 2003-09-26 at 20:25, Manoj Srivastava wrote:
I have a laptop that sometimes is on fixed ip wireless
networks. Since dhcp is not involved, there is nothing that updates
resolvconf, which could be pointing to an
On Sep 28, Manoj Srivastava ([EMAIL PROTECTED]) wrote:
On Fri, 26 Sep 2003 21:37:21 +0200, Thomas Hood [EMAIL PROTECTED] said:
On Fri, 2003-09-26 at 20:25, Manoj Srivastava wrote:
I have a laptop that sometimes is on fixed ip wireless
networks. Since dhcp is not involved, there is
Manoj wrote:
I would be interested in knowing how you set it up equivalent
to cardctl scheme allows me to set up pcmcia networks.
cardmgr's system of configuring things dependently upon
scheme,socket,instance,hwaddr is quite powerful but it is
possible to configure interfaces dependently on
On Sun, 28 Sep 2003 21:49:28 +0200, Thomas Hood [EMAIL PROTECTED] said:
Manoj wrote:
I would be interested in knowing how you set it up equivalent to
cardctl scheme allows me to set up pcmcia networks.
cardmgr's system of configuring things dependently upon
scheme,socket,instance,hwaddr
Hi,
I have a laptop that sometimes is on fixed ip wireless
networks. Since dhcp is not involved, there is nothing that updates
resolvconf, which could be pointing to an inaccurate set of servers.
The solution, in my case, was to add the following star and
stop functions to
On Fri, 2003-09-26 at 20:25, Manoj Srivastava wrote:
I have a laptop that sometimes is on fixed ip wireless
networks. Since dhcp is not involved, there is nothing that updates
resolvconf, which could be pointing to an inaccurate set of servers.
If you bring the interface up with ifup
Are there plans to run up commands in interfaces after
dns-nameservers? Some of my up commands, and probably others, consist of
setting up static routes to other boxes. It is nice to be able to
specify these other boxes by name, and have it resolved using the name
servers set up by the resolvconf
On Thu, 2003-09-25 at 07:29, Jerry Haltom wrote:
Are there plans to run up commands in interfaces after
dns-nameservers?
That would be desirable. It would require a change to the
ifupdown package.
Also, this may seem a LITTLE bit silly, but can dns-domainnames be
provided with a name, which
The resolvconf package provides a framework for dynamic updating
of /etc/resolv.conf and other nameserver lists. (See the long
description at packages.debian.org/resolvconf .)
The resolvconf package is now at version 0.44 in unstable.
If you are interested in the package and haven't tested it
Thomas Hood [EMAIL PROTECTED] writes:
On Sun, 2003-07-06 at 01:00, Goswin Brederlow wrote:
You should think of a mechanism for daemons to get notified about
changes in resolv.conf.
There is already such a mechanism. See below.
Like providing a function to register a script
and a
On Sat, 2003-07-05 at 22:40, Simon Hürlimann wrote:
I'd prefer update-resolv like
update-alternatives update-initrd
update-catalog update-ispell-dictionary
update-default-aspell update-menus
update-default-ispell update-mime
to name just a
On Sun, 2003-07-06 at 01:00, Goswin Brederlow wrote:
You should think of a mechanism for daemons to get notified about
changes in resolv.conf.
There is already such a mechanism. See below.
Like providing a function to register a script
and a list of arguments (like the PID of the program to
On Sun, 2003-07-06 at 01:32, Marco d'Itri wrote:
On Jul 05, Thomas Hood [EMAIL PROTECTED] wrote:
* Before entering the Debian archive it would be nice if resolvconf
were supported by all packages that currently futz with
/etc/resolv.conf, including pump and bind.
If you mean that if
#include hallo.h
* Thomas Hood [Sat, Jul 05 2003, 09:51:56PM]:
Summary
~~~
Resolvconf is a proposed standard framework for updating the
system's information about currently available nameservers.
Most importantly, it manages /etc/resolv.conf , but it does
a bit more than that.
The
On Sun, 2003-07-06 at 12:13, Thomas Hood wrote:
No, I meant that before entering the Debian archive it would
be nice if resolvconf were supported by all packages that
currently futz with /etc/resolv.conf, including pump and bind.
Which other packages?
I guess I need to explain more
On Sun, 2003-07-06 at 12:42, Eduard Bloch wrote:
Please, would you consider to add another feature: priorising some
entries depending on the source. That means:
pppoeconf's and pppconfig's script run the tool with parameter --class
dialup, dhcp clients with --class dynamic and the default
On Sun, 2003-07-06 at 01:52, Nick Phillips wrote:
Actually I think the simplest form would be to have /etc/resolvconf/notify.d
and run all scripts in there at the relevant times, with any necessary
arguments (which would be standard).
Please take a look at how resolvconf runs the scripts in
Summary
~~~
Resolvconf is a proposed standard framework for updating the
system's information about currently available nameservers.
Most importantly, it manages /etc/resolv.conf , but it does
a bit more than that.
Background and rationale
During the long discussion
Am Samstag, 5. Juli 2003 21.51 schrieb Thomas Hood:
Summary
~~~
Resolvconf is a proposed standard framework for updating the
system's information about currently available nameservers.
Cool, I really like this idea.
the need to supply resolver information
to DNS cache programs such as
Thomas Hood [EMAIL PROTECTED] writes:
Summary
~~~
Resolvconf is a proposed standard framework for updating the
system's information about currently available nameservers.
Most importantly, it manages /etc/resolv.conf , but it does
a bit more than that.
You should think of a
On Sun, Jul 06, 2003 at 01:00:20AM +0200, Goswin Brederlow wrote:
The simplest form would be:
resolv.conf-register /etc/init.d/squid reload
Actually I think the simplest form would be to have /etc/resolvconf/notify.d
and run all scripts in there at the relevant times, with any necessary
On Jul 05, Thomas Hood [EMAIL PROTECTED] wrote:
* Before entering the Debian archive it would be nice if resolvconf
were supported by all packages that currently futz with
/etc/resolv.conf, including pump and bind.
If you mean that if should be mandatory to install this package on every
22 matches
Mail list logo
