From: Kurt Garloff <garloff@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Announce: modutils 2.4.3 is available
Date: Wed, 28 Feb 2001 00:12:21 +0100 [thread overview]
Message-ID: <20010228001221.P21238@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <3A9A2B3B.421AE7E8@hanse.com> <22995.983227286@ocs3.ocs-net>
In-Reply-To: <22995.983227286@ocs3.ocs-net>; from kaos@ocs.com.au on Tue, Feb 27, 2001 at 09:41:26AM +1100
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Tue, Feb 27, 2001 at 09:41:26AM +1100, Keith Owens wrote:
> On Mon, 26 Feb 2001 11:08:59 +0100,
> Stefan Smietanowski <stefan@hanse.com> wrote:
> >Keith Owens wrote
> >> modutils-2.4.3.tar.gz Source tarball, includes RPM spec file
> >
> >IIRC 2.4.2 was 2.4 only, and was released under protest, is it the same
> >for 2.4.3?
>
> modutils 2.4 will work on kernel 2.0 and libc 5, one of the changes in
> 2.4.3 is for libc5 support. The protest period has expired.
To clearify: The incompatibility only affects the hotplug kernel device
tables ...
As there was no support amongst USB crowds for adding a version info for the
table formats, the modutils-2.4.2 could not provide support for per 2.4.0
kernel hotplug device tables. Nor can 2.4.3. The rest of the functionality
is unaffected.
Keith, correct me if I misunderstood ...
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-02-27 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 4:44 Announce: modutils 2.4.3 is available Keith Owens
2001-02-26 10:08 ` Stefan Smietanowski
2001-02-26 22:41 ` Keith Owens
2001-02-27 23:12 ` Kurt Garloff [this message]
2001-02-28 0:00 ` Building autofs Rainer Mager
2001-02-28 8:33 ` Urban Widmark
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=20010228001221.P21238@garloff.etpnet.phys.tue.nl \
--to=garloff@suse.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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).