Hi Miklos,
Can you clarify how the new fuseblk filesystem type differs in
functionality from the usual fuse filesystem type?
The patch description says that the only difference is that the
"dev_name" mount option is interpreted in fuseblk.
The description even mentions how this is useful for ZFS, however:
- ZFS pools (and by consequence, the ZFS filesystems inside them) are
typically composed of multiple block devices.
- I'm not even sure where the dev_name mount option or the fuseblk
filesystem type is supposed to go into (/etc/fstab?).
I'm not sure how can I use that functionality, since the ZFS filesystems
shouldn't even be added to /etc/fstab unless the administrator really
wants it (ZFS has an optional "legacy" mode for this).
So typically the filesystems are mounted by the zfs-fuse daemon itself,
which, of course, uses fuse_mount() to mount them.
What are your thoughts on this?
Thanks.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
fuse-devel mailing list
fuse-devel@...
https://lists.sourceforge.net/lists/listinfo/fuse-devel
