Am Freitag, den 15.01.2010, 11:10 -0500 schrieb John A. Sullivan III: > I think that is exactly right. We have had FUSE running successfully > before. It appears to be the installation scripts insistence that it > access sysfs because it finds udev. > > But how do we get it to not find udev? I did remove all links > to /etc/init.d/udev in all the rcX.d directories and restarted the > guest. > > vdbase:/etc# ls rc?.d/*udev* > ls: cannot access rc?.d/*udev*: No such file or directory > > vdbase:/# cd /etc/init.d > vdbase:/etc/init.d# ./udev status > udev requires a mounted sysfs, not started. failed! > failed! as i said, make /etc/init.d/udev return 0 no matter how it's called and you should be fine. > Yet: > Setting up fuse-utils (2.7.4-1.1) ... > creating fuse group... > udev active, skipping device node creation. > udev requires a mounted sysfs, not started. failed! > failed! > invoke-rc.d: initscript udev, action "reload" failed. fuse-utils probably calls /etc/init.d/udev reload directly after installation and there it fails. > On Fri, 2010-01-15 at 17:01 +0100, Thomas Weber wrote: > > well, i have sshfs/fuse running in an ubuntu karmic guest without /sys > > mounted and without udev running, don't see why this shouldn't work in > > lenny either. > > > > I think it's udev that fails because /sys isn't there. > > And fuse fails because udev failed. > > What would udev be good for in a guest anyway? Disable it's startup > > scripts, just let them return 0 for a restart/reload and you should be > > fine. > > > > Tom > >