Date: Thu, 7 Nov 2002 12:54:24 -0800 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> Subject: Re: Bluetooth code Message-ID: <031401c2869f$db71b720$52557f42@errno.com> References: <Pine.BSF.4.21.0211061346120.726-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?031401c2869f$db71b720$52557f42>