Difference between revisions of "Talk:VirtualBox"
m (Mmcmahon moved page Talk:Virtualbox to Talk:VirtualBox: Match other entry with correct case.) |
(Add reasoning and alternative for VirtualBox) |
||
| Line 1: | Line 1: | ||
| − | This program exists and is widely used in the GNU-Linux user community. If there are freedom issues with it, wouldn't it be better to have an entry in the FSD explaining what those are, rather than no information at all? I'm guessing FSD has policies on issues like this, but if it wouldn't break any of them, I would be willing to create a page if someone can point me to some links to an assessment of the freedom issues with VB. --[[User:Strypey|Strypey]] ([[User talk:Strypey|talk]]) 11:27, 3 May 2018 (EDT) | + | * This program exists and is widely used in the GNU-Linux user community. If there are freedom issues with it, wouldn't it be better to have an entry in the FSD explaining what those are, rather than no information at all? I'm guessing FSD has policies on issues like this, but if it wouldn't break any of them, I would be willing to create a page if someone can point me to some links to an assessment of the freedom issues with VB. --[[User:Strypey|Strypey]] ([[User talk:Strypey|talk]]) 11:27, 3 May 2018 (EDT) |
| + | |||
| + | * Not sure if [https://www.virtualbox.org/ticket/12011 this issue] still applies, but my understanding is that the BIOS and the toolchain to build the BIOS for VirtualBox is proprietary. The VirtualBox team was not interested in spending resources to fix it and the community did not fix it either. [https://packages.debian.org/search?keywords=virtualbox&searchon=names&suite=stable§ion=all VirtualBox is not present in Debian] or other distributions. If you are looking for an alternative, the FSF system administrators use [[Virt-manager]] extensively which has a similar yet different workflow. [[User:Mmcmahon|Mmcmahon]] ([[User talk:Mmcmahon|talk]]) 12:59, 27 October 2022 (EDT) | ||
Latest revision as of 12:59, 27 October 2022
- This program exists and is widely used in the GNU-Linux user community. If there are freedom issues with it, wouldn't it be better to have an entry in the FSD explaining what those are, rather than no information at all? I'm guessing FSD has policies on issues like this, but if it wouldn't break any of them, I would be willing to create a page if someone can point me to some links to an assessment of the freedom issues with VB. --Strypey (talk) 11:27, 3 May 2018 (EDT)
- Not sure if this issue still applies, but my understanding is that the BIOS and the toolchain to build the BIOS for VirtualBox is proprietary. The VirtualBox team was not interested in spending resources to fix it and the community did not fix it either. VirtualBox is not present in Debian or other distributions. If you are looking for an alternative, the FSF system administrators use Virt-manager extensively which has a similar yet different workflow. Mmcmahon (talk) 12:59, 27 October 2022 (EDT)
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.