public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Moskowitz <rgm@htt-consult.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Centos/RHEL has old version of Bluez -- what to do?
Date: Mon, 14 Jul 2008 14:18:12 -0600	[thread overview]
Message-ID: <487BB484.2010503@htt-consult.com> (raw)
In-Reply-To: <487B6E48.70807@htt-consult.com>

Robert Moskowitz wrote:
> I am using Centos 5.2.  It has bluez-utils-3.7-2*
>   
And now I realize that there are bluez kernel modules. And I can expect 
that to move to anything more recent (and stable) with bluez, would 
require a kernel compile. Not something I woudl attempt.

argh.
> I realize this is quite old and I have a lot of bluetooth plans.
>
> I would like to update to a more current bluez version, but have a 
> number of concerns.  Like the impact on my other bluez rpms:
>
> bluez-gnome-0.5-5.fc6.i386.rpm
> bluez-hcidump-1.32-1.i386.rpm
> bluez-libs-3.7-1.i386.rpm
> bluez-utils-3.7-2.el5.centos.i386.rpm
> bluez-utils-cups-3.7-2.el5.centos.i386.rpm
> gnome-bluetooth-0.7.0-10.2.el5.i386.rpm
> gnome-bluetooth-libs-0.7.0-10.2.el5.i386.rpm
>
>
> I suppose if I knew what I was doing enough to rebuild all these rpms, I 
> could get this to work.  So I have a few questions:
>
> I want to use Asterisk's chan_mobile that pairs the system to a 
> bluetooth phone for a cellular trunk.
> I want to run a PAN.
> I want a Bluetooth headset for my SIP phone and stereo for my  mp3 playing.
>
> Given these modest wants:
>
> Will it work with bluez 3.7?
> Will it be hard to get it to work and keep working with 3.7?
> Has anyone built more current rpms for Centos 5.2?
> Is anyone willing to help me built more current rpms for Centos 5.2?
>
> Thanks and good day to you all!
>
>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>   

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2008-07-14 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 15:18 [Bluez-users] Centos/RHEL has old version of Bluez -- what to do? Robert Moskowitz
2008-07-14 20:18 ` Robert Moskowitz [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=487BB484.2010503@htt-consult.com \
    --to=rgm@htt-consult.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