On Tue, 31 Mar 2009 17:55:20 -0700 Unsane <[email protected]> dijo:
> Why not install VirtualBox and then install Hardy as a VM, rather than > scrapping the entire OS? This is just not my day. I thought your suggestion was brilliant. I was so upset and frustrated that I couldn't think of something so simple. And better yet, it would give me a chance to prove that OOo 2.4.1 on Hardy is trouble free and would solve my problems. I could leave the decision about reinstalling Hardy until later. I already had VirtualBox installed, with Windows 2000 and XP installed as guest OSs. So I created a new one for Hardy, then inserted the Hardy live CD. It started to install, then announced that it required a 64-bit CPU. Of course, it was Hardy x86_64. Except that I do have x86_64 Intrepid and Vitualbox 2.0.4, and 2.0.4 is supposed to handle 64-bit guest OSs. Well, it doesn't. So off to Sun Microsystems to muck around. I discovered that there have been improvements to 64-bit support and the current version is 2.1.4. But 2.1.4 is not currently in the repos. "No prob, I'll just download the amd64 deb from Sun and install it with gDebi." Hah! Download is quick, but gDebi announces that it can't install it because it conflicts with Virtualbox-OSE. So back to Sun, and I discover that I can add the Sun repo for Virtualbox. Supposedly that will make the latest version appear in Synaptic and Update Manager and stuff. Done. But it still does not appear in Synaptic. OK, back to Sun again. There I find instructions to just install it with apt-get. OK, did that. But the installation with apt-get removed Virtualbox-OSE. "No problem, that's the old version anyway" I think. So I try to launch the new Virtualbox. Apt-get failed to install any new launch menu entries. The old launch entry does nothing - no error messages, just nada. From the command line "virtualbox" and "virtualbox-ose" say they can't find the command. Back to Sun. No instructions for a launch command. "OK, screwi it" I say to myself. I'll just reinstall Virtualbox-OSE 2.0.4 from Synaptic and use a 32-bit Hardy. Synaptic happily installs Virtualbox 2.0.4, although it says it must remove 2.1.4 to do so. Afterwards I click on my launch menu and still nada. Command line still says no such command for either virtualbox or virtualbox-ose. So here I sit with no Virtualbox and apparently no way to get it reinstalled so that it will work. Bah. Time for that bottle of Canadian. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
