Virtualbox-OSE gone from Trisquel 6?
Hi,
I noticed this bug recently:
https://trisquel.info/en/issues/4456
It's not clear if that also meant removing VirtualBox-OSE, which I can't
find in the packages in Trisquel 6.
Can anyone clarify this?
BTW packages.trisquel.info seems down for a few days now, making it more
difficult to compare such packages removal.
Cheers,
Fabian
--
Fabián Rodríguez
http://fsf.magicfab.ca
I certainly hope VirtualBox is gone. Despite its popularity its technical quality is very poor http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw
Other virtualization software is surely better.
VB from the Ubuntu/Trisquel repos is outdated and it is best to grab it from their repository at https://www.virtualbox.org/wiki/Linux_Downloads
With that enabled, does it fix your issue?
It will not fix the issue since the issue is on the Kernel side where the drivers have been removed because of their lack of quality (funny to know that they have not been removed from Parabola).
On 13-01-07 05:37 AM, name at domain wrote:
> It will not fix the issue since the issue is on the Kernel side where
> the drivers have been removed because of their lack of quality (funny
> to know that they have not been removed from Parabola).
Wow, by that logic ("lack of quality"), many more packages would be
removed from Trisquel. Packages for software that doesn't work/crashes
should also be removed then.
Removing VirtualBox actually encourages using the non-free version
packaged on Oracle's site, btw.
The drivers haven't been removed from the "Kernel side", they have been
merely been marked for the amount of bug reports they were making the
automated bug reporting tools fill.
Read the Phoronix article comments carefully, you'll find eveyrone has
an *opinion* on the quality of such drivers, but removing them (and
VirtualBox) isn't going to help.
Cheers,
Fabian
--
Fabián Rodríguez
http://trisquel.magicfab.ca
I am telling this because I've never been able to install or use any Virtualbox (Free or not Free) under Trisquel 5.5 or Trisquel 6.0 always because of the same error while the module was compiling (from the Trisquel servers or from the Oracle's website).
When I searched for the answers that was what they gave me for an answer. But it is quite weird to know that it works on Parabola tho.
UPDATE : I found this old post that can explain a lot of miss understanding.. if anyone can test this that would be great --> https://trisquel.info/en/forum/problem-installing-virtualbox
> Removing VirtualBox actually encourages using the non-free
> version packaged on Oracle's site, btw.
I was under the impression that VirtualBox is now free software? According to their website, the "Extension Pack" is proprietary software, but the VB downloads are GPLv2.
I agree that linking to the VB website might lead users to download the extension pack though.
On 13-01-06 11:00 PM, name at domain wrote:
> VB from the Ubuntu/Trisquel repos is outdated and it is best to grab
> it from their repository at
> https://www.virtualbox.org/wiki/Linux_Downloads
>
> With that enabled, does it fix your issue?
Apparently so. VirtualBox-OSE and VirtualBox used to be two different
things:
https://www.virtualbox.org/wiki/Licensing_FAQ
It seems since version 4 such is not the case:
http://en.wikipedia.org/wiki/Virtualbox#Licensing
F.
--
Fabián Rodríguez
http://trisquel.magicfab.ca
>BTW packages.trisquel.info seems down for a few days now
I don't know other people's needs for using Virtualbox, but I have been using KVM + virt-manager for almost a year now, coincidentally because I couldn't get Virtualbox to run with the latest kernels (via jxself's repo).
Just some comments from my side on KVM + virt-manager:
- I use it primarily for headless servers.
- I've tested live distros in there. There is a known issue regarding sound. There is also a workaround but apparently it might lead to security issues in the VM. I don't know how serious this is, but I only did that long ago. I'm not using the workaround now, so there's no sound, which is not an issue for me at the moment.
- The virt-manager UI is unrefined compared to Virtualbox, but for me it wasn't an issue.
- You need a CPU that supports virtualisation.
https://help.ubuntu.com/community/KVM might be a useful read.