Date: Tue, 26 Oct 2010 00:19:04 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: Importing the fusefs kernel module? Message-ID: <20101025211904.GM2392@deviant.kiev.zoral.com.ua> In-Reply-To: <ia4qnl$bgl$1@dough.gmane.org> References: <ia4qnl$bgl$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--2EBbOLNpWrgl9Xdv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 25, 2010 at 10:53:08PM +0200, Ivan Voras wrote: > Fusefs is the Linux-developed userland filesystem interface which is=20 > fairly popular in the wild, especially with the "sshfs" module which=20 > allows mounting of generic ssh/sftp directories in a very easy way. >=20 > It was developed in one of the very early Google Summer of Code projects= =20 > (2005) and is now in a bit unusual situation: >=20 > 1) it *is* popular, as reports about its breakage arrive pretty soon=20 > after it breaks >=20 > 2) it is currently practically unmaintained. The source code archive is= =20 > from 2008 and the port contains a dozen patches to be applied to it to=20 > make it work on recent systems >=20 > 3) it is also not exactly rock stable, though this has improved with the= =20 > above patches; personally I'd judge it to be as stable as ZFS was two=20 > years ago so there :) >=20 > I'm proposing to import the kernel module into the official tree (there= =20 > are also userland libraries under the GPL; they will stay as ports).=20 > There are no license conflicts for the kernel module. I see two benefits= =20 > from it: >=20 > 1) it will finally integrate the patches needed for it to work in one=20 > tree and provide the "one official place" to work on it >=20 > 2) it will be easier to maintain it here, and changes to the VFS APIs=20 > would be applied to it in sweeping commits together with other file syste= ms. >=20 > I'm not knowledgeable enough to actively work on it (yet) but I can=20 > mechanically maintain it and generally take care of it. >=20 > Objections? This is not going to work. The code is unmaintained. Committing it into the src/ just makes the pile of not working code in src/ bigger. --2EBbOLNpWrgl9Xdv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAkzF9EgACgkQC3+MBN1Mb4gVngCg9YXz6HPSYCEMqquDuCAD1tw4 AXAAoJ1/GGPBHAQu6RF/Z0a3hCEeuOxV =zdAf -----END PGP SIGNATURE----- --2EBbOLNpWrgl9Xdv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101025211904.GM2392>