From owner-freebsd-hackers Thu May 24 11:13:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 789C437B422 for ; Thu, 24 May 2001 11:13:28 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f4OIAAq40514; Thu, 24 May 2001 11:10:10 -0700 (PDT) Date: Thu, 24 May 2001 11:10:10 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: "Jacques A. Vidrine" Cc: James Howard , Matt Dillon , Alfred Perlstein , Lyndon Nerenberg , Subject: Re: telnet to AF_UNIX sockets [PATCH] In-Reply-To: <20010523220844.A26487@shade.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 23 May 2001, Jacques A. Vidrine wrote: > You are not the only one. I can appreciate the `neat' factor, but I > cringed at the commit. It seems like functionality that would be > better put in a separate utility (or port even). It's not like you'd > ever want to run the NVT protocol over an AF_UNIX socket. It depends on how you look at it. If you see telnet as a network client, then you cringe at this (I did initially). But when you think about it, all telnet really does is connect to sockets, so why not extend its functionality to local sockets? -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message