From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Nicholas A. Preyss" <nalp@gmx.net>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-utils 2.7 default configuration
Date: Thu, 20 May 2004 11:20:34 +0200 [thread overview]
Message-ID: <1085044833.4327.132.camel@pegasus> (raw)
In-Reply-To: <1085044520.28151.1256.camel@hades.cambridge.redhat.com>
Hi David,
> OK, I've moved pand, dund and hidd into separate init scripts for
> Fedora.
>
> Updated bluez-* RPMS for FC2/ppc are in my yum repository at
> ftp://ftp.uk.linux.org/pub/people/dwmw2/fc2-mac/ (for i386 you'll want
> to rebuild them from the SRPMS which are also there). I'll probably push
> those as updates for FC2 too.
many thanks for that.
Besides these, have you checked the Bluetooth CUPS backend, which is
also included in bluez-utils-2.7?
> In fact, I suspect that the right answer for pand is to tie it into the
> initscripts and system-config-network, so you add an interface of type
> 'PAN slave' or 'PAN master' and the network scripts handle starting and
> stopping the daemon like they do ipppd, rather than doing it from a SysV
> init script. I haven't used dund so I'm less sure about that but it
> might also be the right approach there.
I am not a Fedora Core user, so I can't answer this question, but in
general it is up to you to decide.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-20 9:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 19:29 [Bluez-devel] bluez-utils 2.7 default configuration Nicholas A. Preyss
2004-05-12 13:23 ` Marcel Holtmann
2004-05-12 14:18 ` David Woodhouse
2004-05-12 17:20 ` Marcel Holtmann
2004-05-12 17:25 ` David Woodhouse
2004-05-12 17:29 ` Marcel Holtmann
2004-05-12 17:33 ` David Woodhouse
2004-05-12 17:45 ` Marcel Holtmann
2004-05-12 17:56 ` David Woodhouse
2004-05-12 21:50 ` Marcel Holtmann
2004-05-20 9:15 ` David Woodhouse
2004-05-20 9:20 ` Marcel Holtmann [this message]
2004-05-20 9:28 ` David Woodhouse
2004-05-20 9:42 ` Marcel Holtmann
2004-05-20 22:04 ` billy pucyutan
2004-05-30 17:20 ` David Woodhouse
2004-05-31 22:22 ` Marcel Holtmann
2004-05-31 22:43 ` David Woodhouse
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=1085044833.4327.132.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=nalp@gmx.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