Re: Bug#168848: ITP: FUSD -- a Linux Framework for User-Space Devices
On Tue, Nov 12, 2002 at 11:29:01PM +0100, Emile van Bergen wrote:
> On Tue, Nov 12, 2002 at 04:34:52PM -0500, Bao C. Ha wrote:
> > FUSD is a Linux framework for proxying device file callbacks
> > into user-space, allowing device files to be implemented by
> > daemons instead of kernel code. Despite being implemented
> > in user-space, FUSD devices can look and act just like any
> > other file under /dev which is implemented by kernel callbacks.
> This is /very/ interesting. Does it also provide such hooks for
> filesystems? It would be great if we could have a way to route pathname
> resolution and the 'canonical' open(), read(), write(), ioctl(), lseek(),
> select(), mmap(), close() API to userspace.
I am not sure if it provides complete hooks for filesystems or
not. I have used it primarily to implement user-space device
drivers for character devices. At a minimum, an user-space device
driver can implement the five basic functionalities: open(),
close(), read(), write() and ioctl(). These user-space devices
can also be polled or selected.
Bao C. Ha
Hacom voice: (310) 675-8221 fax: (310) 675-8225
8D66 6672 7A9B 6879 85CD 42E0 9F6C 7908 ED95 6B38