RFC: fuse packages

[Jeremy Katz]

On Sun, 2005-10-30 at 09:52 +0200, Ville Skyttä wrote:
> On Sat, 2005-10-29 at 14:32 -0400, Jeremy Katz wrote:
> > On Sat, 2005-10-29 at 19:36 +0200, Thorsten Leemhuis wrote:
> > > - Fuse needs a device file /dev/fuse that is packaged for /dev/ and
> > > %{_sysconfdir}/udev/devices/ (bit ugly due to a rpm-bug).  Yes, the
> > > module and udev can create the /dev/fuse automatically when the module
> > > is loaded. But it seems the FUSE-Filesystems try to autoload the module
> > > by accessing /dev/fuse -- if it's not there the module does not get
> > > loaded and the FUSE-Filesystem fails -- or did I miss any trick to solv
> > > that easily?
> > 
> > You probably want to add a fuse file to /etc/udev/makedev.d --
> > start_udev looks there on boot to figure out nodes which need to be made
> > at boot time just to deal with this sort of problems.
> 
> Hm, but that wouldn't help with the autoload assumption part of the
> problem, right?  Dropping in a /etc/sysconfig/modules/fuse.modules
> (see /etc/rc.sysinit) should "fix" it, and if something creates the /dev
> entry when the module is loaded, that too, but in a uglyish way.

No, have the node listed in the makedev.d dir will have it created on
boot -- then userspace can happily go on accessing it to autoload the
module.  This is how, eg, the loop module is handled

Jeremy