Date: Wed, 13 Feb 2008 18:26:16 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-fs@freebsd.org Cc: freebsd-arch@freebsd.org Subject: FUSE/libfolly (was: Re: [RFC] Remove NTFS kernel support) Message-ID: <fov97k$70n$1@ger.gmane.org> In-Reply-To: <20080212190207.GB49155@beastie.creo.hu> References: <3bbf2fe10802061700p253e68b8s704deb3e5e4ad086@mail.gmail.com> <70e8236f0802070321n9097d3fy1b39f637b3c2a06@mail.gmail.com> <slrnfqrp6g.i6j.csaba-ml@beastie.creo.hu> <867ihdc34c.fsf@ds4.des.no> <20080212190207.GB49155@beastie.creo.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
Csaba Henk wrote: > Well, I just started to work on a from scratch FUSE daemon library. > > The story is as follows: I wanted to put together a FUSE interface to > sysctls, and I started it from scratch (so that it shall be clean > licensing-wise, and for the fun of it). Then as things evolved, the > generic code was distilled out to a library I named "folly", while the > actual work on the sysctl fs has stalled. As a proof-of-concept I also > wrote an userspace nullfs using libfolly. > > So I think: fuse4bsd (ie, the kld + the mount util) + libfolly + sysctl > fs could go to base under BSD license. It also might make sense to rebase > ntfs-3g atop of folly -- although it won't help ntfs-3g being GPL'd. Just for clarification: libfolly is the userland part to the kernel fuse4bsd interface; it implements the original FUSE API? So, in general, it should allow the use of 3rd party FUSE components by changing "-lfuse" to "-lfolly"? (what about include files?) Offtopic: Have you seen NetBSD's PUFFS?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fov97k$70n$1>