From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19-rc6-rt3, yum repo
Date: Fri, 17 Nov 2006 21:03:57 +0100 [thread overview]
Message-ID: <20061117200357.GA736@elte.hu> (raw)
i've released the 2.6.18-rc6-rt3 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
the -rt YUM repository for Fedora Core 6 can be activated via:
cd /etc/yum.repos.d
wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
yum update kernel
lots of fixes since -rt0. The latency tracer got more modularized, now
event tracing, function tracing and latency timing/tracing can be
selected independently as well.
to build a 2.6.19-rc6-rt3 tree, the following patches should be applied:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.bz2
http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.19-rc6.bz2
http://redhat.com/~mingo/realtime-preempt/patch-2.6.19-rc6-rt3
as usual, bugreports, fixes and suggestions are welcome,
Ingo
next reply other threads:[~2006-11-17 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 20:03 Ingo Molnar [this message]
2006-11-18 12:31 ` 2.6.19-rc6-rt3, yum repo Michal Schmidt
2006-11-18 13:49 ` Ingo Molnar
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=20061117200357.GA736@elte.hu \
--to=mingo@elte.hu \
--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).