All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Announce: modutils 2.4.6 is available
Date: Sun, 06 May 2001 16:02:35 +1000	[thread overview]
Message-ID: <819.989128955@ocs3.ocs-net> (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.6.tar.gz           Source tarball, includes RPM spec file
modutils-2.4.6-1.src.rpm        As above, in SRPM format
modutils-2.4.6-1.i386.rpm       Compiled with egcs-2.91.66, glibc 2.1.2
modutils-2.4.6-1.sparc64.rpm    Not available yet, waiting for a sparc machine.
modutils-2.4.6-1.ia64.rpm       Compiled with gcc 2.96-ia64-000717 snap 001117,
				libc-2.2.1.
patch-modutils-2.4.6.gz         Patch from modutils 2.4.5 to 2.4.6.

Related kernel patches.

patch-2.4.2-persistent.gz       Adds persistent data and generic string
				support to kernel 2.4.2 onwards.  Optional.

Changelog extract

	* Replace uint64_t with u_int64_t for glibc 2.0.  Luis Carlos Yamamoto.
	* /dev/rtc can be a module.  Urs Thuermann.
	* Do not assume that malloc(0) returns a pointer.  Bug report by
	  Kiichiro Naka, different fix by Keith Owens.
	* Cross compile changes.  Maciej W. Rozycki.
	* Better explanation for rmmod -a.   Marc Herbert.
	* Remove modules(2) references.  Debian #69398.
 	* hppa dp is $global$, not data_start.  Richard Hirst.
 	* hppa64 stub for millicode calls must not use dp.  Richard Hirst.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE69Oj4i4UHNye0ZOoRAl/cAJ9Sppko57LNUHb92z01+CUDW7vMHQCff8kF
jOxArOcYlyk9MHHa7vRUS18=
=mWGA
-----END PGP SIGNATURE-----


             reply	other threads:[~2001-05-06  6:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06  6:02 Keith Owens [this message]
2001-05-09  7:03 ` Announce: modutils 2.4.6 is available Keith Owens

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=819.989128955@ocs3.ocs-net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.