VirtualBox-kmod fails to build on -CURRENT

[Bernhard Fröhlich]

On Di.,   1. Nov. 2011 18:33:54 CET, Ed Schouten <ed at 80386.nl> wrote:

> * Marco Steinbach <coco at executive-computing.de>, 20111101 18:18:
> > You were right about the device naming, I had to create a symlink.
> 
> Okay. I've attached a new version of the patch that:
> 
> - Adds a symbolic link from /dev/vboxdrv0 to /dev/vboxdrv automatically,
> - Changes the code to use /dev/vboxdrv.
> 
> This means the kernel module is backwards compatible, but VirtualBox
> itself isn't. This is probably a good compromise.
> 
> I trust that the warnings and traces you are seeing are in no way
> related to my patch, so I suppose you're better off reporting those to
> the VirtualBox developers.
> 
> decke@, (or who else maintains VirtualBox), will you do the honour of
> getting the patch upstreamed/applied locally? The patch probably has to
> be used by both the virtualbox-ose and the virtualbox-ose-kmod port.
> Thanks!

Thanks a lot for the patch. To be able to submit it upstream please reply if it is okay that the patch is licensed under the MIT License so that Oracle can include it in their products.