From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] [Fwd: Bug#322732: bluez-utils: rfcomm bind fails with obscure error message]
Date: Mon, 22 Aug 2005 13:12:29 +0200 [thread overview]
Message-ID: <1124709149.23599.19.camel@pegasus> (raw)
In-Reply-To: <1124658001.1592.21.camel@saag.bunker.heddley.com>
Hi Edd,
> > When the 'rfcomm' kernel module isn't compiled with CONFIG_BT_RFCOMM_TTY
> > enabled, 'rfcomm bind' will fail with an obscure error message, "Can't
> > create device: Operation not supported". It does this when it's trying to
> > bind to a device in /dev.
this error message is correct. It follows the errno error code that
comes back from the kernel.
> > Could this be changed to report something more useful, such as "Check
> > rfcomm.ko is compiled with TTY support"?
What about a patch for the RFCOMM manual page that explains this
problem?
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-08-22 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 21:00 [Bluez-users] [Fwd: Bug#322732: bluez-utils: rfcomm bind fails with obscure error message] Edd Dumbill
2005-08-22 11:12 ` Marcel Holtmann [this message]
2005-08-22 12:48 ` Fred Schaettgen
2005-08-22 14:20 ` 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=1124709149.23599.19.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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