Date: Tue, 26 Oct 2010 09:00:35 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-arch@freebsd.org Cc: Kostik Belousov <kostikbel@gmail.com>, Ivan Voras <ivoras@freebsd.org> Subject: Re: Importing the fusefs kernel module? Message-ID: <201010260900.35059.hselasky@c2i.net> In-Reply-To: <20101025211904.GM2392@deviant.kiev.zoral.com.ua> References: <ia4qnl$bgl$1@dough.gmane.org> <20101025211904.GM2392@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 25 October 2010 23:19:04 Kostik Belousov wrote: > On Mon, Oct 25, 2010 at 10:53:08PM +0200, Ivan Voras wrote: > > Fusefs is the Linux-developed userland filesystem interface which is > > fairly popular in the wild, especially with the "sshfs" module which > > allows mounting of generic ssh/sftp directories in a very easy way. > > > > It was developed in one of the very early Google Summer of Code projects > > (2005) and is now in a bit unusual situation: > > > > 1) it *is* popular, as reports about its breakage arrive pretty soon > > after it breaks > > > > 2) it is currently practically unmaintained. The source code archive is > > from 2008 and the port contains a dozen patches to be applied to it to > > make it work on recent systems > > > > 3) it is also not exactly rock stable, though this has improved with the > > above patches; personally I'd judge it to be as stable as ZFS was two > > years ago so there :) > > > > I'm proposing to import the kernel module into the official tree (there > > are also userland libraries under the GPL; they will stay as ports). > > There are no license conflicts for the kernel module. I see two benefits > > from it: > > > > 1) it will finally integrate the patches needed for it to work in one > > tree and provide the "one official place" to work on it > > > > 2) it will be easier to maintain it here, and changes to the VFS APIs > > would be applied to it in sweeping commits together with other file > > systems. > > > > I'm not knowledgeable enough to actively work on it (yet) but I can > > mechanically maintain it and generally take care of it. > > > > 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. FYI: There also exists a project called cuse4bsd. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010260900.35059.hselasky>