public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Obex file transfer from ipaq
Date: Wed, 13 Jul 2005 15:43:30 -0300	[thread overview]
Message-ID: <e1effdeb050713114312e70f9e@mail.gmail.com> (raw)
In-Reply-To: <20050713170258.12182.qmail@web33507.mail.mud.yahoo.com>

Hi Vinod,=20

Use gnome-bluetooth or kdebluetooth.

Other option is use command line app.  There is an email=20
posted in the bluez-users list explaining how receive files.=20
The subject is "OBEX File Receive".

Regards,
Claudio.

On 7/13/05, Vinod <geekvinod@yahoo.com> wrote:
> Hi All.
>=20
> I have ipaq 3870 running familiar linux v0.8.2 with
> kernel 2.4.19. I want to send files to a desktop
> running windows and a usb bluetooth dongle.
>=20
> The bluetooth on my ipaq is detected and i can use
> hcitool to find the other device. My question is how
> to send files from the ipaq to the other bluetooth
> device?
>=20
> I found a page
> http://www.caside.lancs.ac.uk/java_bt.php
>=20
> which uses obex transfer. But a tool they use
> 'ussp-push' is not avialable to install through ipkg
> and i cant compile usng make on my ipaq due to no gcc
> compiler.
> Is there any other way i can do this file transfer?
> I can detect a obex service on the other machine.
>=20
> i installed obexftp_0.10.3-r0_arm.ipk to see if i can
> use this. However i am unure of how to use it.
>=20
> # ipkg install openobex-apps_1.0.0-r0_arm.ipk
> Installing openobex-apps (1.0.0-r0) to root...
> Configuring openobex-apps
> root@h3600:/etc/bluetooth# obexftp
> -sh: obexftp: not found
>=20
> Would appreciate any pointers.
>=20
> Thanks,
> Vinod
>=20
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happen=
ing
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by H=
P,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-07-13 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 17:02 [Bluez-users] Obex file transfer from ipaq Vinod
2005-07-13 18:43 ` Claudio Takahasi [this message]

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=e1effdeb050713114312e70f9e@mail.gmail.com \
    --to=cktakahasi@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