I believe we've been complaint with FUSE since Version 1.4 (2003). Unless these have deprecated features, it shouldn't be a problem.
Have you run into any issues with the newest version? Basically, we use a subset of FUSE capabilities. Only the original "high level" interface which maps calls like "open" "read" "write" "dir read" "fstat" and "close" to OWFS callback functions. Most of the fuse development work, which I follow loosely, has been with giving users tighter control over caches, inode maps, and memory mapping. All those are important when trying to emulate a high-performance filesystem in userspace. 1-wire is so slow compared to filesystem calls that we don't need to squeeze out an extra kernel context switch. In fact, even open and close are ignored in our implementation. The only likely problem that might occur with fuse is that we use the earlier directory implementation, which has been deprecated, but supported, for some years now. On Thu, Jan 20, 2011 at 11:12 PM, Gregg Levine <[email protected]> wrote: > Hello! > This should come as no surprise, but here goes, the guys behind it > have come out with a newer version, 2.8.5, and thats newer then the > Slackware release currently running on my test box now. That guy has > 2.8.1 on it. I'm now rebuilding the Slackware package with that > version. > > Ideally group we do need to track what the folks at Fuse are up to on > the releases they are putting out. > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
