> Would'n a dependency be a solution to this?
The module already depends on a kernel version, which causes already other problems (bug 226960)
> Why are the vbox modules not available when there is a kernel update?
It's not that easy. The packages are maintained independently (and virtualbox-ose(-modules) is only community-maintained, which currently means "by me").
See https://bugs.edge.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/179807/comments/32 - it seems like we can get this fixed for Intrepid and hopefully also for Hardy.
> Would'n a dependency be a solution to this?
The module already depends on a kernel version, which causes already other problems (bug 226960)
> Why are the vbox modules not available when there is a kernel update? ose(-modules) is only community- maintained, which currently means "by me"). /bugs.edge. launchpad. net/ubuntu/ +source/ virtualbox- ose/+bug/ 179807/ comments/ 32 - it seems like we can get this fixed for Intrepid and hopefully also for Hardy.
It's not that easy. The packages are maintained independently (and virtualbox-
See https:/