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 #555541 for similar discussion for another filesystem 
implementation.

DA> I doubt that *each* fuse filesystem should notify insserv. I think
DA> that this notification should be placed into fuse-package
DA> (fuse-utils). And only if a filesystem requires additional services,
DA> then it should provide such notifies.

DA> What kind of "additional services" you have in mind, exactly?

not only fuse. for example: network, or runned ssh server.

mhddfs depends only on fuse. So I think that fuse should provide mount
posibility in its init scripts. And FSs like sshfs must provide
additional depends.

DA> I am not a DD, but in my opinion the following makes sense:
DA> If starting up fuse early has no adverse side-effects, then it is the 
proper way to go, and this bug should be merged with #555541.

It is a wrong way in mhddfs's init script to init FUSE. I think that
FUSE must be init in FUSE's script.

DA> Otherwise (assuming there are some side-effects) the following seems to be 
the proper course:
DA> 1)Fuse should be started early only if there are some fuse-based mounts in 
/etc/fstab

Fuse must assume that user can mount FUSE filesystems from fstab (If
he installed fuse-util). I think.

DA> 2)Fuse-utils could not possibly know how to detect all possible syntaxes 
for fuse-based filesystems in /etc/fstab

All syntaxes are identical:

filesystem#something /path fuse options number number

any fuse filesystem is mounted as *fuse* type.


DA> -----BEGIN PGP SIGNATURE-----
DA> Version: GnuPG v1.4.10 (GNU/Linux)

DA> iEYEAREDAAYFAkzHspwACgkQq4wAz/jiZTdv0gCg2y8aAjJ9MC/YLkL+KZfFHMGA
DA> pqUAn1+FP6jb1mjNNxoQZNcfHIUPBj7F
DA> =FMPs

please, don't quote signatures :)
-- 
... mpd playing: U.D.O. - Shout It Out

. ''`.                               Dmitry E. Oboukhov
: :’  :   email: un...@debian.org jabber://un...@uvw.ru
`. `~’              GPGKey: 1024D / F8E26537 2006-11-21
  `- 1B23 D4F8 8EC0 D902 0555  E438 AB8C 00CF F8E2 6537

Attachment: signature.asc
Description: Digital signature

Reply via email to