From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2001-09-19 release of hotplug scripts
Date: Thu, 20 Sep 2001 04:42:43 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100096106319477@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100094690101664@msgid-missing>
> 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\x17679
>
> This release adds ieee1394 support and a try at SuSE support :)
And various bugfixes ... :)
> 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.
To clarify, the ieee1394 support is what needs software that's
as-yet not quite released. Other hotplugging (USB, PCI, network)
still works just fine with 2.4.0 (and, for USB, 2.2.current). The
release is not (as one person suspected :) Science Fiction!
> - Some of the updates from SuSE:
... excluding most of the SuSE-specific admin stuff, so
for now SuSE users will need to get an RPM from SuSE
that knows and uses those hooks. (Much like the way
the Debian and RedHat distros re-use this software.)
I figure converging admin between such distros is not a near
term possibility, but testing for each distro's admin hooks
and then using them is achievable. We're not quite there
yet, but the size of the distro-specific patches should be
shrinking over time ... :)
- Dave
_______________________________________________
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
next prev parent reply other threads:[~2001-09-20 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 0:44 2001-09-19 release of hotplug scripts Greg KH
2001-09-20 4:42 ` David Brownell [this message]
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=marc-linux-hotplug-100096106319477@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 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).