Package: bindfs
Followup-For: Bug #951208
bindfs -o nonempty ... works for me after today's fuse3 update to 3.10.1-3,
which is patched per #939767 ("fuse3: Installing fuse3 breaks fuse2 applications
using -o nonempty").
Package: bindfs
Version: 1.14.7-1
Followup-For: Bug #951208
On 18/02/2020 14:07, Eugene V. Lyubimkin wrote:
> How common of a use case is to use bindfs with a non-empty mount point? I
> never mounted filesystems like that myself, so
> I don't know if it's a minor nuisance with an easy
Hi,
On 18/02/2020 14:07, Eugene V. Lyubimkin wrote:
> How common of a use case is to use bindfs with a non-empty mount point? I
> never mounted filesystems like that myself, so
> I don't know if it's a minor nuisance with an easy workaround, or a
> significant limitation making some use case
>
I've used non-empty mountpoints a few times, mostly when mounting a
directory onto itself, but I have no idea how popular that use case really
is.
Mounting to a new empty location is probably always possible, but it's
sometimes quite undesirable or inconvenient:
- Sometimes I want to enforce
Hello,
Martin Pärtel kirjoitti 17.2.2020 klo 10.49:
> I'm unfortunately unlikely to have time to port bindfs to FUSE 3 in the near
> future :(
>
> The easiest distro-level workaround in terms of "least code required" would
> probably be to patch fuse3's fusermount to
> allow and ignore
Ok, thanks. If you don't use other FUSE filesystems, you can maybe
uninstall `fuse3` and install `fuse`.
I'm unfortunately unlikely to have time to port bindfs to FUSE 3 in the
near future :(
The easiest distro-level workaround in terms of "least code required" would
probably be to patch fuse3's
Hi Martin,
On Wed, 2020-02-12 at 17:17 +0200, Martin Pärtel wrote:
> If that doesn't help, maybe you're running a mixed environment where
> e.g. bindfs is compiled against FUSE 2 but the system runs FUSE 3
> helper binaries? The version list at the end of your e-mail suggests
> this.
I haven't
Hi Willem,
The only reference to "nonempty" in binds code is when a directory is
mounted on itself. In that case bindfs adds `-ononempty` automatically. I
changed it so it doesn't on FUSE 3:
https://github.com/mpartel/bindfs/commit/2c2337b7c9b87744662c4b08d453bf7128444f43
(git master, not in a
Package: bindfs
Version: 1.14.1-1
Severity: normal
File: /usr/bin/bindfs
Dear Maintainer,
Currently, it's not possible for me to mount over nonempty directories.
BindFS insists I have to use -o nonempty:
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the
9 matches
Mail list logo
