Date: Sun, 6 Jul 2014 12:13:15 -0700 From: Harshavardhana <harsha@harshavardhana.net> To: Jordan Hubbard <jkh@mail.turbofuzz.com> Cc: freebsd-fs@freebsd.org Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <CAAeUqd3ZoF7XUmLwvL7y_VorO1JfdtVk=RKcW2rVHKdoVOBRAw@mail.gmail.com> In-Reply-To: <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com> References: <C647EDA1-EA93-4A66-B59D-3B5F959DC0E0@gluster.org> <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> <CAAeUqd0=CdwaVjZjUc4PKxD_gxpydVqCy4tebywi=iV3gkpz1Q@mail.gmail.com> <1A58F492-946F-46D4-A19E-2734F368CDAC@mail.turbofuzz.com> <CAAeUqd1m_FxPWCVft5tmeok8QFsEZWGM-5QV20=mq8MeU=7EbA@mail.gmail.com> <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I can make the /usr/local/var/log/glusterfs directory and it gets much fu= rther. That said, is there some special configure flags we should be pass= ing in our version of the port to properly stuff glusterfs into /var instea= d? Your email tends to imply that we should be passing =E2=80=94localstate= dir, which we can certainly do no problem, I=E2=80=99m just wondering if th= at=E2=80=99s your long-term plan. Again, this is our port: https://github= .com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs > > The fundamental issue with /usr/local is, again, that /usr/local is read-= only on FreeNAS. If there are configuration files that glusterfs expects t= o be modifiable, they can=E2=80=99t live anywhere in /usr/local, nor of cou= rse can any temporary files or log files. We have made special provisions = for /etc and /var such that those can be modified, so we basically just nee= d to compile gluster as a =E2=80=9Csystem service=E2=80=9D and put it in th= e system directories (e.g. prefix is /, not /usr/local). > 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 # ./configure --prefix=3D/usr --sysconfdir=3D/etc --localstatedir=3D/var --libdir=3D/usr/lib64 Since FreeBSD doesn't need "/usr/lib64" you could just use for packages # ./configure --prefix=3D/usr --sysconfdir=3D/etc --localstatedir=3D/var --=20 Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAeUqd3ZoF7XUmLwvL7y_VorO1JfdtVk=RKcW2rVHKdoVOBRAw>