From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging with current modutils and usbdcvs
Date: Tue, 09 Jan 2001 07:37:18 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97902592423278@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97899764909044@msgid-missing>
Miles Lane wrote:
> David Brownell wrote:
>
>> I suspect this is the problem where "usbutils" hasn't
>> yet been updated to understand what modutils 2.4.1 is
>> writing out ...
>>
>> If you update that, you might want to figure out where
>> to install "usbmodules": /usr/local/sbin was where it
>> landed on my system, but that's not one of the normal
>> places to find things run by sysadmin scripts.
>
>
> Where do I get an up-to-date usbmodules? I've never had
> such a utility and don't find it in the hotplug tar file
> you posted.
After a bit of hunting around, I found that usbmodules
comes from usbutils. I went to the usbutils home page:
http://libusb.sourceforge.net/
But, the newest version of the package posted there is:
usbutils-0.7.tar.gz 03-Nov-2000 17:51
I doubt this is what I need for testing.
Pointers to the right stuff?
Miles
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-09 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:14 [linux-usb-devel] Re: hotplugging with current modutils and usbdcvs David Brownell
2001-01-08 23:24 ` David Brownell
2001-01-09 7:22 ` Miles Lane
2001-01-09 7:37 ` Miles Lane [this message]
2001-01-09 7:50 ` Norbert Preining
2001-01-09 8:08 ` Miles Lane
2001-01-09 8:18 ` Norbert Preining
2001-01-09 8:18 ` Miles Lane
2001-01-09 8:22 ` Miles Lane
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=marc-linux-hotplug-97902592423278@msgid-missing \
--to=miles@megapathdsl.net \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).