From owner-freebsd-fs@FreeBSD.ORG Sun Jul 6 23:09:16 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3B7430E for ; Sun, 6 Jul 2014 23:09:16 +0000 (UTC) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 313CB2E99 for ; Sun, 6 Jul 2014 23:09:16 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id k48so3559126wev.6 for ; Sun, 06 Jul 2014 16:09:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=PZV4gRQvxa9chDRVlwAtUVFmCaylWTCHvE7cNYIISHg=; b=o/UFO2w9Q88w1bnFqgOcsBlV40MbYv+J8PiqhdNINHG+gcOWT+lBN5/pBhZ5v0bvyB X50vK0/9cx3H0/4QUCZwuLzU8XkAj+GIKgnDQVj7TvdNEFyJkgY7jYJkzXNms49u3BK8 8UupzrUK5hOIO6ESt6D8IEyqmUmAXgxoSoCV/NnO/J8kuayh89kEbKeLWgWqvwwWrcnY rPY8J13lv/QRv4fNuEsxMJo3tB5dROiX7xb7zRsIUMwf8Y4uY33okx5knnhpj0d3fE39 2xrYz6JnW6tkhpyqel5ZJCb/OyEQVifVrcKkAWxtJP6FSQ/qjBBPtgyNKa09sSZYilCu LNXQ== X-Received: by 10.180.72.43 with SMTP id a11mr33208620wiv.21.1404688154382; Sun, 06 Jul 2014 16:09:14 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id r9sm108037474wia.17.2014.07.06.16.09.12 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Jul 2014 16:09:13 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 7 Jul 2014 01:09:11 +0200 From: Baptiste Daroussin To: Harshavardhana Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <20140706230910.GA8523@ivaldir.etoilebsd.net> References: <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <0F20AEEC-6244-42BC-815C-1440BBBDE664@mail.turbofuzz.com> <20140629203746.GI34108@ivaldir.etoilebsd.net> <1A58F492-946F-46D4-A19E-2734F368CDAC@mail.turbofuzz.com> <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2014 23:09:16 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 06, 2014 at 12:13:15PM -0700, Harshavardhana wrote: > > > > I can make the /usr/local/var/log/glusterfs directory and it gets much = further. That said, is there some special configure flags we should be pa= ssing in our version of the port to properly stuff glusterfs into /var inst= ead? Your email tends to imply that we should be passing =E2=80=94localsta= tedir, which we can certainly do no problem, I=E2=80=99m just wondering if = that=E2=80=99s your long-term plan. Again, this is our port: https://gith= ub.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs > > > > The fundamental issue with /usr/local is, again, that /usr/local is rea= d-only on FreeNAS. If there are configuration files that glusterfs expects= to be modifiable, they can=E2=80=99t live anywhere in /usr/local, nor of c= ourse can any temporary files or log files. We have made special provision= s for /etc and /var such that those can be modified, so we basically just n= eed to compile gluster as a =E2=80=9Csystem service=E2=80=9D and put it in = the system directories (e.g. prefix is /, not /usr/local). > > >=20 > Ah now i get it - "/usr/local" is not a requirement for "GlusterFS" it > is a baggage of using "autotools" when during ./configure if you do > not specify --prefix - so for a standard installation under RPM it is > usually the following flags are used >=20 > # ./configure --prefix=3D/usr --sysconfdir=3D/etc --localstatedir=3D/var > --libdir=3D/usr/lib64 >=20 > Since FreeBSD doesn't need "/usr/lib64" you could just use for packages >=20 > # ./configure --prefix=3D/usr --sysconfdir=3D/etc --localstatedir=3D/var >=20 Here is an updated version of my port http://people.freebsd.org/~bapt/glusterfs.diff This time it passes poudriere (for those not aware of poudriere it is for FreeBSD a bit like what mock is for fedora but on steroid :)) What is new in there: dependency on bison that I missed the first time, a dependency on libexecinfo (on non FreeBSD 10) and a build dependency on git other build-aux/pkg-version is not happily catching the version Tested on FreeBSD 10 regards, Bapt --envbJBWh7q8WU6mo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO51xYACgkQ8kTtMUmk6Ex6zACgh+6z/ECBHd2LlHmCFfuuyqTQ wUIAn18OEXA1pwtiHeVrBVA7fyIBf5Ac =s0+V -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--