From owner-freebsd-chat@FreeBSD.ORG Mon Sep 1 19:13:17 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1BBD16A4BF for ; Mon, 1 Sep 2003 19:13:17 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4690B43FEA for ; Mon, 1 Sep 2003 19:13:17 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfj8a.dialup.mindspring.com ([165.247.205.10] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19u0fP-0007lt-00; Mon, 01 Sep 2003 19:13:11 -0700 Message-ID: <3F53FC71.E97C9FEC@mindspring.com> Date: Mon, 01 Sep 2003 19:12:01 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jeremy C. Reed" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c5d3a93d240021e01b408fbb038440a83ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: chat@freebsd.org Subject: Re: strip FreeBSD a bit X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 02:13:18 -0000 "Jeremy C. Reed" wrote: > On Mon, 1 Sep 2003, Terry Lambert wrote: > > > Or another alternative is his resolver code. His low-level DNS resolver > > > routines are in "public domain". > > > > > > Has anyone integrated djb's public domain resolver code into libc? > > > > I didn't see that the djbdns license declared it to be in the > > public domain. > > I am not sure where either. But DJB noted to bugtraq > <20020704164247.30990.qmail@cr.yp.to> a while back that: > > The .[ch] files (dns.h, dns_dfd.c, dns_domain.c, dns_dtda.c, dns_ip.c, > dns_ipq.c, dns_mx.c, dns_name.c, dns_nd.c, dns_packet.c, dns_random.c, > dns_rcip.c, dns_rcrw.c, dns_resolve.c, dns_sortip.c, dns_transmit.c, > dns_txt.c) and all necessary lower-level .[ch] files are now in the > public domain. > > This is also mentioned at http://cr.yp.to/djbdns/res-disaster.html Yes, I saw this note at that location. However, I did not see a claim and then a disclaim in the source files themselves. > Looking at this source (djbdns-1.05), I don't see any copyrights or > licenses in any of these individual files. Exactly. Berne states that any files not explicitly disclaimed by the author are inherently copyright the author, and without an explicit disclaim by the author of record stating that it's in the public domain, or a license, the code is not legal to use, since nothing gives me any rights to it. > > 3) In accordance with his standard diatribe on SRV and other > > new record types, he only supports address records, MX, > > and TXT records, which is less than useful in the real > > world. > > I have no answer; I do not (knowlingly) use SRV records. Too bad. They are required for zeroconf, and "Rendevous". > I haven't looked at it closely. I just read that it is "designed to > replace the old BIND res_*/dn_* library" at > http://cr.yp.to/djbdns/blurb/library.html. Yes, in about the same way that Windows NT was designed to replace UNIX. 8-). Not plug compatible... > I don't know how easy it would be (or if it would be worth it) to create > wrappers. Doing so would actually defeat his purpose in creating his new API, at least according to the page you referenced on his site. > Anyways, I am curious if anyone uses it (or has tried it) as an > alternative. I looked at it. The API is "OK", though it's not inherently thread safe, unless you implement thread local storage, or open a socket per outstanding request, either of which are not nice. It's inherently reentrant, so in theory it could be made thread safe relatively easily, if you wanted to put in the effort. With no license attached to the code, though, it was uninteresting to me to adopt a new API, when I could write my own and not be under the license cloud, at the same time maintaining binary compatability. 8-). -- Terry