Clay, Thanks for offering to help. If you don't know whether or not you're currently using FUSE, just do "pkg info -r fusefs-libs" and " pkg info -r fusefs-libs3". There are a few fuse ports that don't depend on either fusefs-libs or fusefs-libs3, but not many. If you don't find any, but want to play around anyway, then you can try installing something like fusefs-wikipediafs or fusefs-sshfs. The former lets you mount wikipedia as a file system, and the latter lets you view a remote server's file system via an SSH connection. -Alan On Thu, Aug 8, 2019 at 8:21 PM Clay Daniels Jr. <clay.daniels.jr_at_gmail.com> wrote: > > Alan, I'm pretty much into 13.0 Current and most weeks install the newest snapshot build. I don't know if I use FUSE or not, if you must know the truth. I do some hobby coding, lurk here on the email lists and Forum, and try to learn all I can. So do you have any specific suggestions for programs to install and test FUSE? I kind of like the no-x console & the Xterminal window too, and dabble with clang cc (strictly C, no C++) and Python too. Let me know. > > Clay Daniels > > On Thu, Aug 8, 2019 at 1:36 PM Alan Somers <asomers_at_freebsd.org> wrote: >> >> The new FUSE driver has just landed in current. It raises the protocol >> level from 7.8 to 7.23, fixes many bugs, adds a test suite for the >> driver, and adds many new features. New features include: >> * Optional kernel-side permissions checks (-o default_permissions) >> * Implement VOP_MKNOD, VOP_BMAP, and VOP_ADVLOCK >> * Allow interrupting FUSE operations >> * Support named pipes and unix-domain sockets in fusefs file systems >> * Forward UTIME_NOW during utimensat(2) to the daemon >> * kqueue support for /dev/fuse >> * Allow updating mounts with "mount -u" >> * Allow exporting fusefs file systems over NFS >> * Server-initiated invalidation of the name cache or data cache >> * Respect RLIMIT_FSIZE >> * Try to support servers as old as protocol 7.4 >> >> Performance enhancements include: >> >> * Implement FUSE's FOPEN_KEEP_CACHE and FUSE_ASYNC_READ flags >> * Cache file attributes >> * Cache lookup entries, both positive and negative >> * Server-selectable cache modes: writethrough, writeback, or uncached >> * Write clustering >> * Readahead >> * Use counter(9) for statistical reporting >> >> Now would be a good time for the community to test it. If you are >> BCCed to this email, it's because you maintain a FUSE-related port. >> Please test your port on the latest FreeBSD CURRENT image and let me >> know if you have any problems or find any bugs. >> >> Even if you don't maintain a FUSE port, you can still help. If you >> use current and commonly use any FUSE file systems, please try them >> out after upgrading to the latest image. >> >> Additionally, the following FUSE-related ports don't have maintainers. >> If you use one of them, or know somebody who does, please test them on >> current, and consider adopting the port: >> deskutils/kdeconnect-kde >> devel/gvfs >> devel/py-fusefs >> sysutils/fusefs-afuse >> sysutils/fusefs-chironfs >> sysutils/fusefs-cryptofs >> sysutils/fusefs-funionfs >> sysutils/fusefs-fusepak >> sysutils/fusefs-httpfs >> sysutils/fusefs-s3backer >> sysutils/fusefs-sqlfs >> sysutils/fusefs-zip >> sysutils/p5-Brackup >> sysutils/p5-Fuse >> >> VM images: http://ftp0.nyi.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/13.0-CURRENT/amd64/20190808/ >> ISOs: http://ftp0.nyi.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/ >> >> Thanks for any feedback you can give! >> -Alan >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Fri Aug 09 2019 - 02:02:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC