From: Gene Heskett <gene.heskett@verizon.net>
To: Bluettooth Linux <linux-bluetooth@vger.kernel.org>
Subject: Making serial (rfcomm0) work, need magic incantation, chicken foot voodoo or what?
Date: Sat, 27 Feb 2010 12:04:04 -0500 [thread overview]
Message-ID: <201002271204.04051.gene.heskett@verizon.net> (raw)
Greetings all;
How does one go about, on linux, making /dev/rfcomm0 available to the likes
of minicom?
Its there, blueman-manager says I have a good signal most of the time, that
it is trusted and bonded. lsof discloses no open paths to the device, but
minicom claims it is in use and exits. There is a shell running on the other
end that should give me a system prompt from that system.
I have restarted /etc/init.d/bluetooth several times to no avail.
It may become usable if I reboot this machine, but that isn't how its
supposed to work I don't think.
So what sort of a magic spell do I need here?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Of course it doesn't work. We've performed a software upgrade.
reply other threads:[~2010-02-27 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201002271204.04051.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).