From owner-freebsd-current@FreeBSD.ORG  Tue Feb 17 11:05:25 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B8CB71065670
	for <current@FreeBSD.org>; Tue, 17 Feb 2009 11:05:25 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211])
	by mx1.freebsd.org (Postfix) with ESMTP id 7BA818FC16
	for <current@FreeBSD.org>; Tue, 17 Feb 2009 11:05:25 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: by palm.hoeg.nl (Postfix, from userid 1000)
	id 1228F1CE40; Tue, 17 Feb 2009 12:05:24 +0100 (CET)
Date: Tue, 17 Feb 2009 12:05:24 +0100
From: Ed Schouten <ed@80386.nl>
To: Michael Butler <imb@protected-networks.net>
Message-ID: <20090217110524.GC79178@hoeg.nl>
References: <20080526110543.J26343@fledge.watson.org>
	<alpine.BSF.2.00.0902161233440.5806@fledge.watson.org>
	<4999F7F9.4030204@elischer.org>
	<499A024A.60209@protected-networks.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="a6YTfLRor63AaheO"
Content-Disposition: inline
In-Reply-To: <499A024A.60209@protected-networks.net>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: current@FreeBSD.org
Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 11:05:26 -0000


--a6YTfLRor63AaheO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Michael Butler <imb@protected-networks.net> wrote:
> The usage of rfcomm_sppd as documented in the handbook results in ..
>=20
> Feb 16 19:12:57 toshi kernel: ugen1.2: <Belkin Components> at usbus1
> Feb 16 19:12:57 toshi kernel: ubt0: <Belkin Components FBT003v2
> 	Bluetooth, class 224/1, rev 1.10/5.25, addr 2> on usbus1
> Feb 16 19:13:31 toshi kernel: pid 50258 (rfcomm_sppd) is using legacy
> 	pty devices
>=20
>  .. when connecting to my GPS. Is this functionality to be impacted?

No, it shouldn't, but there's still something wrong with rfcomm_sppd,
because it doesn't use proper libc functions to allocate
pseudo-terminals.

How did you start the application?

--=20
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/

--a6YTfLRor63AaheO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkmamfQACgkQ52SDGA2eCwVrlgCfbxiOIPyFnpn7+Euw5qo1ipQv
aaoAniKvClKBaP8Q+BxNCyPQ+P+MqpBr
=4ZeA
-----END PGP SIGNATURE-----

--a6YTfLRor63AaheO--