SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I had some problems installing VirtualBox 2.1 PUEL (not OSE) on Slackware 12.2. This is what worked for me (this applies to a system upgraded to 12.2 from 12.1 using the official instructions):
After installation (sh VirtualBox-2.1.0-41146-Linux_x86.run as root) VirtualBox would not start complaining about a missing libcap.so.1.
For some reason the package libcap-2.14-i486-1.tgz was not installed on my machine during upgrade and I had to manually download it from a Slackware ftp mirror (look under l/). After installing the package the same complaint about missing libcap.so.1 appeared, so I made a symbolic link as follows
(as root)
cd /lib
ln -s libcap.so.2.14 libcap.so.1
I have installed VirtualBox 2.1.0 yet, and applied your instructions but i have different problem now.
Quote:
sinem@slackware:~$ su
Password:
root@slackware:/home/sinem# VirtualBox
/opt/VirtualBox-2.1.0/VirtualBox: error while loading shared libraries: libcap.so.1: cannot open shared object file: No such file or directory
root@slackware:/home/sinem# cd /lib
root@slackware:/lib# ln -s libcap.so.2.14 libcap.so.1
root@slackware:/lib# VirtualBox
No protocol specified
Qt WARNING: VirtualBox: cannot connect to X server :0.0
root@slackware:/lib#
Last edited by sertmusluman; 12-18-2008 at 04:55 PM.
Yes it works properly now.
Previous versions were requiring a bit work to install an OS on VirtualBox as USER. Now can i directly install an OS as user?
I installed VBox 2.1.0 two days ago but in a different way. I first tried libcap2 as you did, and had the same error. I thought of the linking trick but didn't do it, fearing it could cause some problems. Instead, I found libcap1 from the Debian repository. The original package doesn't compile but there is also a patch there, with that patch applied it compiles nicely and you can run VBox. Here is the page:
Yes it works properly now.
Previous versions were requiring a bit work to install an OS on VirtualBox as USER. Now can i directly install an OS as user?
You're getting that error because the root user can't create an X connection (any GUI program will give you that error). If you run an X session as root you won't get that. But it's a bad idea to run VBox as root anyway, so just run it as a regular user.
Ilgar, how about a buildscript, with the patch? Perhaps you can submit it to slackbuilds.org for everyone. There is a buildscript for libcap1 for slackware 11 at slackbuilds.org but I don't see any patch. Perhaps you can expand this.
Ilgar, how about a buildscript, with the patch? Perhaps you can submit it to slackbuilds.org for everyone.
I guess this won't be accepted. libcap1 is old code, meant for the 2.4.x kernel series. For 2.6.x kernels there's libcap2, which is already included in Slackware 12.2 and won't be accepted by SlackBuilds.org either.
I guess this won't be accepted. libcap1 is old code, meant for the 2.4.x kernel series. For 2.6.x kernels there's libcap2, which is already included in Slackware 12.2 and won't be accepted by SlackBuilds.org either.
In that case I should probably not bother. Isn't it strange that VBox asks for a 2.4 libcap library, because after all it's targeted for and it extensively uses 2.6 stuff...
I installed VB and made the link trick and it works :-D
My question now is how can I activate my USB ports in order to attach an Ipodtouch to my virtual OS.
I received an IPod Touch for Christmas (2G so no linux for me yet) and set this up in my Windows VM in VirtualBox 2.1.
I made the libcap link as above, I changed rc.S as above, I'm already in the wheel group, and I set up a USB filter in VirtualBox. When the device is plugged in and before you boot up the virtual machine, go to Settings->USB, enable USB and USB 2.0. On the right, click the "Add filter from Device" button (second one down) and it should autodetect the USB settings right from the IPod and you can add that filter (if not see if you can grab what its asking for using the lsusb -v command in shell). If you do not set up this filter and go to upgrade/jailbreak your firmware you could potentially brick your ipod! It's unlikely but I wouldn't take that chance.
As of today, there's no jailbreak for the 2G Ipod touch so it's important to seriously do your research on that before doing so. This might not apply to you but I feel obligated to mention it for others who might read this thread. It is too excellent of a device to brick despite the fact it is a prisoner in its own hardware with absolutely zero linux compatibility. Zero unless you have a USB-functional windows/mac virtual machine or physical host... and this method works beautifully in Slackware.
Last edited by zetabill; 12-26-2008 at 04:40 PM.
Reason: If it works once without changing rc.S: after reboot, changing rc.S is necessary. Best to just do it...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.