From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: Announce: kdb v2.2 is available for kernel 2.4.19-rc1
Date: Wed, 10 Jul 2002 09:40:28 +1000 [thread overview]
Message-ID: <31535.1026258028@ocs3.intra.ocs.com.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
ftp://oss.sgi.com/projects/kdb/download/v2.2/
kdb-v2.2-2.4.19-rc1-common-1.bz2
kdb-v2.2-2.4.19-rc1-i386-1.bz2
Starting with kdb v2.0 there is a common patch against each kernel which
contains all the architecture independent code plus separate architecture
dependent patches. Apply the common patch for your kernel plus at least
one architecture dependent patch, the architecture patches activate kdb.
The naming convention for kdb patches is :-
vx.y The version of kdb. x.y is updated as new features are added to kdb.
- -v.p.s The kernel version that the patch applies to. 's' may include -pre,
-rc or whatever numbering system the kernel keepers have thought up this
week.
- -common The common kdb code. Everybody needs this.
- -i386 Architecture dependent code for i386.
- -ia64 Architecture dependent code for ia64, etc.
- -n If there are multiple kdb patches against the same kernel version then
the last number is incremented.
To build kdb for your kernel, apply the common kdb patch which is less
than or equal to the kernel v.p.s, taking the highest value of '-n'
if there is more than one. Apply the relevant arch dependent patch
with the same value of 'vx.y-v.p.s-', taking the highest value of '-n'
if there is more than one.
For example, to use kdb v2.2 for i386 on kernel 2.4.19-rc1, apply
kdb-v2.2-2.4.19-rc1-common-<n> (use highest value of <n>)
kdb-v2.2-2.4.19-rc1-i386-<n> (use highest value of <n>)
in that order.
Changelog extracts.
common
2002-07-09 Keith Owens <kaos@sgi.com>
* Upgrade to 2.4.19-rc1.
* Add dmesg command.
* Clean up copyrights, Eric Sandeen.
* kdb v2.2-2.4.19-rc1-common-1.
i386
2002-07-09 Keith Owens <kaos@sgi.com>
* Upgrade to 2.4.19-rc1.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE9K3Rri4UHNye0ZOoRAggaAJ4le5YLWqMju1okBHGZFYlI5CeyvACg6c8x
EcJU6z5UptMlTt332yZAOlc=
=Vhs9
-----END PGP SIGNATURE-----
reply other threads:[~2002-07-09 23:37 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=31535.1026258028@ocs3.intra.ocs.com.au \
--to=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--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®