From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Price <anprice@redhat.com>
Date: Sun, 17 Feb 2013 14:08:35 +0000
Subject: [Cluster-devel] Heads-up: retiring gfs_controld
In-Reply-To: <511FB556.9070301@redhat.com>
References: <511E35AC.1060306@redhat.com> <511FB556.9070301@redhat.com>
Message-ID: <5120E463.4020208@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On 16/02/13 16:35, Fabio M. Di Nitto wrote:
> On 02/15/2013 02:18 PM, Andrew Price wrote:
>> Hi,
>>
>> Now that Fedora 16 has EOL'd we have little reason to keep gfs_controld
>> and gfs_control in gfs2-utils. They're currently disabled by default but
>> can be enabled with configure option --enable-gfs_controld which adds
>> additional dependencies on corosynclib, clusterlib (discontinued) and
>> openaislib (discontinued).
>>
>> My intention is to remove gfs_control* from gfs2-utils.git before the
>> next release unless there are any good reasons to keep them around.
>>
>> Andy
>>
>
> Just make sure it is clear from which exact kernel version it is
> possible to operate without gfs_control*. so that maintainers will not
> try to backport to linux 1.0.
>
> Fabio

I'd have to get confirmation on this but it looks like this commit 
obsoleted gfs_controld:

    commit e0c2a9aa1e68455dc3439e95d85cabcaff073666
    Author: David Teigland <teigland@redhat.com>
    Date:   Mon Jan 9 17:18:05 2012 -0500

        GFS2: dlm based recovery coordination

        This new method of managing recovery is an alternative to
        the previous approach of using the userland gfs_controld.
    [...]

Which was released in:

    $ git describe --contains e0c2a9aa1e68455dc3439e95d85cabcaff073666
    v3.3-rc1~77^2~4

So a little while after linux 1.0 :)

Andy