Re: FUSE Call for Testing
On Fri, 9 Aug 2019 15:38:06 +0200 Gary Jennejohn wrote: > On Fri, 9 Aug 2019 06:49:36 -0600 > Alan Somers wrote: > > [snip test results] > > > Thanks for the report, Gary. BTW, fusefs mounts are only > > interruptible when mounted with "-o intr". If you didn't use that > > option, then the signal would only interrupt cp after the write to > > fusefs was done. Also, not every fuse file system supports > > interrupts. Looking through its sources, I don't think that > > fusefs-ntfs does. > > > > I'm not convinced of that. I interrupted the 5.2GiB transfer > several times to try out different UBLIO environment settings > and it stopped pretty much immediately. I also did not use > mount but rather a direct invocation of ntfs-3g. > > I suspect that ntfs-3g stops after the interrupt once it has > flushed the UBLIO buffers. > Upon reconsideration, I guess you're right. What stopped was cp and not necessarily ntfs-3g. Still, ^C did what I expected. -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Fri, Aug 9, 2019 at 7:38 AM Gary Jennejohn wrote: > > On Fri, 9 Aug 2019 06:49:36 -0600 > Alan Somers wrote: > > [snip test results] > > > Thanks for the report, Gary. BTW, fusefs mounts are only > > interruptible when mounted with "-o intr". If you didn't use that > > option, then the signal would only interrupt cp after the write to > > fusefs was done. Also, not every fuse file system supports > > interrupts. Looking through its sources, I don't think that > > fusefs-ntfs does. > > > > I'm not convinced of that. I interrupted the 5.2GiB transfer > several times to try out different UBLIO environment settings > and it stopped pretty much immediately. I also did not use > mount but rather a direct invocation of ntfs-3g. > > I suspect that ntfs-3g stops after the interrupt once it has > flushed the UBLIO buffers. > > -- > Gary Jennejohn (gj@) Well, I can guarantee that the write(2) into fusefs was not interrupted if you did not specify "-o intr". I know, because I wrote that code. You would need to use "-o intr" whether you mount by invoking mount or ntfs-3g. But cp probably only copies a few KB to a few hundred KB at a time. So even without "-o intr", a signal would probably feel fairly responsive. -Alan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Fri, 9 Aug 2019 06:49:36 -0600 Alan Somers wrote: [snip test results] > Thanks for the report, Gary. BTW, fusefs mounts are only > interruptible when mounted with "-o intr". If you didn't use that > option, then the signal would only interrupt cp after the write to > fusefs was done. Also, not every fuse file system supports > interrupts. Looking through its sources, I don't think that > fusefs-ntfs does. > I'm not convinced of that. I interrupted the 5.2GiB transfer several times to try out different UBLIO environment settings and it stopped pretty much immediately. I also did not use mount but rather a direct invocation of ntfs-3g. I suspect that ntfs-3g stops after the interrupt once it has flushed the UBLIO buffers. -- Gary Jennejohn (gj@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Fri, Aug 9, 2019 at 3:02 AM Gary Jennejohn wrote: > > On Thu, 8 Aug 2019 12:34:52 -0600 > Alan Somers wrote: > > [snip] > > > 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! > > So, I tried it with fuse-ext2 (mount RO) and ntfs-3g > (fusefs-ntfs). > > Both work. Interrupting a transfer also doesn't seem to cause > problems. > > Reading from NTS was pretty fast at >= 65MiB/sec. I suspect that > most FBSD users will use NTFS in this way. > > Hard to say whether writing to NTFS is faster than it was before > because the transfer rate bounces around all over the place. > Sometimes a few 100KiB, sometimes 10s of MiB. I suspect that the > small transfers are associated with filesystem bookkeeping. > Small tranfers are most frequent. > > NOTE that I had to reinstall fusefs-ntfs (I had a really old > version) for it to work. I tried it with and without LOCK and > UBLIO but no real difference in speed was noticeable. > > NOTE2 that writing to NTFS was tested by copying a 5.2GiB file > from a SATA SSD to a 64GiB USB3 stick plugged into a USB3 port. > I then used /usr/bin/sum to test integrity. The result was > identical for both files, so that's good news. > > -- > Gary Jennejohn (gj@) Thanks for the report, Gary. BTW, fusefs mounts are only interruptible when mounted with "-o intr". If you didn't use that option, then the signal would only interrupt cp after the write to fusefs was done. Also, not every fuse file system supports interrupts. Looking through its sources, I don't think that fusefs-ntfs does. -Alan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Thu, 8 Aug 2019 12:34:52 -0600 Alan Somers wrote: [snip] > 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! So, I tried it with fuse-ext2 (mount RO) and ntfs-3g (fusefs-ntfs). Both work. Interrupting a transfer also doesn't seem to cause problems. Reading from NTS was pretty fast at >= 65MiB/sec. I suspect that most FBSD users will use NTFS in this way. Hard to say whether writing to NTFS is faster than it was before because the transfer rate bounces around all over the place. Sometimes a few 100KiB, sometimes 10s of MiB. I suspect that the small transfers are associated with filesystem bookkeeping. Small tranfers are most frequent. NOTE that I had to reinstall fusefs-ntfs (I had a really old version) for it to work. I tried it with and without LOCK and UBLIO but no real difference in speed was noticeable. NOTE2 that writing to NTFS was tested by copying a 5.2GiB file from a SATA SSD to a 64GiB USB3 stick plugged into a USB3 port. I then used /usr/bin/sum to test integrity. The result was identical for both files, so that's good news. -- Gary Jennejohn (gj@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
Damjan, thanks for the suggestion. I did like Alan suggested and: clay@bsd13:~ % pkg info -r fusefs-libs pkg: No package(s) matching fusefs-libs clay@bsd13:~ % pkg info -r fusefs-libs3 pkg: No package(s) matching fusefs-libs3 I'm sitting here looking at a pkg search fuse in LXTerminal and I see: fusefs-ntfs-2017.3.23 Mount NTFS partitions (read/write) and disk images fusefs-ext2-0.0.10_2 FUSE module to mount ext2, ext3 and ext4 with read write support I triple boot with MS Windows 10, MX Linux, and FreeBSD 13.0, so I could certainly make use of those tools. I just now copied all the files I wanted to save from this installation to a thumbdrive, and now downloading r350702. I will report back later. Clay On Fri, Aug 9, 2019 at 12:25 AM Damjan Jovanovic wrote: > NTFS-3G (sysutils/fusefs-ntfs) is probably the most widely used FUSE > filesystem. > > On Fri, Aug 9, 2019 at 4:21 AM Clay Daniels Jr. > 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 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@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscr...@freebsd.org" >> > >> ___ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org >> " >> > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Thu, Aug 8, 2019 at 10:25 PM Damjan Jovanovic wrote: > NTFS-3G (sysutils/fusefs-ntfs) is probably the most widely used FUSE > filesystem. > fusefs-exfat is also pretty commonly used. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > On Fri, Aug 9, 2019 at 4:21 AM Clay Daniels Jr. > > 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 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@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to " > > freebsd-current-unsubscr...@freebsd.org" > > > > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
NTFS-3G (sysutils/fusefs-ntfs) is probably the most widely used FUSE filesystem. On Fri, Aug 9, 2019 at 4:21 AM Clay Daniels Jr. 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 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@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
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. 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 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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
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 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FUSE Call for Testing
On Thu, Aug 08, 2019 at 12:34:52PM -0600, Alan Somers 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: Thanks for sharing your work! -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FUSE Call for Testing
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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
