From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] mount.gfs2 obsolete upstream (scheduled to be removed)
Date: Wed, 10 Aug 2011 14:43:32 +0200 [thread overview]
Message-ID: <4E427CF4.3040701@redhat.com> (raw)
In-Reply-To: <1312978592.2765.7.camel@menhir>
On 08/10/2011 02:16 PM, Steven Whitehouse wrote:
> Hi,
>
> Just a reminder that when Fedora 14 is no longer being updated, we
> intend to remove mount.gfs2 from the upstream gfs2-utils source. There
> should be no user visible changes beyond the removal of the utility when
> this happens as kernels and gfs2_controld have been able to use the new
> system for mounting for some time.
>
> So this is just a heads up so that it isn't too much of a surprise when
> it happens in a few months time.
>
> Also scheduled for removal are gfs2_quota and gfs2_tool. Both of these
> will be removed shortly after Fedora 17 is released. They are both
> considered obsolete and alternatives have been available for some time.
> In the case of gfs2_quota, that means the generic quota package that is
> supplied with Fedora. In the case of gfs2_tool, that means tunegfs2 or
> mount options, depending on which feature is required.
>
> If there are any questions, please let us know,
>
> Steve.
>
>
It might be a good idea to lay down a map of upstream versions required
to drop mount.gfs2 and quota.
New gfs2-utils without mount.gfs2 requires kernel > x.y.z and
gfs_controld > a.b.c. (we ship gfs_controld from gfs2-utils, but people
might still have old versions around... just in case)
similar for quota support.. is a new quota-tools version required?
kernel? etc.
Mapping to fedora releases is only helpful to fedora users :) but it
leaves other distros in the dark. Specially if some features are working
in fedora only by meaning of local patches.
Cheers
Fabio
next prev parent reply other threads:[~2011-08-10 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 12:16 [Cluster-devel] mount.gfs2 obsolete upstream (scheduled to be removed) Steven Whitehouse
2011-08-10 12:43 ` Fabio M. Di Nitto [this message]
2011-08-10 13:26 ` Steven Whitehouse
2011-08-10 15:42 ` 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=4E427CF4.3040701@redhat.com \
--to=fdinitto@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).