On Tuesday, August 14, 2012 at 14:30 PM, Matt Joyce wrote: > I have to ask. Wasn't FUSE designed to do alot of this stuff? It is > userspace and it doesn't do nasty stuff to file systems. Why aren't we going > that route? Fuse was really designed for the opposite scenario. Fuse "modules" run as daemons, they're not libraries. These daemons attach to a character device and map userspace code into the VFS. Instead, we want to access a filesystem from userspace code. It is a shame, however, because you're right… there is plenty of code there that knows how to read filesystems in userspace. Unfortunately, the FUSE design really doesn't do us any favors.
That said, there are some crazy options to fix that. One could theoretically replace the FUSE character device with one that spoke to userspace processes, instead of interacting with the VFS. There has even been work into creating user-space character devices. One could also make FUSE work with Unix sockets as an alternative to character devices… None of this is out of the box, tested, or even in existence... Regards, Eric Windisch
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
