From owner-freebsd-fs@FreeBSD.ORG Fri Apr 18 21:06:00 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 B8322A08 for ; Fri, 18 Apr 2014 21:06:00 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82A7B1FE6 for ; Fri, 18 Apr 2014 21:06:00 +0000 (UTC) Received: from [10.73.160.242] (nat-dip7.cfw-a-gci.corp.yahoo.com [209.131.62.116]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 292151928E0; Fri, 18 Apr 2014 21:05:57 +0000 (UTC) Subject: Re: What happened with the GlusterFS port? From: Sean Bruno To: Marty Rosenberg In-Reply-To: References: <28234312-7982-49F5-83FD-865649AA9CCB@ultra-secure.de> <1397850220.58880.16.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-xtX5v5mWycLZW+DfJ0tb" Date: Fri, 18 Apr 2014 14:05:54 -0700 Message-ID: <1397855154.58880.25.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 21:06:00 -0000 --=-xtX5v5mWycLZW+DfJ0tb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2014-04-18 at 15:05 -0500, Marty Rosenberg wrote: > If you just want to use freebsd as a brick (as I do), I have patches > against 3.3 that enable it to build, and it hasn't lost any data on me > yet, but every once in a while, things get funky. I've been meaning > to upstream the patches *forever*, but I simply haven't gotten around > to it. >=20 >=20 If you feel frisky, grab up what you have and start assembling a port. It shouldn't be too gross, but it would definitely get more eyeballs on the code if its available for easy installation. sean >=20 > On Fri, Apr 18, 2014 at 2:51 PM, Outback Dingo > wrote: > On Fri, Apr 18, 2014 at 3:43 PM, Sean Bruno > wrote: > =20 > > On Fri, 2014-04-18 at 21:30 +0200, Rainer Duffner wrote: > > > Hi, > > > > > > does anybody know where the effort to port GluserFS to > FreeBSD went? > > > > > > There=E2=80=99s this (very) outdated wiki-page: > > > https://wiki.freebsd.org/GlusterFS > > > > > > and there=E2=80=99s the SoC project: > > > https://wiki.freebsd.org/SummerOfCode2013/GlusterFSport > > > > > > But nothing seems to have happened after it was finished. > > > > > > The port made decent progress over the GSOC period, but no, > it never > > gained any traction to end up in the ports collection. > > > > > =20 > not to hijack the thread but, glusters ancient, use riak-cs, > or swift, or > port leofs > =20 > =20 > > sean > > > > > > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to > "freebsd-fs-unsubscribe@freebsd.org" >=20 >=20 --=-xtX5v5mWycLZW+DfJ0tb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTUZOyAAoJEBkJRdwI6BaH0a8H/AltZMi7omHVrcIqManl/opZ JwgzRfHB6Eq1gtc1cDBsKxAR+yQu3tpLS42lw1d9Mw7n/9rz/UghLuBNvm4r42Fu DKYOlXCPhJM6JQNP7kWjahHLozuVWxyusHvQTu6hmVEzvKqISl++ODLCo/LKQ9ol nfiSXN19xvifv4LdjcdSQV/ED1GrAytgnL1JlEmCpvSfrN5WgRY/n8o88FsQKZ8P WhGHQE8Rhnd/2g9yLmAYrqHrrAz4PJerrAu4Jv7pA7T4Gb4z2RkIzxkVTMFJLTXY 1OoBvTjT9pL2XX70QFKcUr9CeT7OVRVtxzf19VtyIBW23rxG7rNewRCdFjaSAus= =Jerv -----END PGP SIGNATURE----- --=-xtX5v5mWycLZW+DfJ0tb--