I’ve been considering porting PUFFS (NetBSD’s kernel implementation of FUSE) along with reFUSE (the library that goes along with PUFFS) to FreeBSD. I wonder what the interest is in this?
tarfs is still on the plate, but development slowed to a crawl over the last few months as I have joined a startup and it is eating most of my time.
I plan on finishing up tarfs first, then will be looking for another file system related project. I have thought about helping with bluffs also, but that’s not up to me.
I’m the maintainer of the sysutils/fusefs-ntfs (NTFS-3G) port, and it has some serious problems residing in the current fuse4bsd implementation (the author quickly fixed most of the problems that appeared, but now he is very busy at work IIRC). See the fusefs-ntfs/files/README.FreeBSD file, section “Known Problems”.
In short (I’m not a kernel programmer so please excuse me if I made some mistakes in the explanation), as FreeBSD uses vnode based IO and Linux uses full paths, it happens frequently that when a vnode is reused any filesystem using FUSE reports “file not found” or EAGAIN when using the filesystem (not the FUSE one, but the native UFS fs; as the problems is with the vnodes being reused). These problems can make it unusable when doing something else like compiling/extracting. Doing any kind of operations inside the FUSE filesystem does not produce the error, as it uses a user space caching library.
If you make any progress on the port, I would like to hear about it. Also it would be nice if the code could be shared between FreeBSD and NetBSD then.
Sure, that’s really neat one!
what happened to tarfs?
If PUFFS is more stable then FreeBSD’s existing port, and it’s compatible with existing FUSE modules, then thumbs up!
tarfs is still on the plate, but development slowed to a crawl over the last few months as I have joined a startup and it is eating most of my time.
I plan on finishing up tarfs first, then will be looking for another file system related project. I have thought about helping with bluffs also, but that’s not up to me.
Hello.
I’m the maintainer of the sysutils/fusefs-ntfs (NTFS-3G) port, and it has some serious problems residing in the current fuse4bsd implementation (the author quickly fixed most of the problems that appeared, but now he is very busy at work IIRC). See the fusefs-ntfs/files/README.FreeBSD file, section “Known Problems”.
In short (I’m not a kernel programmer so please excuse me if I made some mistakes in the explanation), as FreeBSD uses vnode based IO and Linux uses full paths, it happens frequently that when a vnode is reused any filesystem using FUSE reports “file not found” or EAGAIN when using the filesystem (not the FUSE one, but the native UFS fs; as the problems is with the vnodes being reused). These problems can make it unusable when doing something else like compiling/extracting. Doing any kind of operations inside the FUSE filesystem does not produce the error, as it uses a user space caching library.
If you make any progress on the port, I would like to hear about it. Also it would be nice if the code could be shared between FreeBSD and NetBSD then.
Thanks,
Ale