From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Small patch for hotplug scripts, success story
Date: Fri, 12 Jan 2001 15:35:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97931362106688@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97929561925475@msgid-missing>
Hi Norbert,
> linux-2.4.0-final + modutils/hotplug patch
> modutils-2.4.1
>
> hotplugging works IF:
>
> * usbmodules is removed: It gives NOTHING! at the moment, at least for
> my devices
Right -- the current version won't understand the 2.4.1 modutils
output, but then its standard install isn't in the path that the
hotplug scripts use.
> * fix in hotplug.function:
> LISTER=`which ${1}modules 2>/dev/null`
> unfortunately if which is /usr/bin/which we get
> LISTER="which: no usbmodules in ...."
> because /usr/bin/which don't write this message to stderr, but stdout.
> Therefor no internal scanning is done and nothing works.
Curious. I didn't see that, but then maybe I'm running with
a "which" command that doesn't have that bug.
> Better would be
> LISTER=`type -p ${1}modules`
> since these scripts are bash and `type' is a buildin.
Sounds good! The fix is now in CVS (at linux-usb for now).
> But after these two changes (remove usbmodules and fix which<->type -p) it
> is working!
Great! Thanks for the confirmation.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-12 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 10:33 Small patch for hotplug scripts, success story Norbert Preining
2001-01-12 15:35 ` David Brownell [this message]
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-97931362106688@msgid-missing \
--to=david-b@pacbell.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 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.