Date: Wed, 24 Jul 2013 17:37:14 +0300 From: Alexander Panyushkin <vsityz@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FUSE not work. Message-ID: <51EFE69A.9050100@gmail.com> In-Reply-To: <51EAA6A3.0@FreeBSD.org> References: <51E94F09.4020109@FreeBSD.org> <51E95B4D.4030104@gmail.com> <51E96C84.3000209@FreeBSD.org> <51E97265.8040507@gmail.com> <51E9E669.3090500@FreeBSD.org> <CAN6yY1tC0n=jijX2kGJrZu2Pc45%2BhaQsHFrEsozkucT%2BTZL-NA@mail.gmail.com> <51EAA6A3.0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
20.07.2013 18:02, Pedro Giffuni пишет: > On 19.07.2013 23:42, Kevin Oberman wrote: >> ... >> >> >> fuse is at least partly broken in -current. I discovered that if you >> mount two devices that use fuse, when you umount any of them, ll are >> marked as not mounted and disappear from df(1) or mount(8) output, >> but only one is actually cleanly unmounted and, if it has been >> written to, will likely be corrupt. This applies to at least ntfs. >> >> ATM no one is supporting fuse in current, so this may become a >> serious issue before long. > > I reverted my incompatible changes and will try to see if upstream wants > to adopt something compatible for birthtime support. > > I do agree that fuse needs a lot of work. I wonder if NetBSD's > puffs/libperfuse > is any better. > > Pedro. Can we expect in the near future a working version of FUSE to FreeBSD 10?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51EFE69A.9050100>