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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for the pointer, however, although my French is ... absent, to say the least, if get it right, this SlackBuild script is intended for repackaging the closed source version, and not for building the open source edition of Virtual Box. I may be wrong, though.
Anyway, interesting!
gargamel
Yup, I believe you are right ... it seems to only compile the kernel module and take the rest from the .run
Hi, all, I'd just like to share my two cents on the topic. I just found out two days ago about VirtualBox available under GPL so I thought I'd give it a try. For me installation has been much easier than you've described. I simply
1) downloaded the VirtualBox-1.3.2 run file
2) install with the command
Code:
sh Virt*.run install
Note: if the target isn't specified it installs to /opt/VirtualBox-1.3.2
3) make my user a member of vboxusers
4) as root modprobe vboxdrv
5) after some fiddling and research I learned about the required LD_LIBRARY_PATH variable since all the libs went into the install directory. So I made a little script and copied it to /usr/bin
#!/bin/bash
cd /opt/VirtualBox-1.3.2
export LD_LIBRARY_PATH=/opt/VirtualBox-1.3.2
./VBoxSVC &
./VirtualBox
As I write this I have it open installing DOS 5. I didn't require any of the bcc, Xerces, iasl, etc.
To my very surprise, I dont have this node under /dev/vboxdrv but I could easily modprobe the kernel module.
How can I create this. I did not get any error while compiling and installing kernel modules for Vbox. Why want this created automatically ?
Hardik
Once you 'modprobe vboxdrv' as root it will show up.
Quote:
Originally Posted by dracolich
Hi, all, I'd just like to share my two cents on the topic. I just found out two days ago about VirtualBox available under GPL so I thought I'd give it a try. For me installation has been much easier than you've described. I simply
True, but
Quote:
After several years of intensive development, VirtualBox was released as Open Source in January 2007. InnoTek has chosen to release its VirtualBox source code under the GNU General Public License (GPL).
If you are interested in using VirtualBox -- either for private or business use --, you have the choice between two versions:
* The full VirtualBox package is available in binary (executable) form free of charge from the Downloads page. This version is free for personal use and evaluation under the terms of the VirtualBox Personal Use and Evaluation License.
If, instead, you wish to purchase licenses for enterprise use and/or enterprise support for VirtualBox, please do not hesitate to contact InnoTek.
* The VirtualBox Open Source Edition (OSE) is the one that has been released under the GPL and comes with complete source code. It is functionally equivalent to the full VirtualBox package, except for a few features that primarily target enterprise customers. This gives us a chance to generate revenue to fund further development of VirtualBox.
VirtualBox OSE is also available from the Downloads page.
It seems that the binaries are under a different license, and if you wanted to compile the VirtualBox OSE, then what I've posted above is accurate. If you want VirtualBox (non-OSE) then you use the binaries. Your choice. Of course, binaries may be easier/quicker to install.
Last edited by H_TeXMeX_H; 01-26-2007 at 04:56 PM.
The closed source licence conditions sound pretty liberal to me. Even commercial use seems to be allowed to a degree. So the non-OSE seems to be ok for most people, if they don't want go through the hassle of compiling from source. And there's the advantage that the closed source edition already supports USB. The details can be found here:
Ah.
I didn't pay much attention to the difference before I downloaded. Thanks for pointing it out. When it works it's nice. After my previous post I had to modify my script a bit - just take off the last line that says ./VirtualBox because it was killing the daemon. It can also be modified to add any VBOX_FLOPPY or VBOX_CDROM lines.
The licensed version of VirtualBox is now available in version 1.3.4 with a modified installer for Slackware. The only thing to do is to add some lines to /etc/rc.d/rc.local, but these lines are shown at the end of the installation process.
Fluxx.
P. S.: USB is working quite good within the guest system.
I just found out a this morning when checking the site. Indeed, it installs onto Slackware without any errors (I still haven't had to add libxalan-c and libxerces-c) and displays the lines to add to rc.local. I haven't had a chance to try it yet, but when I do I'm gonna check out the improved usb device filters, alsa sound and see if I can share host folders. I couldn't get folder sharing to work with 1.3.2.
I've installed the binary version of VirtualBox 1.3.8. But it didn't work. Each time i start a vm, it's just a black screen, nothing happen.
Can any one help me ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.