Updated ebuilds on jokey's overlay[1] as usual, updated kernel modules tarball is on my webspace[2].

[1] http://overlays.gentoo.org/dev/jokey
[2] http://gentoo.zerodev.it/files/vbox-kernel-module-src-3.0.12.tar.bz2

As usual i updated the ebuilds on jokey's overlay[1], the updated kernel modules tarball is on my webspace[2].

As usual many thanks to Patrick (bonsaikitten) for the review and the quick proxy commit in portage!

[1] http://overlays.gentoo.org/dev/jokey
[2] http://gentoo.zerodev.it/files/vbox-kernel-module-src-3.0.10.tar.bz2

As usual i updated the ebuilds on jokey's overlay[1], the updated kernel modules tarball is on my webspace[2].

[1] http://overlays.gentoo.org/dev/jokey
[2] http://gentoo.zerodev.it/files/vbox-kernel-module-src-3.0.8.tar.bz2

UPDATE:
Due a critical bug[2] virtualbox upstream silently updated (the official
announcement should be posted later) the virtualbox-bin amd64 binary[3]
i just revbumped on jokey's overlay[1] app-emulation/virtualbox-bin to 3.0.6-r1

[1] http://overlays.gentoo.org/dev/jokey
[2] http://www.virtualbox.org/ticket/616
[3] http://vbox.innotek.de/pipermail/vbox-dev/2009-September/001822.html

Days ago noticed that finally Id released the linux port (and the QuakeLive.com Game Launcher addon for firefox) for the linux os.

The installation is obviously straightforward:
- visit www.quakelive.com
- register, login install the plugin and restart firefox
- visit the site again and the game will download all the necessary files
- enjoy!

Another good game, and good porting for linux too, by Id Software, Inc!
[ Finally i can drop the additional windows xp hard drive used for QuakeLive ]

I just bumped the following ebuilds too:

• net-libs/gsoap (2.7.13)
• dev-util/kbuild (0.1.5-r2 aka r2336)

[1] http://overlays.gentoo.org/dev/jokey

Step 1 - (Create a new interface):
First you have to add a new hostonly/dhcp interface using the command:

/opt/VirtualBox/VBoxNetAdpCtl add

Note that at the moment the interface name is harcoded/determined by the
"VBoxNetAdpCtl" command, so you can't call it for istance
"foobarif0", a fixed name "vboxnetN" will be assigned (eg: vboxnet1)

Step 2 - (Add and enable a dhcp server)
Now you can add, if you wish to, a dhcp server to the new interface
"vboxnet1" and configure a dhcp range, for example, with the command:

VBoxManage dhcpserver modify --ifname vboxnet1 \
--ip 192.168.1.254 --netmask 255.255.255.0 \
--lowerip 192.168.1.0 --upperip 192.168.1.250 --enable

Step 3 - (Register the interface and enable HostOnly newtworking)
Now you can register the "new" hostonly, dhcp enabled,
interface "vboxnet1" with an existing VirtualMachine with the
following commands:

VBoxManage modifyvm wxp --nic1 hostonly
VBoxManage modifyvm wxp --hostonlyadapter1 vboxnet1

Step 4 - (Start the VM with VBoxRDP)
Finally you can start the VirtualMachine (and connect later to it
via RDP with an rdp client, rdesktop for example), let's fire up the
VirtualMachine with the command:

VBoxVRDP -s MachineName

Enjoy

Notes:
Not sure if it is a bug or a default behaviour but keep in mind
that a new/different hostonly adapter must be first created
manually with "VBoxNetAdpCtl" and then registered later with the
virtualmachine, on the official manual this is not reported[1].

[1] http://www.virtualbox.org/manual/UserManual.html#vboxmanage-dhcpserver

today VirtualBox 3.0.2 was released, it's a maintenance release this means that it will contain only bugfixes[1] and no new features.

Updated ebuilds are available on jokey's overlay as usual[2].

[1] http://www.virtualbox.org/wiki/Changelog
[2] http://overlays.gentoo.org/dev/jokey