From owner-freebsd-arch  Thu Nov  7 13:18:36 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7AE9D37B401; Thu,  7 Nov 2002 13:18:35 -0800 (PST)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1159843E42; Thu,  7 Nov 2002 13:18:35 -0800 (PST)
	(envelope-from sam@errno.com)
Received: from melange (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.5/8.12.1) with ESMTP id gA7LIU1H064807
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Thu, 7 Nov 2002 13:18:30 -0800 (PST)?g
	(envelope-from sam@errno.com)œ
X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange
Message-ID: <035101c286a3$4a7ccf80$52557f42@errno.com>
From: "Sam Leffler" <sam@errno.com>
To: "Poul-Henning Kamp" <phk@critter.freebsd.dk>
Cc: "Julian Elischer" <julian@elischer.org>, <arch@FreeBSD.ORG>,
	"Long,    Scott" <Scott_Long@adaptec.com>, <re@FreeBSD.ORG>,
	"Murray Stokely" <murray@freebsdmall.com>
References: <4259.1036703140@critter.freebsd.dk>
Subject: Re: Bluetooth code 
Date: Thu, 7 Nov 2002 13:19:00 -0800
Organization: Errno Consulting
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

> In message <031401c2869f$db71b720$52557f42@errno.com>, "Sam Leffler"
writes:
> >I made a quick pass over this code.  It's not clear to me why this stuff
is
> >or should be dependent on netgraph.  The code looks to support a new
> >protocol domain and sockets within that domain so it would seem possible
for
> >it to stand apart from netgraph.  A bluetooth implementation that was not
> >tied to netgraph would be preferrable as freebsd users would get the
> >benefits of additional (non-freebsd users) working with the code.
> >
> >Specific stuff:
> >
> >1. Why isn't btsockstat integrated into netstat?
>
> Actually, isn't netstat(8) hairy enough as it is ?
>

I understand why btsockstat was written as a standalone program.  However I
think it would be better to integrate it into the program people know to use
to view active sockets.

    Sam


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message