From: Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster 3.0.7 stable release
Date: Tue, 12 Jan 2010 15:10:18 +0100 [thread overview]
Message-ID: <1263305418.21303.14.camel@marc> (raw)
In-Reply-To: <4B4C5A0A.6010203@redhat.com>
Hello Fabio,
hello list,
Am Dienstag, den 12.01.2010, 12:16 +0100 schrieb Fabio M. Di Nitto:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The cluster team and its community are proud to announce the 3.0.7
> stable release from the STABLE3 branch.
>
> This release contains a few major bug fixes. We strongly recommend
> people to update your clusters.
>
> In order to build/run the 3.0.7 release you will need:
>
> - - corosync 1.2.0
> - - openais 1.1.1
> - - linux kernel 2.6.31
gfs-kernel doesn't build against 2.6.32 without the following (untested)
change:
sed 's/generic_file_aio_write_nolock/blkdev_aio_write/' \
-i gfs-kernel/src/gfs/ops_file.c
But i don't know if this change is the right thing to do...
--8<--
>
> Under the hood (from 3.0.6):
>
--8<--
> Fabio M. Di Nitto (15):
--8<--
> gfs: disable gfs kernel and userland tool build by default
This one caught my attention...
Is porting of gfs-kernel to latest vanilla kernel still in progress or
is gfs1 going to be abandoned anytime soon?
Some quick and dirty testing with gfs2 went fine so far.
Thanks,
Marc
next prev parent reply other threads:[~2010-01-12 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 11:16 [Cluster-devel] Cluster 3.0.7 stable release Fabio M. Di Nitto
2010-01-12 14:10 ` Marc [this message]
2010-01-12 14:24 ` Fabio M. Di Nitto
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=1263305418.21303.14.camel@marc \
--to=cluster-devel@redhat.com \
/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).