From: VJB <v-j-b@gmx.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] BT-Barcode-Scanner, /dev/rfcommX
Date: Sun, 01 May 2005 18:47:47 +0200 [thread overview]
Message-ID: <42750833.8010908@gmx.de> (raw)
Hi,
I have a problem with reading and writing of /dev/rfcommX for others,
on Suse Linux Prof. 9.2.
I'm using the command
rfcomm bind ...
for connecting a BT-Barcode-Scanner with the system. All works fine.
But every time, you run this command, the rights for the file /dev/rfcommX
change to read and write only for root. But I need although read and write
for others.
Can you help me?
Regards,
Volker Brandhoff
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-05-01 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 16:47 VJB [this message]
2005-05-01 17:11 ` [Bluez-users] BT-Barcode-Scanner, /dev/rfcommX Szilágyi Szilveszter
2005-05-01 17:17 ` 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=42750833.8010908@gmx.de \
--to=v-j-b@gmx.de \
--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 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.