[opensuse-factory] Tumbleweed - Virtualbox policy and Thunderbird
Hi, I have read some time ago that Virtualbox was removed from Tumbleweed because of the not so easy maintainable kernel source. If Virtualbox doesn't support the Tumbleweed Kernel version out of the box it is fine that Virtualbox isn't compiled in Tumbleweed but if it does support it the effort can't be that high I suppose? So isn't it possible to ship the Virtualbox kernel module as soon as it is supported from the vendor? In general I would prefer something like DKMS for openSUSE. It is stupid that a kernel version is "hardcoded" in one version while the sources are available and other Kernels are supported. With DKMS we wouldn't have the problem now I suppose. Anyway this is another issue, not a Tumbleweed one. A MozillaThunderbird 5 upgrade with the compatible Enigmail would be great. It is already in factory. Thanks Tim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Jul 16, 2011 at 03:55:51PM +0200, Tim wrote:
Hi,
I have read some time ago that Virtualbox was removed from Tumbleweed because of the not so easy maintainable kernel source.
If Virtualbox doesn't support the Tumbleweed Kernel version out of the box it is fine that Virtualbox isn't compiled in Tumbleweed but if it does support it the effort can't be that high I suppose? So isn't it possible to ship the Virtualbox kernel module as soon as it is supported from the vendor?
No, if the virtualbox kmp is in the tumbleweed repo, it will cause breakage for people who use it when the updated kernel breaks any update for it. And as there is no "support" from the vendor for this code, there's not much I can do sorry. I have heard of people using the virtualbox repo that is built against tumbleweed fairly successfully, and recommend doing that if you really are stuck using virtualbox.
In general I would prefer something like DKMS for openSUSE. It is stupid that a kernel version is "hardcoded" in one version while the sources are available and other Kernels are supported. With DKMS we wouldn't have the problem now I suppose.
Heh, no, it would be the same problem, DKMS doesn't solve this at all.
A MozillaThunderbird 5 upgrade with the compatible Enigmail would be great. It is already in factory.
What packages specifically are you looking for? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 07/17/2011 07:21 PM, Greg KH wrote:
On Sat, Jul 16, 2011 at 03:55:51PM +0200, Tim wrote:
Hi,
I have read some time ago that Virtualbox was removed from Tumbleweed because of the not so easy maintainable kernel source.
If Virtualbox doesn't support the Tumbleweed Kernel version out of the box it is fine that Virtualbox isn't compiled in Tumbleweed but if it does support it the effort can't be that high I suppose? So isn't it possible to ship the Virtualbox kernel module as soon as it is supported from the vendor?
No, if the virtualbox kmp is in the tumbleweed repo, it will cause breakage for people who use it when the updated kernel breaks any update for it.
And as there is no "support" from the vendor for this code, there's not much I can do sorry. I have heard of people using the virtualbox repo that is built against tumbleweed fairly successfully, and recommend doing that if you really are stuck using virtualbox.
In general I would prefer something like DKMS for openSUSE. It is stupid that a kernel version is "hardcoded" in one version while the sources are available and other Kernels are supported. With DKMS we wouldn't have the problem now I suppose.
Heh, no, it would be the same problem, DKMS doesn't solve this at all.
A MozillaThunderbird 5 upgrade with the compatible Enigmail would be great. It is already in factory.
What packages specifically are you looking for?
thanks,
greg k-h
Virtualbox hasn't needed additional kernel modules in my Tumbleweed for quite some time. [Unless it's happening and I didn't notice, nah surely not]. It's been a month or two since I needed to use a kmp-virtualbox RPM. Currently using kernel-desktop-2.6.39.2-36.1.x86_64 and VirtualBox-4.0-4.0.12_72916_openSUSE114-1.x86_64 Works for me with windows and Linux VMs. Try it and see. John -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 07/17/2011 11:21 AM, Greg KH wrote:
On Sat, Jul 16, 2011 at 03:55:51PM +0200, Tim wrote: No, if the virtualbox kmp is in the tumbleweed repo, it will cause breakage for people who use it when the updated kernel breaks any update for it. I would prefer temporary breakups than it not working at all without user interaction. And as there is no "support" from the vendor for this code, there's not much I can do sorry. I have heard of people using the virtualbox repo that is built against tumbleweed fairly successfully, and recommend doing that if you really are stuck using virtualbox. Ok, I will search for a separate Tumbleweed Virtualbox repository.
I wouldn't call it stuck. Virtualbox is much more user friendly than Qemu/KMS. I tried to Switch to KMS but imho it can't compete in the area of Desktop virtualization besides being to complicated for the use case.
In general I would prefer something like DKMS for openSUSE. It is stupid that a kernel version is "hardcoded" in one version while the sources are available and other Kernels are supported. With DKMS we wouldn't have the problem now I suppose. Heh, no, it would be the same problem, DKMS doesn't solve this at all. When I have upgraded my Kernel in Debian or Ubuntu all the packages which needed separate modules were still working since they were compiled against the current Kernel after installation. Of course this did/does only work if the new Kernel is supported by the module source. In Opensuse if I use a different kernel all these packages doesn't work since they only have precompiled modules. Another disadvantage is that even with every (bigger?) official Kernel update the modules have to be updated.
I don't see the problem with the compilation during installation besides the need for some extra packages?
packagesA MozillaThunderbird 5 upgrade with the compatible Enigmail would be great. It is already in factory. What packages specifically are you looking for? Mozilla Thunderbird 5 and its dependency. The current Thunderbird Enigmail addon would break with the new version so it would needed to be updated too I suppose. I am not sure if there are other Thunderbird addons in the repository.
Thanks Tim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 17 July 2011 15:00, Tim
On 07/17/2011 11:21 AM, Greg KH wrote:
On Sat, Jul 16, 2011 at 03:55:51PM +0200, Tim wrote: No, if the virtualbox kmp is in the tumbleweed repo, it will cause breakage for people who use it when the updated kernel breaks any update for it. I would prefer temporary breakups than it not working at all without user interaction.
John Andrews (swerdna) posts his repos including Vbox in this thread. http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/462176... Do please post there if that doesn't help, I feel like getting Vbox running to. I think you must have meant "KVM" before, KMS is a fairly recent graphics development (Kernel Mode Setting). Think Virtual Box was based on Qemu, I quite agree about the interface & "out of the box" running, for the occasional use rather than multiple VM guests on a server machine, where the GUI becomes backage. Regards Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Greg KH -
John Andrews (swerdna) -
Rob OpenSuSE -
Tim