VirtualBox on Indiana
I've taken the leap and converted my desktop to run Indiana Developer Preview 2. It's looking pretty nice so far, but as the Preview title suggests, running this as a primary development machine is still a bit on the bleeding edge. So, I'm filing or updating bugs at http://defect.opensolaris.org as they pop up.
Getting VirtualBox running was one of my top priorities so that it remains easy to test in-development bits on Nevada too. So, I downloaded and installed VirtualBox for my amd64 system, and got this:
$ /usr/bin/VirtualBox ld.so.1: VirtualBox: fatal: libX11.so.4: open failed: No such file or directory Killed
So, I found (well, David pointed me at) Indiana bug 512, which describes the missing symlink. Since it's just a missing link, I was easily able to work around it.
# cd /usr/lib/amd64 # ln -s ../../X11/lib/64/libX11.so.6 libX11.so.4
Now I can launch /usr/bin/VirtualBox, and am installing Nevada right now.
"ln -s ../../X11/lib/64/libX11.so.6 libX11.so.4
"
installf?
Posted by UX-admin on March 11, 2008 at 03:15 AM PDT #
X (and all of Indiana) is managed by pkg(5) in the Developer Preview preview, which is a new packaging system. installf is no longer appropriate because System V packaging doesn't manage the installed X files, and wouldn't have been appropriate for a one-off workaround done by an admin (me) even if it was a command which manipulated pkg(5) packages.
I don't want to tell the system that this file is managed by packaging in my workaround -- it's not, it's just a workaround I put in place. I'm waiting for the real fix for the bug referenced above (512) from the X team. :)
The System V style of packages is still supported (I used pkgadd to install Virtual Box), but bits of the OS like X are not managed that way.
Posted by Liane Praza on March 11, 2008 at 07:31 AM PDT #