From: valen willie <valen.willie@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] New User
Date: Wed, 28 Sep 2005 01:34:29 +1000 [thread overview]
Message-ID: <d73fa6c30509270834679fe3e1@mail.gmail.com> (raw)
In-Reply-To: <20050927095829.41367ac0@nim.leo>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Gee,
THanks Paul...THat was a fast reply from you
now I got my device up and working
Next, I have to buy another bluetooth device set so I can start my
experiment with it.
Gotta keep in touch!
On 9/27/05, Paul LeoNerd Evans <leonerd@leonerd.org.uk> wrote:
>
> On Tue, 27 Sep 2005 16:18:09 +1000
> valen willie <valen.willie@gmail.com> wrote:
>
> > Hi,
> >
> > I just bought myself a USB Bluetooth Adapter.
> > I'm very new to Bluetooth and intend to learn more about it.
> > I'm using Slackware 10.1.
> > I have bluez module loaded automatically when I plug in my bluetooh
> > adapter into my USB port.
> > But then, what should I do, what application should I start or install
> > now to utilize my bluetooth adapter?
>
> Well, it'll depend on your distro. One tool you might find useful
> initially is "hcitool"; it does some initial diagnostics...
>
> $ hcitool devices
> Devices:
> hci0 00:07:61:19:7A:BA
>
> $ hcitool scan
> Scanning ...
> 00:02:EE:C6:41:B2 LeoPhone
>
> hcitool --help for a full list.
>
> I run debian, and this program is provided by the bluez-utils package;
> but other distros may vary.
>
> --
> Paul "LeoNerd" Evans
>
> leonerd@leonerd.org.uk
> ICQ# 4135350 | Registered Linux# 179460
> http://www.leonerd.org.uk/
>
>
>
[-- Attachment #2: Type: text/html, Size: 2027 bytes --]
next prev parent reply other threads:[~2005-09-27 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 6:18 [Bluez-users] New User valen willie
2005-09-27 8:58 ` Paul LeoNerd Evans
2005-09-27 15:34 ` valen willie [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-02 16:48 [Bluez-users] new user Anas koara
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=d73fa6c30509270834679fe3e1@mail.gmail.com \
--to=valen.willie@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).