public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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:42:34 +0200	[thread overview]
Message-ID: <1085046154.4327.147.camel@pegasus> (raw)
In-Reply-To: <1085045305.28151.1269.camel@hades.cambridge.redhat.com>

Hi David,

> It's in the bluez-utils-cups RPM. I haven't tried it as I have no
> suitable hardware. We only have the client side implemented, don't we --
> I can't emulate it by using another Linux/BlueZ box as the 'printer'?

that is great. A "server side" is on my todo list, but I haven't written
any line of code so far.

> I note it doesn't actually try very hard to find printers :)

You have to give the right URI. For example for a printer with Bluetooth
address 00:90:02:63:e0:83 it is bluetooth://00900263E083/

> > > 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.
> 
> That's not really distro-specific. Well, the precise details of the
> implementation might be -- but the idea that it's done in network
> configuration and started like pppd on 'ifup', rather than by init like
> a system daemon, isn't. 

For pand you simply start it and let the IP assignment done by the
network hotplugging. For dund this is done by your pppd scripts. So no
IP configuration has to be done in the init scripts, but you have to
start the daemons somewhere. Otherwise you won't get the SDP entries and
so nobody can find your service.

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

  reply	other threads:[~2004-05-20  9:42 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
2004-05-20  9:28                   ` David Woodhouse
2004-05-20  9:42                     ` Marcel Holtmann [this message]
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=1085046154.4327.147.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