From: David Armour <d.f.armour@shaw.ca>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] bash: syntax error near unexpected token `newline'
Date: Wed, 30 Aug 2006 12:51:25 -0700 [thread overview]
Message-ID: <44F5EC3D.1050607@shaw.ca> (raw)
hello list,
i hope this is the right place to ask for help translating the above
error. googling the error message produced no hits.
i'm trying to get my plantronics headset working with Micro Star
International Bluetooth Dongle. i've gotten further using info found at:
http://article.gmane.org/gmane.linux.ubuntu.user/77096/match=bluez+gnome+headset+dapper
than with anything i could dig up in the wiki, or in the ubuntu forums.
## for plantronics headset, the red&blue lights must be flashing ## check!
>> The command should output something like this:
>> Scanning ... 00:13:70:4F:83:3B Nokia HS-26W
## for headset,... 00:03:89:53:EC:7F 320 Plantronics ## woohoo!
>>
>> The set of numbers is the Bluetooth Device Address, bd_addr for short.
>> Running the command: >> sudo hidd --connect <bd_addr>
>> should connect the mouse to the computer, and allow the mouse to work.
## running: >>sudo hidd --connect <00:03:89:53:EC:7F>
## bash: syntax error near unexpected token `newline' ## gah!
can someone where to look to address this error? thanks in advance.
## relevant hcid.conf: (tried both pinwrapper/bluepin lines
with/without ';')
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
#pin_helper /usr/bin/pinwrapper;
pin_helper /usr/bin/bluepin;
# D-Bus PIN helper
#dbus_pin_helper;
}
>> hcidump -X -V
>> bash: hcidump: command not found ## ????
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-08-30 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 19:51 David Armour [this message]
2006-08-30 21:00 ` [Bluez-users] bash: syntax error near unexpected token `newline' Paulo Wollny
[not found] <mailman.44465.1156973920.29847.bluez-users@lists.sourceforge.net>
2006-08-31 6:44 ` [Bluez-users] bash: syntax error near unexpected token `newline', (Paulo Wollny) David Armour
[not found] ` <44F6DCB0.3030400@ibdcon.org.br>
2006-08-31 15:38 ` [Bluez-users] bash: syntax error near unexpected token `newline' David Armour
2006-08-31 18:43 ` redondos
2006-08-31 23:49 ` Paulo Wollny
[not found] <mailman.47971.1157055066.29847.bluez-users@lists.sourceforge.net>
2006-09-01 17:52 ` David Armour
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=44F5EC3D.1050607@shaw.ca \
--to=d.f.armour@shaw.ca \
--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