From owner-freebsd-net Tue May 22 11:14:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 1DC7737B422 for ; Tue, 22 May 2001 11:14:07 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA20173; Tue, 22 May 2001 14:13:59 -0400 (EDT) (envelope-from wollman) Date: Tue, 22 May 2001 14:13:59 -0400 (EDT) From: Garrett Wollman Message-Id: <200105221813.OAA20173@khavrinen.lcs.mit.edu> To: Barney Wolff Cc: freebsd-net@FreeBSD.ORG Subject: Re: Using connect() on UDP RPC client sockets. In-Reply-To: <20010522001710.A91710@tp.databus.com> References: <200105202256.aa30752@salmon.maths.tcd.ie> <20010520184033.A83645@tp.databus.com> <200105211850.OAA09062@khavrinen.lcs.mit.edu> <20010522001710.A91710@tp.databus.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Can anyone realistically see bind or ntpd being modified to take > advantage of it when running on FreeBSD? Yes, given that it results in substantial simplification and (in the case of named) enables non-privileged operation even in the presence of dynamically-configured network interfaces. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message