From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Announce: modutils 2.4.18 is available
Date: Mon, 22 Jul 2002 17:45:47 +1000 [thread overview]
Message-ID: <29877.1027323947@kao2.melbourne.sgi.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.4
modutils-2.4.18.tar.gz Source tarball, includes RPM spec file
modutils-2.4.18-1.src.rpm As above, in SRPM format
modutils-2.4.18-1.i386.rpm Compiled with gcc 2.96 20000731,
glibc 2.2.2.
modutils-2.4.18-1.ia64.rpm Compiled with gcc 2.96-ia64-20000731,
glibc-2.2.3.
patch-modutils-2.4.18.gz Patch from modutils 2.4.17 to 2.4.18.
Changelog extract
* Optionally only check the numeric part of the kernel and module
version, insmod -N. This option is always set for kernel >= 2.5, it
defaults to off for earlier kernels.
This change should have been in modutils 2.4.17 but it slipped through
my TODO list. This patch goes with the 2.5 kernel change
http://marc.theaimsgroup.com/?l=linux-kernel&m=102595659604735&w=2
Checking the complete version string (including EXTRAVERSION) is a
waste of time. For historical reasons, insmod only checks the first
32 characters of the version string, many users have longer version
strings. Users make significant changes to their config and kernel but
do not change the version string, as a test for compatibility this is
pointless. Above all, storing the full string in kernel module.h
forces a complete rebuild when you change one character in
EXTRAVERSION. So you have a test that is incomplete, unreliable and
has horrible side effects, time to kill it.
As always, the default for modutils on stable kernels is no change to
existing behaviour, unless the user requests it.
For kernel 2.5 and later, insmod only checks the numeric version
number. With modutils 2.4.18 and the above kernel patch, changing
EXTRAVERSION no longer forces a complete kernel rebuild.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE9O7gqi4UHNye0ZOoRAjxdAKCB7UZxLxexChP0y+3nFquk0VubKQCgsLnp
L9FoBM+sIAqWvvf1IOTL0HM=
=4VET
-----END PGP SIGNATURE-----
next reply other threads:[~2002-07-22 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 7:45 Keith Owens [this message]
2002-07-22 15:34 ` Kai Germaschewski
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=29877.1027323947@kao2.melbourne.sgi.com \
--to=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
all inboxes | Powered by JetHome®