[opensuse-factory] Poll of VirtualBox users
Hi, A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2020-03-19 04:29 PM, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Thanks,
Larry
I think it would be a good idea. It's always "fun" trying to find it to download. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a):
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
I might be missing something, but the add-on You are supposed to install in the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-) -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
Hi, Am 19.03.20 um 21:38 schrieb Vojtěch Zeisek:
Hi
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package. I might be missing something, but the add-on You are supposed to install in
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a): the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
No, it's the extension pack for the host system with their own license that you have to download from the Oracle Website in order to activate some features: https://www.virtualbox.org/wiki/Downloads#VirtualBox6.1.4OracleVMVirtualBoxE... And I don't think having an automatic download from a third-party website is something Oracle or the OpenSUSE users would appreciate. Ben -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 19/03/2020 21:51, Ben Greiner wrote:
Hi,
Am 19.03.20 um 21:38 schrieb Vojtěch Zeisek:
Hi
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package. I might be missing something, but the add-on You are supposed to install in
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a): the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
No, it's the extension pack for the host system with their own license that you have to download from the Oracle Website in order to activate some features: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.virtualbox.org_wiki_Downloads-23VirtualBox6.1.4OracleVMVirtualBoxExtensionPack&d=DwIDaQ&c=thdlSQUKcAunxaltNxOnpA&r=rQMCMl4AQx8LkqcV6Z_KaNDuQW75wf_RzKbpnczVnKo&m=A6r7VQQ8-S-AdlYvkoC9M58BqhWtrXp1kKIsONTYO3k&s=hAQCVQsiirzOv1OedlxQk1SY7J7Dvitb8eY-_EO8ZZs&e=
And I don't think having an automatic download from a third-party website is something Oracle or the OpenSUSE users would appreciate.
+1 Providing a way to ease the installation of the extension pack is fine by me (although the current process didn't strike me as particularly difficult), but I would definitely not call it automatically after the installation of VBox itself. I'm sure I'm not the only one using VBox in a professional setting: in this context, you have to be very careful about sticking to the letter of the license. Just my 2¢ Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com Disclaimer | Use of IBA e-communicationhttps://iba-worldwide.com/disclaimer The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 3/19/20 3:38 PM, Vojtěch Zeisek wrote:
Hi
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a):
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
I might be missing something, but the add-on You are supposed to install in the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item. What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 19/03/2020 21.56, Larry Finger wrote:
On 3/19/20 3:38 PM, Vojtěch Zeisek wrote: ...
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
I think that would be nice. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Dne čtvrtek 19. března 2020 21:56:11 CET, Larry Finger napsal(a):
On 3/19/20 3:38 PM, Vojtěch Zeisek wrote:
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a):
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post- install routine for the openSUSE package.
I might be missing something, but the add-on You are supposed to install in the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Ah, sorry, I didn't get correct purpose of the script. This would IMHO indeed be very useful. :-) -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
Yes, that would be great!
Schöne Grüße
Axel
--
Written from cell phone - excuses for typos
Am 19. März 2020 22:04:54 MEZ schrieb "Vojtěch Zeisek"
Dne čtvrtek 19. března 2020 21:56:11 CET, Larry Finger napsal(a):
On 3/19/20 3:38 PM, Vojtěch Zeisek wrote:
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a):
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post- install routine for the openSUSE package.
I might be missing something, but the add-on You are supposed to install in the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Ah, sorry, I didn't get correct purpose of the script. This would IMHO indeed be very useful. :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 3/20/20 7:26 AM, Larry Finger wrote:
On 3/19/20 3:38 PM, Vojtěch Zeisek wrote:
Hi
Dne čtvrtek 19. března 2020 21:29:19 CET, Larry Finger napsal(a):
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
I might be missing something, but the add-on You are supposed to install in the quest OS, aren't You? So If I install e.g. Windows (poke) in VB... I guess the script wouldn't be able to install the VB add-ons on that guest Windows, would it? So... I might be missing the point of it...? Otherwise, anything simplifying getting guest add-ons to installed VM is fine. :-)
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Is SUSE's Legal team happy to interpret that license in this way? otherwise the package is likely not to pass a legal review. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Fri, Mar 20, 2020 at 09:45:49AM +1030, Simon Lees wrote:
On 3/20/20 7:26 AM, Larry Finger wrote:
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Is SUSE's Legal team happy to interpret that license in this way? otherwise the package is likely not to pass a legal review.
We used to have something like that for TTF font pack from Microsoft but it was a package (pullin-msttfonts or so - I still have a lock for it on some older systems) which anyone could decide not to install (IIRC it was installed by default for some period of time). I'm pretty sure there are people who would object to mandatory installation of strangely lincensed Oracle stuff so I would suggest such script to be in a separate subpackage so that anyone could decide not to have it. It could still be installed by default (majority of virtualbox users seems to want it) but there should be an option to opt out. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2020-03-20 07:38, Michal Kubecek wrote:
I'm pretty sure there are people who would object to mandatory installation of strangely lincensed Oracle stuff so I would suggest such script to be in a separate subpackage so that anyone could decide not to have it. It could still be installed by default (majority of virtualbox users seems to want it) but there should be an option to opt out.
Doesn't PUEL conflict with the use at work / in companies? I'd suggest to avoid to automatically install such license trap for those who do not know about or care explicitly. I'm not a lawyer, but since the license is much different to the other OSS packages, probably the user will at least have to acknowledge it at installation time. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2020-03-20 at 08:08 +0100, Bernhard Voelker wrote:
On 2020-03-20 07:38, Michal Kubecek wrote:
I'm pretty sure there are people who would object to mandatory installation of strangely lincensed Oracle stuff so I would suggest such script to be in a separate subpackage so that anyone could decide not to have it. It could still be installed by default (majority of virtualbox users seems to want it) but there should be an option to opt out.
Doesn't PUEL conflict with the use at work / in companies? I'd suggest to avoid to automatically install such license trap for those who do not know about or care explicitly.
I'm not a lawyer, but since the license is much different to the other OSS packages, probably the user will at least have to acknowledge it at installation time.
Have a nice day, Berny
All of openSUSE's packages, including our non-oss repo packages, should have no restrictions on how the software is used (eg. preventing commercial use) So on that grounds, I strongly dislike this suggestion. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 3/20/20 5:08 PM, Michal Kubecek wrote:
On Fri, Mar 20, 2020 at 09:45:49AM +1030, Simon Lees wrote:
On 3/20/20 7:26 AM, Larry Finger wrote:
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Is SUSE's Legal team happy to interpret that license in this way? otherwise the package is likely not to pass a legal review.
We used to have something like that for TTF font pack from Microsoft but it was a package (pullin-msttfonts or so - I still have a lock for it on some older systems) which anyone could decide not to install (IIRC it was installed by default for some period of time).
I'm pretty sure there are people who would object to mandatory installation of strangely lincensed Oracle stuff so I would suggest such script to be in a separate subpackage so that anyone could decide not to have it. It could still be installed by default (majority of virtualbox users seems to want it) but there should be an option to opt out.
From memory I think that package was in the non-free repo i'm guessing it would be best to do similar here. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Fri, 20 Mar 2020 07:38:32 +0100, Michal Kubecek
On Fri, Mar 20, 2020 at 09:45:49AM +1030, Simon Lees wrote:
On 3/20/20 7:26 AM, Larry Finger wrote:
It is not the guest additions. That needs to be done from within the guest. I also need to run VM versions of Windows for certain tasks. At least, you can now download and install that iso file from the "Devices" menu item.
What I am talking about here is the PUEL-licensed stuff that adds the USB 2 and USB 3 drivers to the host code. With that license, we cannot distribute, but we could supply a script that ensures that it is always updated when you update to a new version of VB.
Is SUSE's Legal team happy to interpret that license in this way? otherwise the package is likely not to pass a legal review.
We used to have something like that for TTF font pack from Microsoft but it was a package (pullin-msttfonts or so - I still have a lock for it on some older systems) which anyone could decide not to install (IIRC it was installed by default for some period of time).
It is still available (and installed on most of my boxes) 12.2 fetchmsttfonts-11.4-10.1.4.noarch 13.1 fetchmsttfonts-11.4-15.3.1.noarch 13.2 fetchmsttfonts-11.4-17.3.1.noarch 42.1 fetchmsttfonts-11.4-18.5.noarch 15.1 fetchmsttfonts-11.4-lp151.43.1.noarch TW fetchmsttfonts-11.4-23.1.noarch
I'm pretty sure there are people who would object to mandatory installation of strangely lincensed Oracle stuff so I would suggest such script to be in a separate subpackage so that anyone could decide not to have it. It could still be installed by default (majority of virtualbox users seems to want it) but there should be an option to opt out.
Michal Kubecek
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.31 porting perl5 on HP-UX, AIX, and Linux https://useplaintext.email https://tux.nl http://www.test-smoke.org http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
On Thu, 19 Mar 2020 15:29:19 -0500, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Personally, I really like the idea. I usually forget to look on my mostly-headless system that I run VB on, and after an upgrade, I sometimes am caught out by the fact that the extensions also needed to be upgraded, and that sometimes prevents a VM from resuming. Automating that would definitely resolve that issue for me. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 19 Mar 2020 21:15:49 +0000, Jim Henderson wrote:
On Thu, 19 Mar 2020 15:29:19 -0500, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Personally, I really like the idea. I usually forget to look on my mostly-headless system that I run VB on, and after an upgrade, I sometimes am caught out by the fact that the extensions also needed to be upgraded, and that sometimes prevents a VM from resuming.
Automating that would definitely resolve that issue for me.
I had completely forgotten about Oracle's PUEL licensing terms - free for personal use, must be purchased for business use. On that basis, I'd be more inclined to say don't automatically run it, but maybe either (a) package it separately so installing it is an option, or (b) include the script in the package but don't run it automatically. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 20. März 2020, 20:41:09 CET schrieb Jim Henderson:
On Thu, 19 Mar 2020 21:15:49 +0000, Jim Henderson wrote:
On Thu, 19 Mar 2020 15:29:19 -0500, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Personally, I really like the idea. I usually forget to look on my mostly-headless system that I run VB on, and after an upgrade, I sometimes am caught out by the fact that the extensions also needed to be upgraded, and that sometimes prevents a VM from resuming.
Automating that would definitely resolve that issue for me.
I had completely forgotten about Oracle's PUEL licensing terms - free for personal use, must be purchased for business use.
On that basis, I'd be more inclined to say don't automatically run it, but maybe either (a) package it separately so installing it is an option, or (b) include the script in the package but don't run it automatically.
Jim, if I understand Larry correctly, he would package a script, that does the usual manual operations in the background. Given, the script runs automatically only after a manual installation with license agreement accepted and a check, that an *older* extpack exists already (in case, the user changes his mind and uninstalls it), we should be save legally wise and profit from more comfortable updates. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 20 Mar 2020 21:39:35 +0100, Hans-Peter Jansen wrote:
Jim, if I understand Larry correctly, he would package a script, that does the usual manual operations in the background.
Given, the script runs automatically only after a manual installation with license agreement accepted and a check, that an *older* extpack exists already (in case, the user changes his mind and uninstalls it), we should be save legally wise and profit from more comfortable updates.
If that's the case - that it checks for the existence of a previously- installed extpack package, then I could see that working. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Samstag, 21. März 2020 00:18:20 CET Jim Henderson wrote:
On Fri, 20 Mar 2020 21:39:35 +0100, Hans-Peter Jansen wrote:
Jim, if I understand Larry correctly, he would package a script, that does the usual manual operations in the background.
Given, the script runs automatically only after a manual installation with license agreement accepted and a check, that an *older* extpack exists already (in case, the user changes his mind and uninstalls it), we should be save legally wise and profit from more comfortable updates.
If that's the case - that it checks for the existence of a previously- installed extpack package, then I could see that working.
This would be dangerous without at least checking the License has not changed, and even then I would be very cautious ... Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Am Samstag, 21. März 2020, 02:42:09 CET schrieb Stefan Brüns:
On Samstag, 21. März 2020 00:18:20 CET Jim Henderson wrote:
On Fri, 20 Mar 2020 21:39:35 +0100, Hans-Peter Jansen wrote:
Jim, if I understand Larry correctly, he would package a script, that does the usual manual operations in the background.
Given, the script runs automatically only after a manual installation with license agreement accepted and a check, that an *older* extpack exists already (in case, the user changes his mind and uninstalls it), we should be save legally wise and profit from more comfortable updates.
If that's the case - that it checks for the existence of a previously- installed extpack package, then I could see that working.
This would be dangerous without at least checking the License has not changed, and even then I would be very cautious ...
Sure, Stefan, but with a previous installation, this script could make use of a natively provided mechanism, that should take care of the licensing changing event as well: License accepted. For batch installation add --accept-license=56bexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to the VBoxManage command line. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 3/21/20 5:22 AM, Hans-Peter Jansen wrote:
Sure, Stefan, but with a previous installation, this script could make use of a natively provided mechanism, that should take care of the licensing changing event as well:
License accepted. For batch installation add --accept-license=56bexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to the VBoxManage command line.
As far as I can tell, that accept-license option only works for commercial users with a valid license. At least I do not have any number like this. I agree that a minimum of 100 seats for such a license is absurd! Thanks to everyone that responded to this poll. You gave me some good ideas, and I am grateful that I did not trigger a flame war, which is entirely too easy on openSUSE's mailing lists! :) My current thinking is to avoid modifying the package installation process, and add some code to the wrapper used to launch the VB GUI. Users that start their VMs using the autostart method, or those using scripts executed on bootup of the host will continue to operate as usual. In the VB wrapper script, the new code will have a check to see if an extpack is installed. If not, we are done. If an existing pack is present, the license will be checked to see if it is the current version. If not, the new code again exits, as the user will need to OK the new license. This test will need to be changed in package generation when Oracle has a new release. Fortunately, the license does not change very often - the current version is from July 2017. When a given system has some extpack installed, and the license matches the current one, then the version is compared with the current release as reported by VBoxManange. If the two differ, then the new extpack will be downloaded, installed, and the downloaded file will be deleted. This method should avoid installing a new version on systems where no one has approved the license. That will cover both personal and commercial cases. Please let me know if the above scheme misses any important points. Thanks again for the thoughtful responses. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On 19 Mar 15:29, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
I'd provide a script but not run it automatically at all, due to the licensing incompatibilities. Regards, ismail -- Aus so krummem Holze, als woraus der Mensch gemacht ist, kann nichts ganz Gerades gezimmert werden. — Immanuel Kant SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
Am Donnerstag, 19. März 2020, 21:29:19 CET schrieb Larry Finger:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Thanks, Larry for taking care of that. On systems, that use the extension pack, it's always a nuisance to download and install it manually, especially on remote systems. Forgetting it results in unfunny operational errors. # from my cheat sheet: wget https://download.virtualbox.org/virtualbox/6.1.4/Oracle_VM_VirtualBox_Extens... VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-6.1.4.vbox-extpack How do you detect, that an extension pack was installed before? Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Mar 19, 2020 at 03:29:19PM -0500, Larry Finger wrote:
Hi,
A user just contributed a script that downloads and installs the extension pack for VirtualBox. I would like to get the sense of VB users regarding implementation of this script in the post-install routine for the openSUSE package.
Thanks for your hardwork in maintaining and extending VirtualBox. This would be unwelcome for me, unless it was "unambiguously easy to avoid". I've never missed the Extension pack and the last time I looked at the Oracle PUEL we'd need a minimum 100 seat order to use for two machines, with a feeling that it was mystery-box software and some other software licesing complications. I'd have to switch back to spare seats of VMware, which is our company standard but never seemed to work well for me on openSUSE (could well have been my errors), and another nudge to conform with Debian or Mint. Daniel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (17)
-
Axel Braun -
Ben Greiner -
Bernhard Voelker -
Carlos E. R. -
Daniel Morris -
H.Merijn Brand -
Hans-Peter Jansen -
İsmail Dönmez -
James Knott -
Jim Henderson -
Larry Finger -
Michal Kubecek -
Philippe Andersson -
Richard Brown -
Simon Lees -
Stefan Brüns -
Vojtěch Zeisek