public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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-09-19 release of hotplug scripts
Date: Wed, 19 Sep 2001 17:44:02 -0700	[thread overview]
Message-ID: <20010919174402.A17423@kroah.com> (raw)
In-Reply-To: <20010424124116.A13291@kroah.com>
In-Reply-To: <20010424124116.A13291@kroah.com>

I've just packaged up the latest Linux hotplug scripts into a release,
which can be found at:
	http://sourceforge.net/project/showfiles.php?group_id=17679

This release adds ieee1394 support and a try at SuSE support :)

Here's the full changelog:
	- Added ieee1394.agent from Kristian Hogsberg
	  <hogsberg@users.sourceforge.net>
	- with docs, "sh -x" debug support, minor fix.  Needs kernel
	  2.4.10 and modutils 2.4.9 to hotplug.
	- Some of the updates from SuSE:
		* add/use debug_msg macro in hotplug_functions
		modprobe -s (to syslog)
		* various agent tweaks/fixes
		* more usb.handmap entries (from usbmgr)
	- Added the fxload program
	- Rework root makefile and hotplug.spec to install in prefix
	  location without need of spec file for install.
	- Added installation directions to make the /var/run/usb
	  directory, and updated the rpm spec file to match.
	- added half of Stephen Williams <steve@icarus.com> REMOVER
	  patch. It is up to the install script to create the
	  /var/run/usb directory.  Something like the following would be
	  enough:
	  	mkdir /var/run/usb
		chmod 0700 /var/run/usb

Thanks,

greg k-h

  reply	other threads:[~2001-09-20  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 19:41 2001-04-24 release of hotplug scripts Greg KH
2001-09-20  0:44 ` Greg KH [this message]
2001-09-20  4:42   ` 2001-09-19 " David Brownell
2001-09-20  5:41     ` Ryan W. Maple

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=20010919174402.A17423@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