Date: Thu, 7 Nov 2002 13:19:00 -0800 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> Subject: Re: Bluetooth code Message-ID: <035101c286a3$4a7ccf80$52557f42@errno.com> References: <4259.1036703140@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?035101c286a3$4a7ccf80$52557f42>