linux-hotplug.vger.kernel.org archive mirror
 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: [ANNOUNCE] 2004-04-01 release of hotplug scripts
Date: Thu, 01 Apr 2004 18:48:52 +0000	[thread overview]
Message-ID: <20040401184852.GA13967@kroah.com> (raw)

I've just packaged up the latest Linux hotplug scripts into a release,
which can be found at:
	kernel.org/pub/linux/utils/kernel/hotplug/hotplug-2004_04_01.tar.gz
or for those who like bz2 packages:
	kernel.org/pub/linux/utils/kernel/hotplug/hotplug-2004_04_01.tar.bz2

As this release was primarily a sync up with a bunch of pending Gentoo
patches, I did not build rpm packages, as there was nothing really new
that any Red Hat user would care much about.  That's also why I didn't
update the sf.net page (besides it being a big pain to do so...)

The main web site for the linux-hotplug project can be found at:
	http://linux-hotplug.sf.net/
which contains lots of documentation on the whole linux-hotplug
process.
 
The release is still backwards compatible with 2.4, so there is no need
to worry about upgrading.

The full ChangeLog extract since the last release is included below for
those who want to know everything that's been changed, and who to blame
for them :)

thanks,

greg k-h

Thu Apr  1 2004 kroah
        - 2004_04_01 release
        - From Martin Hicks <mort@bork.org>
                - fix hotplug.spec file, adding clean rule.
        - Sync up with fixes in Gentoo tree:
                - return proper error value in pci.rc
                - handle system overrides properly in usb.rc
                - handle system overrides properly in usb.agent
                - fix LOADED test in hotplug.functions
                - add ability to start network scripts properly.
                - add ability to stop network scripts properly.

Thu Apr  1 2004 ukai
        - hotplug.functions: $MODULE need s/-/_/g to match with lsmod output
        - usb.agent: use $DEVPATH for $REMOVER if $DEVPATH is defined.
           when coldplugging on 2.6.*, we don't know $DEVICE, but $DEVPATH,
           so $DEVPATH should be used for unique string to device.

Web Mar 31 2004 ukai
        - input.agent: don't try to check empty $dev_bits in input_match_bits
           some posix shell may complain on it.





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2004-04-01 18:48 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=20040401184852.GA13967@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;
as well as URLs for NNTP newsgroup(s).