From owner-freebsd-arch  Thu Nov  7 12:54: 0 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 F31F937B401; Thu,  7 Nov 2002 12:53:58 -0800 (PST)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 84F6C43E4A; Thu,  7 Nov 2002 12:53:58 -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 gA7Krr1H064659
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Thu, 7 Nov 2002 12:53:55 -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: <031401c2869f$db71b720$52557f42@errno.com>
From: "Sam Leffler" <sam@errno.com>
To: "Julian Elischer" <julian@elischer.org>, <arch@FreeBSD.ORG>
Cc: "Long, Scott" <Scott_Long@adaptec.com>, <re@FreeBSD.ORG>,
	"Murray Stokely" <murray@freebsdmall.com>
References: <Pine.BSF.4.21.0211061346120.726-100000@InterJet.elischer.org>
Subject: Re: Bluetooth code
Date: Thu, 7 Nov 2002 12:54:24 -0800
Organization: Errno Consulting
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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

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?
2. l2test, hcdump, and hcinfo are missing (cited in man pages).
3. A bluetooth(4) man page would be useful.

It's unclear to me how this support is used.  There are no user-level
applications that make use of it and I don't recognize existing applications
that could use it.  I suggest that w/o a "real user" adding this stuff to
the system is premature.

    Sam


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