public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Cox <rcox27@triad.rr.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Hotplug
Date: Sat, 10 Apr 2004 12:16:55 -0400	[thread overview]
Message-ID: <200404101216.55544.rcox27@triad.rr.com> (raw)
In-Reply-To: <1081613051.5398.1.camel@pegasus>

On Saturday 10 April 2004 12:04 pm, Marcel Holtmann wrote:
> Hi Aben,
>
> > > 	I'm trying to get bluez running on my gentoo linux server so I can
> > > connect to my IPaq 2215.  I've got a connection successfully
> > > established, but I'm trying to automate it with hotplug in hopes of
> > > setting up a NAP bridge.  The docs I've found so far are rather unclear
> > > on this subject, but I've created an '/etc/hotplug/bluetooth.agent'
> > > script.  Right now, I'm just trying to get hotplug to call that script
> > > when a connection is established to automatically configure bnep0, but
> > > it only seems to get called on startup when I reboot my kernel.  I had
> > > the impression that 'pand' would emit a hotplug event for bnep0 when a
> > > connection is established, but I'm not so sure now.  Any guidance about
> > > how I might proceed.  Thank you in advance for any information you may
> > > provide.
> >
> > not bluetooth.agent, but net.agent.
> > you need action after creating NET (bnep0)
> >
> > i have iPAQ4155 connected.
> > read thread  "No more bluez.o in 2.6?"
>
> I don't know anything about Gentoo, but for Debian you don't have to
> touch net.agent. Simply put another rule into /etc/network/interfaces.
>
> Regards
>
> Marcel

Marcel,

	Gentoo is somewhat similar.  It does not have an /etc/network/interface, but 
the interfaces are configure in /etc/init.d and /etc/conf.d.  There you 
create an /etc/init.d/net.bnep0 (which is identical to the net.ethx scripts) 
and put the iface info in /etc/conf.d/net.  You are right that I didn't need 
to touch the net.agent script though.  I never realized it was being called 
until Aben informed me.  I will have to create a '/var/lock/subsys/network' 
lockfile somewhere, but at least bnep0 is being configured automatically now.

Regards

Richard


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-04-10 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 15:26 [Bluez-users] Hotplug Richard Cox
2004-04-10 15:47 ` Aben Siatris
2004-04-10 16:04   ` Marcel Holtmann
2004-04-10 16:16     ` Richard Cox [this message]
2004-04-10 16:06   ` Richard Cox
2004-04-10 16:36     ` Aben Siatris
2004-04-10 16:55       ` Richard Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09 14:35 Хедин
2004-06-10 10:22 ` 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=200404101216.55544.rcox27@triad.rr.com \
    --to=rcox27@triad.rr.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