On Thu, 2008-11-27 at 19:16 +0000, Armindo Silva wrote: > > No they are not! They just can be run at the same time
Wrong. The way the kvm package is installed on Ubuntu, they cannot be installed at the same time because when the machine boots, the KVM initscript makes running VirtualBox impossible. No point to having it installed if you cannot run it -- again, assuming the regular user has no root abilities (sudo or otherwise) on his machine. > I did not understand what you been by this. Of course i have root (in > this case sudo powers) on my machine Good for you. I suspect you are a lone user sitting at home on your own machine, which you installed yourself, yes? > and you should have to or you couldn't install either kvm or vbox. You really don't understand how corporate/managed environments work do you? Typically your company's IT department installs and manages the software on your machine and you, as a user, are not free to go install what you want willy-nilly -- typically neither are you afforded root access to mess up your machine. Giving users "admin" rights on their machines is the road to the type of madness that Windows based IT departments face with users installing all kinds of crap that destablizes their machines and brings in virii, worms and trojans. Further, it escalates the TCO of user machines with additional software needed to combat user ignorance and silliness and the additional labour of having to go fix the machines once the users have pooched them with the latest funky screensaver. > If you are a only on a machine that have both installed but vbox can't > be used you should complain to your sys admin. Sure, my sysadmin *might* understand the incompatibilities between VirtualBox and KVM, but then again, there are literally thousands of packages available in Ubuntu. Is he to know of all of the various mutual-exlusivities of them all? Of course not. That is why packing systems like dpkg/apt (and RPM and most if not all others for that matter) allow the package authors, who *are* intimately knowledgeable about the software they are packaging and what it's incompatible with to help the sysadmin and describe conflicts in the package itself. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
