On Sun, Mar 9, 2008 at 8:05 AM, Michael Meskes <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 05, 2008 at 06:31:11PM -0300, Nelson A. de Oliveira wrote:
> > Today while upgrading to 1.5.6-dfsg-2 (from 1.5.6-dfsg-1):
> >
> > Setting up virtualbox-ose (1.5.6-dfsg-2) ...
> > Starting VirtualBox host networking ...fail!
> > invoke-rc.d: initscript virtualbox-ose, action "start" failed.
> > dpkg: error processing virtualbox-ose (--configure):
> > subprocess post-installation script returned error exit status 1
> > Errors were encountered while processing:
> > virtualbox-ose
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Now this tells us what?
Setting up virtualbox-ose (1.5.6-dfsg-2) ...
+
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/bin:/sbin:/usr/sbin
+ CONFIG=/etc/vbox/interfaces
+ VARDIR=/var/run/VirtualBox
+ VARFILE=/var/run/VirtualBox/vboxnet
+ TAPDEV=/dev/net/tun
+ [ -f /etc/default/virtualbox-ose ]
+ . /etc/default/virtualbox-ose
+ LOAD_VBOXDRV_MODULE=0
+ [ -f /etc/redhat-release ]
+ [ -f /etc/SuSE-release ]
+ [ -f /etc/gentoo-release ]
+ system=other
+ [ other = redhat ]
+ [ other = suse ]
+ [ other = gentoo ]
+ [ other = other ]
+ [ 0 = 1 ]
+ start
+ start_network
+ begin Starting VirtualBox host networking
+ echo -n Starting VirtualBox host networking
Starting VirtualBox host networking+ [ -f /var/run/VirtualBox/vboxnet ]
+ [ ! -d /var/run/VirtualBox ]
+ touch /var/run/VirtualBox/vboxnet
+ [ ! -f /etc/vbox/interfaces ]
+ [ ! -r /etc/vbox/interfaces ]
+ VBoxTunctl -h
+ grep VBoxTunctl
+ modprobe tun
+ cat /proc/misc
+ grep tun
+ fail_msg
+ [ -f /var/run/VirtualBox/vboxnet ]
+ rm /var/run/VirtualBox/vboxnet
+ echo ...fail!
...fail!
+ return 1
+ exit
invoke-rc.d: initscript virtualbox-ose, action "start" failed.
dpkg: error processing virtualbox-ose (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
virtualbox-ose
>From /etc/init.d/virtualbox-ose:
# Fail if we don't have the kernel tun device
# Make sure that the tun module is loaded (Ubuntu 7.10 needs this)
modprobe tun > /dev/null 2>&1
if ! cat /proc/misc 2>/dev/null | grep tun > /dev/null
then
fail_msg
return 1
fi
I don't have tun compiled on this Kernel.
Can this be the cause to have this fail? (returning 1 will cause
postinst to fail, right?)
> A not mountes /proc for instance would suffice to get this result.
proc on /proc type proc (rw,noexec,nosuid,nodev)
Best regards,
Nelson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
