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 13:22:21 +0100 [thread overview]
Message-ID: <1068034941.10385.190.camel@pegasus> (raw)
In-Reply-To: <20031105121405.GA9763@sybren.thirdtower.com>
Hi Sybren,
> > 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.
>
> I wanted to delay the starting of pppd until the connection was actually
> made. I thought it was the easiest to just parse rfcomm's output.
try to implement an updetach feature ;) But I prefer that you use this
rfcomm bind 0 <bdaddr> [channel] (only once needed)
pppd /dev/rfcomm0 ...
> PS: What is the list's policy on PGP-signed messages?
We have no policy about that and I never sign messages that go out to a
mailing list.
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 12:22 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
2003-11-05 12:14 ` Sybren Stuvel
2003-11-05 12:22 ` Marcel Holtmann [this message]
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=1068034941.10385.190.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox