On 23.04.2011 01:38, Victor Hahn wrote:
I guess I know what the problem was - VirtualBox was probably still
running when I removed the packet(s). However, I didn't see any kind of
warning message. Is this case handled?
Removing the package should fail if a VM is still running.
--
To
Hmm... then I'm running out of ideas. I think the VirtualBox application
was still open, but no VM running. However, this shouldn't block the
kernel modules. There must be some unhandled case left, but I'm not sure
how to locate ist.
Regards,
Victor
On 04/23/2011 09:52 AM, Felix Geyer wrote:
On
On 19.04.2011 18:54, Victor Hahn wrote:
Should rmmod stuff
virtualbox-ose is supposed to rmmod all its modules.
Does the apt term.log contain Stopping VirtualBox kernel modules?
Anything interesting around it?
Which version of virtualbox-ose have you had installed?
--
To UNSUBSCRIBE,
I guess I know what the problem was - VirtualBox was probably still
running when I removed the packet(s). However, I didn't see any kind of
warning message. Is this case handled?
Here's the log except. Guess there's nothing interesting in it.
Removing virtualbox-ose-qt ...
Removing
Package: virtualbox-ose
Severity: minor
Should rmmod stuff
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
5 matches
Mail list logo
