From: Marcel Holtmann <marcel@holtmann.org>
To: giochi@telvia.it
Cc: bluez-users@lists.sourceforge.net
Subject: Re: Re: [Bluez-users] rfcomm problem
Date: Fri, 23 Apr 2004 13:52:12 +0200 [thread overview]
Message-ID: <1082721131.1843.4.camel@merlin> (raw)
In-Reply-To: <1971820044523102014464@telvia.it>
Hi Fabrizio,
> rfcomm that I use is the right one: it comes from bluez-utils...
I don't think so ;)
Try "which rfcomm" to find the whole path of the program. Maybe you have
both installed and the wrong one is the first in your search path.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-04-23 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 10:20 Re: [Bluez-users] rfcomm problem giochi
2004-04-23 11:52 ` Marcel Holtmann [this message]
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=1082721131.1843.4.camel@merlin \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=giochi@telvia.it \
/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