Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Mar 2007 20:10:05 +0200
From:      Ivan Voras <ivoras@fer.hr>
To:        freebsd-fs@freebsd.org
Subject:   Re: TDFS ... or other distributed file system technologies   for FreeBSD?
Message-ID:  <eubmlt$fgp$1@sea.gmane.org>
In-Reply-To: <45CCECCB7ECB612F504211F3@ganymede.hub.org>
References:  <4746DA006C148BC0FF1241C6@ganymede.hub.org>	<euberg$f1u$1@sea.gmane.org> <45CCECCB7ECB612F504211F3@ganymede.hub.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig28E7029D3A88E3EFA082ACAC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Marc G. Fournier wrote:

> 'k ... now, you have a 'proof-of-concept' already, using FUSE ... how m=
uch more=20
> would be involved in the kernel module?

Much more. Currently, I know only the very basics of the VFS system.

> I'm just wondering if it would be time better spent polishing off the F=
USE=20
> implementation and pushing that for now, get ppl deploying it, testing =
it, etc=20
> ... and then work on the 'performance enhanced kernel module'?

If time to deployment is in question, TDFS is the way to go, and this
would be what I prefer. Another idea of mine for this is that maybe they
could be made compatible in the network protocol... lots of ideas,
little time.

> Then again, from the other side of the coin ... what are the chances th=
at a=20
> kernel module would get into the main stream distribution vs the FUSE m=
odule?

Since FUSE is (L)GPL'ed, chances of getting it into base are slim. Then
there's the question of who would be responsible for it, since the
developer of the FUSE BSD module was also a SoC student and I don't know
if he's interested in maintaining it that way - I'll go ask him.

> As a stop-gap, have you considered submitting a TDFS port, to give it a=
 bit=20
> more profile?

That is a good idea, I'll try to do it soon. (though it's not
complicated to compile & try it by hand).



--------------enig28E7029D3A88E3EFA082ACAC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGCV39ldnAQVacBcgRAuLcAJ4iQMc1jiOrZFpE3dJ9IpTm0UAq7QCdG54V
0UdLCuj04MRxcj00wpBmCE4=
=TizQ
-----END PGP SIGNATURE-----

--------------enig28E7029D3A88E3EFA082ACAC--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eubmlt$fgp$1>