From: Marcel Holtmann <marcel@holtmann.org>
To: Sybren Stuvel <sybren@thirdtower.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm patch
Date: Wed, 05 Nov 2003 11:16:54 +0100 [thread overview]
Message-ID: <1068027414.10388.149.camel@pegasus> (raw)
In-Reply-To: <200311050945.34166.sybren@thirdtower.com>
Hi Sybren,
> I've been working with bluetooth for a few months now, trying to let BlueZ (on
> my PC) talk to Affix (on my Zaurus). One difficulty is that rfcom doesn't
> flush it's stdout when a new (incoming and/or outgoing) connection has been
> made.
>
> With the attached patch, scripts can use rfcomm to connect via bluetooth and
> fork() the process in order to start using the connection (ie. by running
> pppd over it).
I have no problem with the patch, but if you talk about PPP over RFCOMM
you should better use dund. And why do you need this for scripting? You
can bind a RFCOMM channel to a device and all stuff would be done in
background without user interaction.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-11-05 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 8:45 [Bluez-devel] rfcomm patch Sybren Stuvel
2003-11-05 10:16 ` Marcel Holtmann [this message]
2003-11-05 12:14 ` Sybren Stuvel
2003-11-05 12:22 ` Marcel Holtmann
2003-11-05 15:00 ` Sybren Stuvel
2003-11-05 15:50 ` Alan Huang
2003-11-06 8:39 ` Marcel Holtmann
2003-11-06 20:29 ` [Bluez-users] " Alan Huang
2003-11-06 23:44 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1068027414.10388.149.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=sybren@thirdtower.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.