Package Details: vboxhost-hook 1.1-1

Git Clone URL: https://aur.archlinux.org/vboxhost-hook.git (read-only)
Package Base: vboxhost-hook
Description: mkinitcpio hook to compile the virtualbox host modules
Upstream URL: https://github.com/alucryd/mkinitcpio-hooks
Licenses: GPL3
Submitter: alucryd
Maintainer: alucryd
Last Packager: alucryd
Votes: 101
Popularity: 1.263276
First Submitted: 2013-01-20 16:10
Last Updated: 2015-09-04 14:38

Latest Comments

alexbrinister commented on 2016-03-13 19:42

Oh okay. Thanks for the heads up

Alex Brinister

alucryd commented on 2016-03-13 08:42

alexbrinister: There is no need for this hook anymore, I will remove it soon™. The dkms package now comes with pacman 5 hooks which should take care of the build when you install/upgrade/remove kernel headers and dkms packages.

alexbrinister commented on 2016-03-13 00:17

Helo,

The vbox hook does not work anymore because the VirtualBox source tree has changed name. Below is the correct code for the hook. Perhaps this should be a bug in the Github repository, not a comment here...

build() {
_version=$(pacman -Qs virtualbox-host-dkms | sed 's/^[^ ]* \|-[0-9]*$//g;2d')_OSE
echo "Building virtualbox host modules for ${KERNELVERSION} kernel..."
dkms install vboxhost/$_version -k ${KERNELVERSION}/_arch
}

Alex Brinister

alucryd commented on 2013-08-08 10:38

Thx, glad you like it!

plmosqueda commented on 2013-08-08 03:49

very cool, thanks

ZeroBit commented on 2013-01-26 21:00

@Alucryd: Thanks! It works good!

ZeroBit commented on 2013-01-25 14:25

@Alucryd: Thanks! It works good!

alucryd commented on 2013-01-24 22:37

@ZeroBit: My pleasure!

ZeroBit commented on 2013-01-24 22:36

@Alucryd: Thanks! It works good!

alucryd commented on 2013-01-21 10:24

This package is replacing the old virtualbox-hook.

alucryd commented on 2013-01-20 16:12

This package has been superseded by vboxhost-hook, please use that one instead from now on. virtualbox-hook will be deleted soon.

alucryd commented on 2013-01-19 23:36

@ZeroBit: Sorry about that, I put whitespaces where I shouldn't have during my last update. Thx for reporting it, should work fine now. (Weird thing is, my nvidia hook which is an exact replica did not throw this error.)

ZeroBit commented on 2013-01-19 21:30

Error during
# mkinitcpio -p linux

/usr/lib/initcpio/install/vbox: line 16: warning: here-document at line 13 delimited by end-of-file (wanted `HELPEOF')
/usr/lib/initcpio/install/vbox: line 17: syntax error: unexpected end of file
==> ERROR: Failed to read /usr/lib/initcpio/install/vbox

alucryd commented on 2012-12-25 23:56

@morxa: Thx, I've updated the PKGBUILD.

morxa commented on 2012-12-25 22:44

virtualbox-host-dkms replaces virtualbox-host-source.

Anonymous comment on 2012-09-24 14:01

virtualbox-host-source hit community. thanks for your helps.

alucryd commented on 2012-09-22 16:40

@romainhk: I won't, because not everyone is using the stock kernel. Anyone who installs this package should know they need headers anyway.

romainhk commented on 2012-09-22 16:38

because it build a module, can you add the linux-headers dependency ?

engelus commented on 2012-09-19 11:23

Hi in the last update I found a new service called dkms.service is that service achievment the same function of this hook? Thanks.

alucryd commented on 2012-09-18 07:12

@dlin: Read below...

@msx: No problem, glad it's working great for you!

dlin commented on 2012-09-18 05:53

error: target not found: virtualbox-host-source

msx commented on 2012-09-17 14:05

*Update*
So far everything is working great here with the [community-testing] repo enabled.
Thanks again.

alucryd commented on 2012-09-17 13:06

@msx: Sorry I was too hasty and didn't check where the new vbox came from: the package is still in community-testing http://www.archlinux.org/packages/?q=virtualbox-host-source, please do not update virtualbox-hook until vbox 4.2 hits community (or enable community-testing ;).

msx commented on 2012-09-17 11:44

@Alucryd there isn't yet a virtualbox-host-source package so I presume it will be available when VB 4.2 hits AUR, right?
BTW, thanks for your work, I'm a daily user of VirtualBox.

alucryd commented on 2012-09-17 08:38

Updated for new naming of vbox packages. Please remove this package, update your system, and reinstall it afterwards.

alucryd commented on 2012-08-30 07:04

@ShadowKyogre: This package was the first time I ever used regex, I see you're much more adept than me^^ I've used your command, and it seems to work great, plus it works with any locale, thx! As for arch, it is queried and modified by the PKGBUILD when you build the package on your computer

alucryd commented on 2012-08-29 07:23

@ShadowKyogre: This package was the first time I ever used regex, I see you're much more adept than me^^ I've used your command, and it seems to work great, plus it works with any locale, thx! As for arch, it is queried and modified by the PKGBUILD when you build the package on your computer

alucryd commented on 2012-08-29 07:23

@ShadowKyogre: This package was the first time I ever used regex, I see you're much more adept than me^^ I've used your command, and it seems to work great, plus it works with any locale. As for arch arch, it is queried and modified by the PKGBUILD when you build the package on your computer

ShadowKyogre commented on 2012-08-28 23:59

Updated that last command to the following after toying around with sed a bit more: pacman -Qs '^virtualbox$'|sed 's/^[^ ]* \|-[0-9]*$//g;2d'

ShadowKyogre commented on 2012-08-28 23:51

@Alucryd: I managed to trim off a few characters off of getting the version for a package, but it's still probably messy:
pacman -Qs '^virtualbox$'|head -n1|sed 's&^[^ ]* \|-[0-9]*$&&g'

Aside from this, I notice that you have ${KERNELVERSION}/arch instead of ${KERNELVERSION}/<some appropriate specific architecture like mentioned in the VirtualBox Arch Linux wiki page>. I haven't installed the package yet, but does putting /arch instead of the specific architecture still make it run fine?

ShadowKyogre commented on 2012-08-28 23:49

@Alucryd: I managed to trim off a few characters off of getting the version for a package, but it's still probably messy:
pacman -Qs '^virtualbox$'|head -n1|sed 's&local/virtualbox \|-[0-9]*$&&g'

Aside from this, I notice that you have ${KERNELVERSION}/arch instead of ${KERNELVERSION}/<some appropriate specific architecture like mentioned in the VirtualBox wiki>. I haven't installed the package yet, but does putting /arch instead of the specific architecture still make it run fine?

alucryd commented on 2012-08-28 15:01

Oh nice one ennorie, I hadn't thought about other languages, I'll update the package asap. Thx!

ennorie commented on 2012-08-28 14:04

suggest :
LANG=en_EN pacman -Qi virtualbox-source
or something, for grep Version to work with languages other then English.

alucryd commented on 2012-08-07 08:03

New new vbox hook: I was going to update the hook with every virtualbox update because of the way the dkms command works: it needs the virtualbox version, and at first I thought recreating the hook files using the PKGBUILD version was a good idea.

However, I just came up with a (probably very ugly) way to make the hook directly query the virtualbox version, so here it is, hook 2.0 final (sorry for the downgrade guys).

alucryd commented on 2012-08-04 14:52

New vbox hook: vbox now uses dkms to build the kernel modules, you can either add dkms to your DAEMONS array in mkinitcpio (wiki says it doesn't work for now, haven't tested though) or continue to use this hook, which will call dkms and build the modules for you.

alucryd commented on 2012-07-17 08:04

Okay I won't have time to reinstall Arch before a week or two but here's the modified pkgbuild, please tell me if it breaks anything.

Anonymous comment on 2012-07-16 16:34

only got this pkg left w/ /lib dependencies. thank you for your time!

alucryd commented on 2012-07-15 22:11

Indeed, I'll have to modify it when I get my arch boxes back on their feet. For the time being it should work since /lib is a symlink to /usr/lib anyway.

daurnimator commented on 2012-07-15 07:33

This package uses files in /lib
See https://wiki.archlinux.org/index.php/DeveloperWiki:usrlib

alucryd commented on 2012-05-23 07:18

Updated the package, no more editing of system files. Also modified the wiki to reflect the changes. Thx for the heads up guys.

alucryd commented on 2012-05-23 07:17

Updated the package, no more editing of system files. Also modified the wiki to reflect the changes.

alucryd commented on 2012-05-22 18:03

Fine, it seems I was wrong and I apologize. I would have thought that a package as widely used as catalyst would at least meet the arch requirements. I will modify my install script so it only tells the user what to do.

@seblu: You sounded like you believed I would make a virtualbox-bin-hook in your comment, well at least that's how I understood it^^

alucryd commented on 2012-05-22 18:02

Fine, it seems I was wrong and I apologize. I would have thought that a package as widely used as catalyst would at least meet the arch requirements. I will modify my install script so it only tell the user what to do.

@seblu: You sounded like you believed I would make a virtualbox-bin-hook in your comment, well at least that's how I understood it^^

seblu commented on 2012-05-22 17:53

@Alucryd: I answered to your statement about virtualbox-bin and module compiling. Not related to virtualbox!

It's not because users are free to install apps from AUR you can do anything. The control is not done uploading but haphazard way. You cannot provide a package which remove all users system and expect it will stay in AUR by example.

Catalyst is a _bad_ example, config files must not be automagically updated (espicially those one), as daemon must not be added automagically to rc.conf!
I asked to others TUs/Dev and in one sentence: "scripts touching configuration files is plain wrong".

seblu commented on 2012-05-22 17:48

@Alucryd: I answered to your statement about virtualbox-bin and module compiling. Not related to virtualbox!

It's not because users are free to install apps from AUR you can do anything. The control is not done uploading but haphazard way. You cannot provide a package which remove all users system and expect it will stay in AUR by example.

Catalyst is a _bad_ example, config files must not be automagically updated (espicially those one), as daemon must not be added automagically to rc.conf!
To quote ioni, maintainer of catalyst package: "scripts touching configuration files is plain wrong".

falconindy commented on 2012-05-22 17:38

Sorry, but you are flat out _wrong_ to modify user config in an install scriptlet. This is Arch, not Debian. No official package will ever do this, and pointing at another poorly written package in the AUR is not a reasonable justification.

alucryd commented on 2012-05-21 19:53

And virtualbox does not come with vboxdrv hence this package. I fail to see why I *must* not modify pacman.conf and mkinitcpio.conf when catalyst packages have done exactly the same for a very long time. Plus installing an aur package is up to the user, if anybody doesn't like my install script, they're free to compile the modules manually whenever they upgrade kernels.

seblu commented on 2012-05-21 19:40

for at least one year, virtualbox-bin support building module at boot time via /etc/rc.d/vboxdrv.

Your install script modify /etc/pacman.conf and /etc/mkinitcpio.conf. You must not do that!

alucryd commented on 2012-05-15 15:12

@DSpider: There is no need for me to make another package for virtualbox-bin. Seblu is going to change his PKGBUILD to work with dkms soon, which will handle the modules compilation and loading for you. BTW, I don't know if it's a specific USB support you need, but the regular virtualbox handle this perfectly if you install the extension package.

DSpider commented on 2012-05-15 14:34

I'm using "virtualbox-bin" (PUEL edition, the one with USB support) and /usr/bin/vboxbuild doesn't even exist. Can you make a "virtualbox-bin-hook" AUR package with a different "vbox" file? http://pastie.org/3915404

Or maybe adapt it with an "[" so that it checks if pacman has "virtualbox-bin" installed? Thanks.

alucryd commented on 2012-04-08 14:56

@benben: It happens when linux-headers hasn't been updated, updating it will take care of the error line and compilation will proceed. Installing the package should have added linux-headers in the SyncFirst array of /etc/pacman.conf, if not can you add it and try rebuilding your initramfs?
BTW, the unloading/reloading errors sometimes happens to me too, but the modules are built regardless.

Anonymous comment on 2012-04-08 12:08

thanks for this nice little thingy but I get the following error:


Building virtualbox modules for 3.3.1-1-ARCH kernel...
:: Unloading VirtualBox kernel modules [BUSY] [FAIL]
error: `/lib/modules/3.3.1-1-ARCH/build' does not appear to be a valid kernel build directory.
:: Reloading VirtualBox kernel modules [BUSY] [FAIL]
Ok.

what am I missing?