From: Greg KH <greg@kroah.com>
To: linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
Linux-usb-users@lists.sourceforge.net
Subject: 2001-02-14 release of hotplug scripts
Date: Wed, 14 Feb 2001 15:49:16 -0800 [thread overview]
Message-ID: <20010214154916.A13258@kroah.com> (raw)
I've just packaged up the latest hotplug scripts into a release, and
they can be found at:
http://download.sourceforge.net/linux-hotplug/hotplug-2001_02_14.tar.gz
http://download.sourceforge.net/linux-hotplug/hotplug-2001_02_14-1.noarch.rpm
http://download.sourceforge.net/linux-hotplug/hotplug-2001_02_14-1.src.rpm
depending on which format you prefer.
Changes in this version from the last release are:
- rpm makes the subsystem scripts executable
- some logging fixes
- insistence on having a writable /tmp so bash works properly
- added support for pcimodules
- Fixes some problems seen with Redhat 7 systems when the
partial USB setup in /etc/rc.sysinit was not disabled. The
failure mode was that all USB modules got loaded, rather than
only modules for the devices that were connected.
- In conjunction with the "usbmodules" and "pcimodules" patches
to "usbutils-0.7" and "pciutils-2.1.8", devices that are
connected at boot time will also be configured. If you don't
have those utilities, you'll need to plug USB and CardBus
devices in after the system is booted, otherwise they can't be
properly configured.
- other small fixes.
If you haven't patched your version of usbutils and pciutils, you can
get the patch at:
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m=98141435915986&w=2
Hopefully updated versions of these two packages will be released with
these changes in them soon.
thanks,
greg k-h
--
greg@(kroah|wirex).com
reply other threads:[~2001-02-14 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010214154916.A13258@kroah.com \
--to=greg@kroah.com \
--cc=Linux-usb-users@lists.sourceforge.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@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