Re: FUSE Call for Testing

2019-08-09 Thread Gary Jennejohn
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

Re: FUSE Call for Testing

2019-08-09 Thread Alan Somers
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

Re: FUSE Call for Testing

2019-08-09 Thread Gary Jennejohn
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.

Re: FUSE Call for Testing

2019-08-09 Thread Alan Somers
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:

Re: FUSE Call for Testing

2019-08-09 Thread Gary Jennejohn
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

Re: FUSE Call for Testing

2019-08-09 Thread Clay Daniels Jr.
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:

Re: FUSE Call for Testing

2019-08-09 Thread Kevin Oberman
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

Re: FUSE Call for Testing

2019-08-08 Thread Damjan Jovanovic
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.

Re: FUSE Call for Testing

2019-08-08 Thread Alan Somers
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

Re: FUSE Call for Testing

2019-08-08 Thread Clay Daniels Jr.
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

Re: FUSE Call for Testing

2019-08-08 Thread Steve Kargl
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! --

FUSE Call for Testing

2019-08-08 Thread Alan Somers
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,