Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-27 Thread Dmitry Astapov
On Wed, Oct 27, 2010 at 8:03 AM, Dmitry E. Oboukhov un...@debian.orgwrote: DA It is not a bug of insserv per se. Rather, insserv needs to be notified that when mhddfs mounts are present, fuse becomes a pre-requisite for mounting them. See bug #41 for similar discussion for another

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-27 Thread Dmitry E. Oboukhov
DA It is not a bug of insserv per se. Rather, insserv needs to be notified that when mhddfs mounts are present, fuse becomes a pre-requisite for mounting them. See bug #41 for similar discussion for another filesystem implementation. DA I doubt that *each* fuse filesystem should notify

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-26 Thread Dmitry E. Oboukhov
tags 592211 unreproducible moreinfo thanks Hi, Dmitry! I don't reproduce the problem. I use mhddfs only from fstab: home.uvw.ru:[~]$ grep mhddfs /etc/fstab mhddfs#/mnt/first_1T,/mnt/second_1T,/mnt/fourth/common /share/share fuse user,allow_other,default_permissions,exec 0 0

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-26 Thread Dmitry Astapov
On Tue, Oct 26, 2010 at 4:41 PM, Dmitry E. Oboukhov un...@debian.orgwrote: Hi, Dmitry! I don't reproduce the problem. I use mhddfs only from fstab: home.uvw.ru:[~]$ grep mhddfs /etc/fstab mhddfs#/mnt/first_1T,/mnt/second_1T,/mnt/fourth/common /share/share fuse

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-26 Thread Dmitry E. Oboukhov
DA Configuration: DA ~$ grep mhddfs /etc/fstab DA mhddfs#/storage-1Tb,/storage-500Gb /storage fuse allow_other,mlimit=15G 0 2 DA Insserv version: DA $ apt-cache policy insserv DA insserv: DA Installed: 1.14.0-2 DA Maybe your configuration does not use insserv? Yes, Now I hear about insserv for

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-26 Thread Dmitry Astapov
On Tue, Oct 26, 2010 at 8:12 PM, Dmitry E. Oboukhov un...@debian.orgwrote: DA Configuration: DA ~$ grep mhddfs /etc/fstab DA mhddfs#/storage-1Tb,/storage-500Gb /storage fuse allow_other,mlimit=15G 0 2 DA Insserv version: DA $ apt-cache policy insserv DA insserv: DA Installed: 1.14.0-2

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-10-26 Thread Dmitry E. Oboukhov
DA It is not a bug of insserv per se. Rather, insserv needs to be notified that when mhddfs mounts are present, fuse becomes a pre-requisite for mounting them. See bug #41 for similar discussion for another filesystem implementation. I doubt that *each* fuse filesystem should notify

Bug#592211: mhddfs-related entries in fstab are not processed under dependency-driven boot (insserv)

2010-08-08 Thread Dmitry Astapov
Package: mhddfs Version: 0.1.37 Severity: important Since recently, insserv (a.k.a. dependency-driven boot) is the preferred way of booting up Debian machines. With default insserv setup, fuse is started after the local and remote filesystems are mounted up, which means that fuse is not