From owner-freebsd-current@freebsd.org Fri Aug 9 04:02:56 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7ED0CBC256 for ; Fri, 9 Aug 2019 04:02:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com [209.85.167.66]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 464Wmb3XGkz41vR for ; Fri, 9 Aug 2019 04:02:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f66.google.com with SMTP id p197so68428520lfa.2 for ; Thu, 08 Aug 2019 21:02:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Q97wgqhkWFGH45BaBTsgEhWu3ANcDKERHE/8S9CGvTM=; b=OGym0knWljCsFZFV9KkLY6cgKKPAtPSHD2WuQuBI4f7UA8mJKA8teRGFwLnkoojRWs qEf7AsdXDbWxiHehio8L7GBOkLFoIoBjOWRr3cy9RgG8w+lQNRg92ynesaprJlKKJXBG HuvqP6geB8XPgDAOQHCKMj7objN9NBGBLodJjvBX8wDDemhu+XJ1Y2JS5x35V3NIEKSD zRszPqdnbdDbpf7pz4QjeMbBC2pRiXq11gsLlQMDDB/6Z/WfHpgAGj8B7c+qkSOC2SFE D8fBZVqd3sIJJi5os9fL3jbrCxjUMh92q7jpFtjZRHIa1yVTFyZgiXkEBhg8SVV5YVpS vlsw== X-Gm-Message-State: APjAAAX728GvtFhHXPqVWrm0cEuewQs71L5Q5TPhlQEuEvJfSB7ijv5T 09bsQqiC77tkJ3mIJjrsEtC1nRVToQo5ZwSNg24= X-Google-Smtp-Source: APXvYqx9z9dIf/Av2gZxvv5LdB3zBE0uoUimkoohpICfMQRAEBfXPVPMcMqwBWtIkByWdGGiBuI8gSHoNgoKXxPJDLI= X-Received: by 2002:a19:6904:: with SMTP id e4mr11518699lfc.156.1565323373333; Thu, 08 Aug 2019 21:02:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Thu, 8 Aug 2019 22:02:41 -0600 Message-ID: Subject: Re: FUSE Call for Testing To: "Clay Daniels Jr." Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 464Wmb3XGkz41vR X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.167.66 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-4.11 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.996,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[66.167.85.209.list.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-1.12)[ip: (0.28), ipnet: 209.85.128.0/17(-3.38), asn: 15169(-2.43), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.167.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2019 04:02:56 -0000 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 tr= uth. I do some hobby coding, lurk here on the email lists and Forum, and tr= y 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 w= indow too, and dabble with clang cc (strictly C, no C++) and Python too. Le= t 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/1= 3.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-unsubscribe@freebsd.or= g"