You are not logged in.
I'm a relative n00b to Arch, haging migrated from Ubuntu (pha!!). Arch rocks!
However, my beloved virtualbox isnt playing ball!
After many hours of getting arch up and running I now need some assitance please with VirtualBox PEUL. I've googled and search these wikis and found:
http://aur.archlinux.org/packages.php?d … s=0&SeB=nd
http://www.mail-archive.com/vbox-users% … 02889.html
http://wiki.archlinux.org/index.php/VirtualBox
but, I dont know how to install.
I used yaourt (having spent another many hours trying to get to speed with what Arch AUR is and yaourt!!)
This is what I did:
1. Visited http://wiki.archlinux.org/index.php/VirtualBox and followed PEUL instructions...
2. Click on AUR link and then click on PKGBUILD and it downloaded a PKGBUILD from here http://aur.archlinux.org/packages.php?d … s=0&SeB=nd
3. Then went back to the wiki http://wiki.archlinux.org/index.php/VirtualBox and clicked on VirtualBox_1.5.6-1_Linux_x86.run and downloaded the file.
4. In accordance with the instructions on the wiki, I ran makepkg
HOWEVER, I get errors!!:
# makepkg --asroot
==> Making package: virtualbox_bin 1.5.6-1 (Thu May 1 20:06:33 BST 2008)
==> WARNING: Running makepkg as root...
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found VirtualBox_1.5.6-1_Linux_x86.run in build dir
-> Found vbox.install in build dir
-> Found vbox_build_module in build dir
-> Found vboxnet.patch in build dir
-> Found interfaces in build dir
==> Validating source files with md5sums...
VirtualBox_1.5.6-1_Linux_x86.run ... FAILED
vbox.install ... Passed
vbox_build_module ... Passed
vboxnet.patch ... Passed
interfaces ... Passed
==> ERROR: One or more files did not pass the validity check!
This is what is in the downloaded files dir:-
ls -l
total 48
-rw-r--r-- 1 daz users 3642 2008-05-01 20:06 PKGBUILD
-rw-r--r-- 1 daz users 26055 2008-05-01 20:05 VirtualBox_1.5.6-1_Linux_x86.run
-rwxrwxrwx 1 nobody nobody 217 2008-01-08 20:58 interfaces
drwxrwxrwx 2 root root 125 2008-05-01 20:06 src
-rwxrwxrwx 1 nobody nobody 2717 2008-02-22 18:22 vbox.install
-rwxrwxrwx 1 nobody nobody 174 2008-02-22 17:45 vbox_build_module
-rwxrwxrwx 1 nobody nobody 2179 2007-12-30 12:31 vboxnet.patch
Can anyone help please? In Ubuntu all this was just installed with dpkg -i VirtualBox.deb
I'm sure Arch is just as "simple" :-)
Last edited by keratos (2008-05-04 07:54:14)
Offline
Ah..that one is fairly easy. Edit the PKGBUILD file and remove the md5sum values:
md5sums=('894fa6e75bd47d21d9e0f6e3724b8b1c'
'b5db7f573dd527694588823cb245b513'
'58eca0d128ca2b131881167e8efb382c'
'7279506a30c072906b6898554badd679'
'23d094a975174b7b599fb93bc0c43936')
so that it looks like this:
md5sums=()
Voila! It's because of the temporary *.run file--it doesn't match the original *.run file's md5sum. Once the PKGBUILD is updated, this won't be an issue.
thayer williams ~ cinderwick.ca
Offline
Nearly!!!
Deleting all the lines in md5sums... caused no end of probs.
All I had to do was md5sum [b]VirtualBox_1.5.6-1_Linux_x86.run[/b] and enter the returned checksum in the first line of the md5sums
However, still errors!...
==> Making package: virtualbox_bin 1.5.6-1 (Thu May 1 22:20:34 BST 2008)
==> WARNING: Running makepkg as root...
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found VirtualBox_1.5.6-1_Linux_x86.run in build dir
-> Found vbox.install in build dir
-> Found vbox_build_module in build dir
-> Found vboxnet.patch in build dir
-> Found interfaces in build dir
==> Validating source files with md5sums...
VirtualBox_1.5.6-1_Linux_x86.run ... Passed
vbox.install ... Passed
vbox_build_module ... Passed
vboxnet.patch ... Passed
interfaces ... Passed
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
VirtualBox_1.5.6-1_Linux_x86.run: line 20: syntax error near unexpected token `newline'
VirtualBox_1.5.6-1_Linux_x86.run: line 20: `<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">'
???
WHY oh WHY is this SO difficult.
Offline
Before you dive in at the deep end and try and install Virtualbox without really understanding what you are doing, you should read: http://wiki.archlinux.org/index.php/AUR_User_Guidelines
AUR PKGBUILDs should be saved in a suitable area such that users can build packages (to avoid major mishaps), which can then be installed by the root user (or sudo).
The AUR consists of packages tagged as "community" or "unsupported". Community packages can be installed using the standard pacman -S pkgname command (assuming the Community repository is enabled in pacman.conf).
Searching the AUR for virtualbox using the web frontend shows several relevant packages in Community, see here.
The following community packages should get you started:
virtualbox-ose
virtualbox-modules
virtualbox-ose-additions
If you want to try the others (in unsupported), you'll need to download, compile and install them yourself, in the same way any other non-community AUR package is installed.
The wiki Package management guide should also bring you up to speed on what is possible.
Suggest you don't use yaourt until you are comfortable with installing AUR packages manually. If you need realtime help, join the #Archlinux channel on Freenode on IRC.
Offline
Or try the bin file no problem here yaourt -S virtualbox_bin
Offline
For the record, he did say he was trying to install the PUEL version, which as far as I know isn't available from the repos. Also, the errors he has received aren't related whatsoever to his inexperience--they are purely PKGBUILD/Wiki anomalies.
That said, VirtualBox OSE is adequate for most general use, and it is available in the repos as has been mentioned.
Last edited by thayer (2008-05-02 00:26:01)
thayer williams ~ cinderwick.ca
Offline
Before you dive in at the deep end and try and install Virtualbox without really understanding what you are doing, you should read: http://wiki.archlinux.org/index.php/AUR_User_Guidelines
AUR PKGBUILDs should be saved in a suitable area such that users can build packages (to avoid major mishaps), which can then be installed by the root user (or sudo).
The AUR consists of packages tagged as "community" or "unsupported". Community packages can be installed using the standard pacman -S pkgname command (assuming the Community repository is enabled in pacman.conf).
Searching the AUR for virtualbox using the web frontend shows several relevant packages in Community, see here.
The following community packages should get you started:
virtualbox-ose
virtualbox-modules
virtualbox-ose-additionsIf you want to try the others (in unsupported), you'll need to download, compile and install them yourself, in the same way any other non-community AUR package is installed.
The wiki Package management guide should also bring you up to speed on what is possible.
Suggest you don't use yaourt until you are comfortable with installing AUR packages manually. If you need realtime help, join the #Archlinux channel on Freenode on IRC.
thanks for the reply and the advice, HOWEVER..
I have decided to install from AUR, HAVING READ THE AUR wiki!! The reason I do not wish to use OSE is because it does not support USB devices, but clearly you will know this - wont you.
If we could just focus on the specific problem being encountered, then that would be more useful - thank you for your support.
Last edited by keratos (2008-05-02 06:51:24)
Offline
For the record, he did say he was trying to install the PUEL version, which as far as I know isn't available from the repos. Also, the errors he has received aren't related whatsoever to his inexperience--they are purely PKGBUILD/Wiki anomalies.
CORRECT!
You are on the money here, can you please offer any further assitance thayer??
Offline
Or try the bin file no problem here yaourt -S virtualbox_bin
Good idea, I checked this out originally but it didnt work so I went for "manual" install.
The download from yaourt never starts, just hangs - the server is dead or something?? ...
# yaourt -S virtualbox_bin
==> WARNING: Building unsupported package as root is dangerous.
Please run yaourt as a non-privileged user.
==> Downloading virtualbox_bin PKGBUILD from AUR...
==> Last 5 comments ordered by date (asc):
Comment by: chris_es on 20080414 [17:02:11]
Hello!
Thanks a lot for this package :o)
Just a quick comment about where to copy the Sun .run package. It should be put to where the tarball from AUR was extracted.
In my case, it is /home/[users]/virtualbox-bin/
Cheers
Chris
Comment by: fi-dschi on 20080419 [22:46:37]
You may download the run-file at
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=innotek-1.5.6-G-F@CDS-CDS_SMI
Comment by: GGLucas on 20080421 [00:40:38]
Can't get the kernel module working in 2.6.25, vbox_build_module completes fine, but I get the following error:
$ sudo modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-ARCH/misc/vboxdrv.ko): Unknown symbol in module, or unknown parameter (see dmesg)
with these messages in dmesg:
vboxdrv: Unknown symbol change_page_attr
vboxdrv: Unknown symbol change_page_attr
Comment by: Geekosaurio on 20080422 [03:54:09]
Maybe you could find this instructions helpful
http://www.mail-archive.com/vbox-users@virtualbox.org/msg02889.html
I've not tried this myself but I will do it soon and post the info here. Maybe create a separate package for 2.6.25 kernels it's a good idea.
Comment by: ise on 20080429 [18:12:57]
The vboxdrv from the mailinglist of virtualbox runs here without problems on 2.6.25 with vbox 1.5.6
First Submitted: Sun, 11 Mar 2007 00:52:22 +0000
Last Updated: Fri, 22 Feb 2008 18:26:15 +0000
virtualbox_bin 1.5.6-1 (Unsupported): Powerful x86 virtualization - binary version (non GPL - free for personal use and evaluation)
==> virtualbox_bin dependencies:
- libidl2 (already installed)
- libxslt (already installed)
- qt3 (already installed)
- e2fsprogs (already installed)
- sdl (already installed)
- libstdc++5 (already installed)
- patch (already installed)
==> Edit the PKGBUILD (recommended) ? [Y/n] ("A" to abort)
==> ----------------------------------------------
==>n
==> WARNING: This PKGBUILD contains install file that can be dangerous.
vbox.install
==> Edit vbox.install (recommended) ? [Y/n] ("A" to abort)
==> ----------------------------------------------
==>n
==> Continue the building of 'virtualbox_bin'? [Y/n]
==> ----------------------------------------------
==>y
==> Building and installing package
==> Making package: virtualbox_bin 1.5.6-1 (Fri May 2 06:06:28 BST 2008)
==> WARNING: Running makepkg as root...
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading VirtualBox_1.5.6-1_Linux_x86.run...
--2008-05-02 06:06:29-- http://195.34.175.98/download/1.5.6/VirtualBox_1.5.6-1_Linux_x86.run
Connecting to 195.34.175.98:80...
Last edited by keratos (2008-05-02 05:52:33)
Offline
So why don't you just install from the generic i386 Linux package from the VirtualBox site? I just did it and it took me 5 minutes. All you need to do is download the VirtualBox-1.6.0-Linux_x86.run file, chmod it so it's executable and then run it. Installs to /opt by default in it's own directory... Simple simple.
Offline
And here's proof in the pudding. Everything works for me. Tested the network as well, it was literally that easy.
Offline
Got it. Thanks.
Works perfectly.
I noticed this whilst googleing, however I wasnt sure what a .run is and why it just wasnt a normal executable file with .sh extenstion or something.Why is this?
Offline
Btw: If you don't want/cannot use the OSE version, here is a PKGBUILD. You have to download the 1.6.0 files manually. http://users.archlinux.de/~pierre/packa … irtualbox/
Offline
Btw: If you don't want/cannot use the OSE version, here is a PKGBUILD. You have to download the 1.6.0 files manually. http://users.archlinux.de/~pierre/packa … irtualbox/
USB support is required. OSE does not provide this - unless I am mistaken?!
I attempted PKGBUILD however this did not work - see first post above.
danke irgendwie.
Last edited by keratos (2008-05-04 09:15:16)
Offline
Got it. Thanks.
Works perfectly.
I noticed this whilst googleing, however I wasnt sure what a .run is and why it just wasnt a normal executable file with .sh extenstion or something.Why is this?
If you look at the .run file in a text editor you'll see that it is a script. It just has bits and pieces encoded directly into it. I agree, the installation support on the site is pretty nil, I didn't even see a link to instructions when I went to download it. Oh well, the 1.6 stuff works well -- not even sure why you'd want to try to use the packages when this is so quick and clean.
Last edited by windexh8er (2008-05-04 14:50:22)
Offline
keratos wrote:Got it. Thanks.
Works perfectly.
I noticed this whilst googleing, however I wasnt sure what a .run is and why it just wasnt a normal executable file with .sh extenstion or something.Why is this?
If you look at the .run file in a text editor you'll see that it is a script. It just has bits and pieces encoded directly into it. I agree, the installation support on the site is pretty nil, I didn't even see a link to instructions when I went to download it. Oh well, the 1.6 stuff works well -- not even sure why you'd want to try to use the packages when this is so quick and clean.
agreed!! upstream install was very simple....
i just didnt know what a ".run" file was.
could you possibly elaborate on the "bits and pieces encoded..." bit ??
Offline
<snip> ... not even sure why you'd want to try to use the packages when this is so quick and clean.
Because that's the whole purpose of having a package manager? Do you want to run uninstall scripts to uninstall programs and rely on their correctness? I don't.
@Pierre: Thanks for the PKGBUILDs. Did you send them to the owners of the packages in the AUR?
Haven't been here in a while. Still rocking Arch.
Offline
Do you want to run uninstall scripts to uninstall programs and rely on their correctness? I don't.
Ahem - the scripts etc. contained within a package are no different, their "correctness" is still not guaranteed however it could be argued that there is a qualatative "assessment" made on the package prior to being accepted into the repo, however, this is not guaranteed.
Furthermore, PKGBUILD scripts should be viewable/editable prior to running them, during the build process.
So I do not agree with your statement.
Offline
Sigi wrote:Do you want to run uninstall scripts to uninstall programs and rely on their correctness? I don't.
Ahem - the scripts etc. contained within a package are no different, their "correctness" is still not guaranteed however it could be argued that there is a qualatative "assessment" made on the package prior to being accepted into the repo, however, this is not guaranteed.
What I was referring to was that when a Arch package is installed via pacman, every file in the package can be uninstalled with a "pacman -Rs packagename". If you start to install things with installscripts, probably as user root, how do you make sure that you can get rid of EVERY file the package installed with the script? It is way cleaner to run the script as a dedicated build user or in a chrooted environment and only install the generated pkg.tar.gz.
Furthermore, PKGBUILD scripts should be viewable/editable prior to running them, during the build process.
How do you build packages? Automated? Man, just run
vi PKGBUILD ; makepkg
Haven't been here in a while. Still rocking Arch.
Offline
Well, why not consider posting what you actually mean rather than leave it open for interpretation!
vi PKGBUILD; makepkg
Furthermore, PKGBUILD scripts should be viewable/editable prior to running them, during the build process.
Read again! thats what I said, "Man"
"Man" ???? What's that - some swiss colloquial term?
Last edited by keratos (2008-05-16 05:35:39)
Offline
vi PKGBUILD; makepkg
Furthermore, PKGBUILD scripts should be viewable/editable prior to running them, during the build process.
Read again! thats what I said, "Man"
It certainly is what you said - but that's what is usually done anyway. One doesn't run PKGBUILD scripts, one runs makepkg on the PKGBUILDs. Why sould makepkg let you view/edit PKGBUILDs? You can use any editor you want to do so... I don't get your point.
Haven't been here in a while. Still rocking Arch.
Offline