On Jan 21 17:11, Yaakov (Cygwin/X) wrote:
Corinna Vinschen wrote:
I'm not asking to use the resolver lib. I'm asking that the resolver
code in bind's libs uses the same method to fetch nameserver and
domain information as Cygwin's default resolver does.
You could just as easily make the
A request: I think a lot of people would find it useful if you were to split
out the client tools, in particular 'host', from the bind server package. I
don't want to run a DNS server-- I just want to be able to use the 'host'
command. Thanks, Andrew.
On Jan 21 11:51, Andrew Schulman wrote:
A request: I think a lot of people would find it useful if you were to split
out the client tools, in particular 'host', from the bind server package. I
don't want to run a DNS server-- I just want to be able to use the 'host'
command. Thanks, Andrew.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Schulman wrote:
A request: I think a lot of people would find it useful if you were to split
out the client tools, in particular 'host', from the bind server package. I
don't want to run a DNS server-- I just want to be able to use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
And here's another problem, Yaakov.
Why does the bind package require an /etc/resolv.conf file? Isn't that
used only by the resolver lib? And the resolver lib is part of Cygwin
1.7 anyway, or in the minires package
On Jan 21 11:20, Yaakov (Cygwin/X) wrote:
Corinna Vinschen wrote:
Why does the bind package require an /etc/resolv.conf file? Isn't that
used only by the resolver lib? And the resolver lib is part of Cygwin
1.7 anyway, or in the minires package for Cygwin 1.5. Minires/Cygwin 1.7
don't
A request: I think a lot of people would find it useful if you were to
split
out the client tools, in particular 'host', from the bind server package. I
don't want to run a DNS server-- I just want to be able to use the 'host'
command. Thanks, Andrew.
I don't see that as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Ok, but the Cygwin resolver lib also works without this file because the
nameserver information can be (and is) fetched from Windows. Would it
be feasible to use the same method as the resolver lib so that we don't
have
On Jan 21 11:58, Yaakov (Cygwin/X) wrote:
Corinna Vinschen wrote:
Ok, but the Cygwin resolver lib also works without this file because the
nameserver information can be (and is) fetched from Windows. Would it
be feasible to use the same method as the resolver lib so that we don't
have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Well, yes. That's why I'm asking the above question.
I'm really not sure where you're going with this. This isn't Cygwin
specific; BIND doesn't use libresolv on Linux either.
Yaakov
-BEGIN PGP SIGNATURE-
On Jan 21 12:56, Yaakov (Cygwin/X) wrote:
Corinna Vinschen wrote:
Well, yes. That's why I'm asking the above question.
I'm really not sure where you're going with this. This isn't Cygwin
specific; BIND doesn't use libresolv on Linux either.
I'm not asking to use the resolver lib. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I'm not asking to use the resolver lib. I'm asking that the resolver
code in bind's libs uses the same method to fetch nameserver and
domain information as Cygwin's default resolver does.
You could just as easily make
At 12:37 PM 1/21/2009, Corinna Vinschen wrote:
On Jan 21 11:20, Yaakov (Cygwin/X) wrote:
Corinna Vinschen wrote:
Why does the bind package require an /etc/resolv.conf file? Isn't that
used only by the resolver lib? And the resolver lib is part of Cygwin
1.7 anyway, or in the minires
On Jan 18 22:54, Christopher Faylor wrote:
Woo hoo!
Thanks Yaakov!
Indeed. Just go ahead, Yaakov.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
Woo hoo!
Thanks Yaakov!
cgf
15 matches
Mail list logo