From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] CYGWIN: Fix resolver debugging output
Date: Tue, 2 Feb 2021 11:02:41 -0700 [thread overview]
Message-ID: <9f964f14-4e8e-b36f-fa73-777c567f2f3b@SystematicSw.ab.ca> (raw)
In-Reply-To: <20210201190215.GA4251@calimero.vinschen.de>
On 2021-02-01 12:02, Corinna Vinschen via Cygwin-patches wrote:
> On Feb 1 15:46, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin-patches wrote:
>>> Except, the value has no meaning for ipv6.
>>
>> It'll print all 0's :-) But: minires does not make use of the _ext field.
>> It does use the conventional nsaddr_list (which is IPv4), but only if
>> Windows native DNS API is not used: "osquery"(aka use_os)=0. >>
>> For debugging purposes, that is enough and very convenient (yet the output
>> needed some tune-up, which I suggested in my patch).
> Ok.
>> But for practical purposes, only Windows API should be used in regular
>> applications (which is the default, anyways, since /etc/resolv.conf is not
>> routinely provided, so "osquery=1" implicitly).
> Yeah, I think so, too. Ideally we should have stripped out all code
> providing non-Windows means (i. e., /etc/resolv.conf support) back when
> this code was folded into Cygwin. It just doesn't make sense, at least
> not by default.
I've been generating /etc/resolv.conf -> /run/resolvconf/resolv.conf for years
in an /etc/postinstall/0p_...dash script from ipconfig /all output (not aware of
a Cygwin source to get this interface info) also run at startup, with some
customizations, and not noticed any issues so far. Should I be wary in future?
>> I'm not sure if improvements to use _ext by the minires own code would be
>> any beneficial.
>>
>> Having said that, AAAA replies should be made understood by the
>> minires-if-os shim code (and I can provide a patch for that, too).
> That would be great!
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-02-02 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:29 Anton Lavrentiev
2021-02-01 10:34 ` Corinna Vinschen
2021-02-01 14:23 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-02-01 15:02 ` Corinna Vinschen
2021-02-01 15:46 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-02-01 19:02 ` Corinna Vinschen
2021-02-02 18:02 ` Brian Inglis [this message]
2021-02-02 19:38 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f964f14-4e8e-b36f-fa73-777c567f2f3b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).