<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 31/03/2014 23:06, Thomas Gouverneur
wrote:<br>
</div>
<blockquote cite="mid:d1da99759ce906eed92adf460680487b@espix.net"
type="cite">
<p>Ram,</p>
<p>Thanks for your answer.</p>
<p> </p>
<p>1. Yes</p>
<p>2. Yes, considering that you need to run an 'svcadm restart
virtualbox-run-once' service that gets installed with the first
installation. Then, when an upgrade is done, this service is
responsible to upgrade drivers and/or services at its next
start. (so either manually, or, indeed after a reboot).</p>
<p>Does that make sense?</p>
<p> </p>
</blockquote>
<br>
So it requires manual running of a service to make the upgrade work?
Is it possible to automate this somehow as part of the IPS upgrade
procedure itself?<br>
<br>
Regards,<br>
Ram.<br>
<br>
<blockquote cite="mid:d1da99759ce906eed92adf460680487b@espix.net"
type="cite">
<p>--Thomas</p>
<p> </p>
<p>Le 2014-03-31 13:49, Ramshankar a écrit :</p>
<blockquote type="cite" style="padding-left:5px;
border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="moz-cite-prefix">Hi,<br>
<br>
Thanks for the work and the heads up, but before I look into
this, a couple of questions:<br>
<br>
1. Does the installation work without requiring reboots
(drivers are loaded and active after installation)? <br>
<br>
2. Does upgrading VirtualBox versions work without requiring
reboots (old drivers are unloaded, removed and new ones are
installed and loaded) ?<br>
<br>
Regards,<br>
Ram.<br>
<br>
On 03/30/2014 03:42 PM, Thomas Gouverneur wrote:</div>
<blockquote type="cite" style="padding-left:5px;
border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<p>Hi!</p>
<p>I'm writing today because I've been asked some time ago to
write a converter from SVR to IPS packages for VirtualBox to
allow the installation of VirtualBox and of the extension
pack through IPS. I wonder now if this work can be useful
upstream too?!</p>
<div>
<pre>I published the scripts there: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/tgouverneur/VBox-SVR2IPS">https://github.com/tgouverneur/VBox-SVR2IPS</a>
And an example repository can be found there: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://mdma.igh.cnrs.fr/vbox/en/catalog.shtml?show_all_versions=1&action=Refresh">http://mdma.igh.cnrs.fr/vbox/en/catalog.shtml?show_all_versions=1&action=Refresh</a>
The repository has been built with the VirtualBox.org's packages converted using the scripts present inside the GitHub repository listed below.
NOTE: This repo has only been tested with Solaris 11.1.
Any idea with who I could start the discussion to see what would those package be missing to allow a possible upstream adoption, so we can all have IPS upstream packages of VirtualBox in the future?
Thanks,
--Thomas</pre>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
vbox-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
</blockquote>
<p> </p>
<div>
<pre>--
--Thomas</pre>
</div>
</blockquote>
<br>
</body>
</html>