From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Sending bug reports without setting up email
Date: Wed, 20 Jul 2016 17:01:50 +0200 [thread overview]
Message-ID: <375d7040-05cb-377c-5df9-d345087291ee@cs.ucla.edu> (raw)
In-Reply-To: <m3shv44evl.fsf@gnus.org>
On 07/20/2016 03:29 PM, Lars Ingebrigtsen wrote:
> Yes, res_ninit would be better, I think. But is res_ninit supported
> less/more than res_init on non-GNU/Linux systems, I wonder? I tried
> googling for this briefly, but was unable to say...
If memory serves, res_ninit was introduced by BIND 8.2 in the previous
millennium and nowadays any system that has the deprecated res_init
function should also have res_ninit. For what it's worth res_ninit is on
the oldest platform I have easy access to (Solaris 10, released 2005).
On systems that lack res_ninit we could punt and pretend there are no
name servers.
Sorry, I've lost track of why you wanted direct access to the list of
name servers. Something about looking up MX records for gnu.org when
half-a-dozen other bits of code don't work? For something that esoteric
maybe it'd be simpler to hard-code the IP addresses.
next prev parent reply other threads:[~2016-07-20 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:50 Sending bug reports without setting up email Lars Ingebrigtsen
2016-05-09 18:19 ` Lars Ingebrigtsen
2016-05-09 18:52 ` Eli Zaretskii
2016-05-09 19:03 ` Lars Ingebrigtsen
2016-05-10 15:02 ` Paul Eggert
2016-05-11 20:55 ` daniel sutton
2016-05-11 21:00 ` Kaushal Modi
2016-05-11 21:05 ` Eli Zaretskii
2016-05-11 21:17 ` Kaushal Modi
2016-05-12 5:47 ` Eli Zaretskii
2016-05-11 21:01 ` Eli Zaretskii
2016-07-20 13:29 ` Lars Ingebrigtsen
2016-07-20 15:01 ` Paul Eggert [this message]
2016-07-20 15:06 ` Lars Ingebrigtsen
2016-07-20 16:07 ` Paul Eggert
2016-07-20 16:10 ` Lars Ingebrigtsen
2016-07-20 16:27 ` Paul Eggert
2016-07-20 16:30 ` Lars Ingebrigtsen
2016-07-20 16:37 ` Stefan Monnier
2016-07-21 10:45 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=375d7040-05cb-377c-5df9-d345087291ee@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).