From: Sybren Stuvel <sybren@thirdtower.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Sybren Stuvel <sybren@thirdtower.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm patch
Date: Wed, 5 Nov 2003 13:14:05 +0100 [thread overview]
Message-ID: <20031105121405.GA9763@sybren.thirdtower.com> (raw)
In-Reply-To: <1068027414.10388.149.camel@pegasus>
On Wed, Nov 05, 2003 at 11:16:54AM +0100, Marcel Holtmann wrote:
> I have no problem with the patch, but if you talk about PPP over RFCOMM
> you should better use dund.
I tried dund, but I couldn't get it to work together with Affix on my
Sharp Zaurus (running OpenZaurus 3.2). I'll try again and come up with
some info that might actually be useful for solving the mistery ;-)
> 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.
Greetz,
Sybren
PS: What is the list's policy on PGP-signed messages?
--
(o_ Q: God, root, what is difference?
//\ A: God can change the byte order on the CPU, root can't.
V_/_
next prev parent reply other threads:[~2003-11-05 12:14 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 [this message]
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=20031105121405.GA9763@sybren.thirdtower.com \
--to=sybren@thirdtower.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.