All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Taylor <cht@imipolex-g.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] D-Link DWB-120M and BlueZ 2.14
Date: Fri, 28 Jan 2005 18:31:58 -0800	[thread overview]
Message-ID: <200501290231.ALR00339@ms12.netsolmail.com> (raw)

>
>it will be installed into /etc/hotplug/usb/ and you need a working and
>up-to-date hotplug to make this working.

Thanks for your help. Nothing got installed into /etc/hotplug/usb. Can I 
just manually copy somethng from bluez-utils-2.14/extra into there, like 
bcm203x.usermap? I can't figure out where it should go.

My /etc/rc.d/rc.hotplug says this at the top:
# $Id: hotplug,v 1.3 2002/12/03 02:01:48 dbrownell Exp $

Is that too old?

------------------
Chris Taylor
cht@imipolex-g.com
Los Angeles


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2005-01-29  2:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  2:31 Chris Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31  8:06 [Bluez-users] D-Link DWB-120M and BlueZ 2.14 Chris Taylor
2005-01-30 20:46 Chris Taylor
2005-01-30 20:58 ` Marcel Holtmann
2005-01-30 19:48 Chris Taylor
2005-01-30 19:52 ` Marcel Holtmann
2005-01-29  1:28 Chris Taylor
2005-01-29  1:36 ` Marcel Holtmann
2005-01-28 21:51 Chris Taylor
2005-01-29  1:13 ` 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=200501290231.ALR00339@ms12.netsolmail.com \
    --to=cht@imipolex-g.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.