On Fri, 2010-01-15 at 20:10 +0100, Thomas Weber wrote:
> 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.
>
<snip>
Yes, it looks like that is exactly the case. I made udev exit 0
immediately and it worked so it must have been trying to start udev
again. Thanks - John
Received on Fri Jan 15 21:21:07 2010