Re: Bug#168848: ITP: FUSD -- a Linux Framework for User-Space Devices
Emile van Bergen wrote:
> 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.
You might want to have a look at FUSE (it's in Debian) which does
precisely that. I used it for some projects and it works quite nicely.
There are even bindings for Python and Perl, though they aren't packaged
yet.
Package: fuse-source
Description: Filesystem in USErspace (source for kernel module)
Simple interface for userspace programs to export a virtual
filesystem to the linux kernel.
.
This package contains the source code for the fuse module. It is
required to use fuse with a self-compiled kernel.
Package: fuse-utils
Description: Filesystem in USErspace (utilities)
Simple interface for userspace programs to export a virtual
filesystem to the linux kernel.
.
This package contains the fusermount utility which is necessary to
mount fuse filesystems.
Package: libfuse-dev
Description: Filesystem in USErspace (development files)
Simple interface for userspace programs to export a virtual
filesystem to the linux kernel.
.
This package contains the files necessary to write applications in C
or C++ using fuse.
--
Roland Bauerschmidt
Reply to: