this is where the ones that design vserver have to step in... i don't know why/why not... Rik Bobbaers -- http://harry.enzoverder.be linux/unix/system/network/security/hardware/DR admin "If a man speaks his mind in a forest, and there's no woman to hear it ... is he still wrong?" > It looks like that is the underlying problem but is it safe to do that? > I, perhaps foolishly, assumed there was a good reason vserver did not do > that by default. Thanks - John > > On Fri, 2010-01-15 at 11:34 +0100, Rik Bobbaers wrote: >> maybe a stupid suggestion, but... is sysfs mounted in your guest? >> if not, what if you'd mount it at start? >> >> greetings, >> >> Rik Bobbaers >> >> -- http://harry.enzoverder.be >> linux/unix/system/network/security/hardware/DR admin >> "If a man speaks his mind in a forest, and there's no woman to hear it >> ... >> is he still wrong?" >> >> > Hello, all. We are trying to install a Debian Lenny vserver on a >> CentOS >> > 5.4 host running a custom kernel - 2.6.28.7-vs2.3.0.36.7. We are >> trying >> > to install fuse-utils and sshfs for use wit X2Go (a great project for >> > those unfamiliar with it - www.x2go.org). We keep getting: >> > >> > 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. >> > dpkg: error processing fuse-utils (--configure): >> > subprocess post-installation script returned error exit status 1 >> > dpkg: dependency problems prevent configuration of sshfs: >> > sshfs depends on fuse-utils (>= 2.7); however: >> > Package fuse-utils is not configured yet. >> > dpkg: error processing sshfs (--configure): >> > dependency problems - leaving unconfigured >> > Errors were encountered while processing: >> > fuse-utils >> > sshfs >> > >> > In the past, we simply created the fuse device manually and added >> > SECURE_MOUNT >> > SECURE_REMOUNT >> > BINARY_MOUNT >> > to ccapabilities >> > >> > Short of giving SYS_ADMIN and running udev, how do we get this to >> work? >> > Thanks - John >> > >> > >> > >> > > >