Kay,<br><br>I am not sure if i made my self clear, what i am doing is and custom distro for an custom embedded device, which i want to have the ability to upgrade the system in runtime, which i need to ability to to stop my custom driver modules for the upgrade. So this is why i was asking what is the best way of starting and stop modules.<br>
<br>Unless what your saying is replace the file and just reboot, instead of stop the service and replace then start it again.<br><br>Pawel<br><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 10:08 AM, Kay Sievers <span dir="ltr"><<a href="mailto:kay@vrfy.org">kay@vrfy.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Mar 19, 2012 at 15:02, Pawel Pastuszak <<a href="mailto:pawelpastuszak@gmail.com">pawelpastuszak@gmail.com</a>> wrote:<br>
> So in this case how would you support upgrading the kernel module?<br>
> The main reason to do the module unload is so you can upgrade the module to<br>
> an new version.<br>
<br>
</div>Just do that _in_ the running service; systemd can not help with<br>
native tools to support that.<br>
<font color="#888888"><br>
Kay<br>
</font></blockquote></div><br>