public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] easiest way to get OBEX support (client/server) ?
Date: Sat, 30 Aug 2008 12:50:26 +0200	[thread overview]
Message-ID: <1220093426.7145.86.camel@californication> (raw)
In-Reply-To: <e96e9eeb0808300144y19c285a0l7156e6fb9a415547@mail.gmail.com>

Hi Voni,

> > The current assumption is it runs in the user session and hence
> > requiring a D-Bus session bus. However the end goal is to give the
> > choice to run it at system level if you don't have a fine grained
> > security model anyway.
> >
> > For these case it really helps if you just state what you wanna do with
> > it. Otherwise we will focus on our current plans and do everything else
> > when we have time. Also patches are always welcome.
> 
> I need to be able to demonstrate OBEX profiles on a bluez-based
> embedded system which is very early in its development. No GUI
> whatsover. I only have the shell. I have DBUS obviously (although I
> only run system session currently). It's really important because this
> way managers here will be able to choose between bluez and other
> stacks.

just go into the code and replace SESSION with SYSTEM and create a D-Bus
security policy file for org.openobex.

> I guess that currently my only option is obexftp  ?  Unfortunately it
> doesn't cross compile cleanly.. (I did manage to cross compile
> openobex without a problem though).
> 
> IIRC the obex project in the bluez cvs worked pretty nice on a PC.
> unfortunately we use expat and not libxml so I can't use it on my
> embedded system..

I am not touching that code anymore, but that could be easily fixed :)

You will have to do some development since you can't expect that you can
just take open source stuff without any integration work. And that is
exactly what you have to do, integrate it. If patches come up during
this, then send them upstream and we likely include them and then next
time (next product) the integration work goes down.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-08-30 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 10:49 [Bluez-users] easiest way to get OBEX support (client/server) ? Voni Hakau
2008-08-25 10:56 ` Voni Hakau
2008-08-29 12:13   ` jayjwa
2008-08-30  7:11     ` Voni Hakau
2008-08-30  9:34       ` Marcel Holtmann
2008-08-30  8:44         ` Voni Hakau
2008-08-30 10:50           ` Marcel Holtmann [this message]
2008-08-30  7:16     ` Voni Hakau
2008-08-30  9:30       ` 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=1220093426.7145.86.camel@californication \
    --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