reload kernel module from initscript during package update

I've got a package which contains a kernel module (packaged with
dkms). This kernel module is loaded by an init-script, which is also
part of the package. Now the problem is this: If an application is
running and using the device, the init script fails when it tries to
reload the updated module, which right now causes the package
installation to fail.

Now the question is: Are there any best practices to handle this sort of thing?

I thinking of implementing one of the following ideas:
I could ask the user with a debconf dialog if he wants to terminate
the application[s] holding the device node open, warning that an old
module version is used if the applications are not terminated.

I could also just leave the module loaded and give a hint, that the
modules initscript needs to be called with restart.

Christoph

Re: reload kernel module from initscript during package update

<div>
<div class="gmail_quote">On Fri, Jul 1, 2011 at 09:23, Christoph Mathys <span dir="ltr">&lt;<a href="mailto:eraserix@...">eraserix <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
I've got a package which contains a kernel module (packaged with<br>
dkms). This kernel module is loaded by an init-script, which is also<br>
part of the package. Now the problem is this: If an application is<br>
running and using the device, the init script fails when it tries to<br>
reload the updated module, which right now causes the package<br>
installation to fail.<br><br>
Now the question is: Are there any best practices to handle this sort of thing?<br><br>
I thinking of implementing one of the following ideas:<br>
I could ask the user with a debconf dialog if he wants to terminate<br>
the application[s] holding the device node open, warning that an old<br>
module version is used if the applications are not terminated.<br><br>
I could also just leave the module loaded and give a hint, that the<br>
modules initscript needs to be called with restart.<br><br>
Christoph<br><br>
--<br>
Ubuntu-motu mailing list<br><a href="mailto:Ubuntu-motu@...">Ubuntu-motu@...m</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu</a><br>
</blockquote>
</div>
<br>Why not set up the module to load on demand from a modalias instead?<br clear="all"><br>-- <br>Mario Limonciello<br><a href="mailto:superm1@..." target="_blank">superm1@...</a><br>
</div>

Re: reload kernel module from initscript during package update

On 01/07/2011 22:26, Mario Limonciello wrote:
> On Fri, Jul 1, 2011 at 09:23, Christoph Mathys <eraserix@...
> <mailto:eraserix@...>> wrote:
> 
>     I've got a package which contains a kernel module (packaged with
>     dkms). This kernel module is loaded by an init-script, which is also
>     part of the package. Now the problem is this: If an application is
>     running and using the device, the init script fails when it tries to
>     reload the updated module, which right now causes the package
>     installation to fail.
> 
>     Now the question is: Are there any best practices to handle this sort of thing?
> 
>     I thinking of implementing one of the following ideas:
>     I could ask the user with a debconf dialog if he wants to terminate
>     the application[s] holding the device node open, warning that an old
>     module version is used if the applications are not terminated.
> 
>     I could also just leave the module loaded and give a hint, that the
>     modules initscript needs to be called with restart.
> 
>     Christoph
> 
>     --
>     Ubuntu-motu mailing list
>     Ubuntu-motu@... <mailto:Ubuntu-motu@...>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
> 
> 
> Why not set up the module to load on demand from a modalias instead?

I think the issue is less to do with the initscript and more to do with
reloading the module -- after the upgrade, the postinst doesn't manage to reload
the module because something is holding onto the device node.

-- 
Kind regards,
Loong Jin

On 01/07/2011 22:26, Mario Limonciello wrote:
> On Fri, Jul 1, 2011 at 09:23, Christoph Mathys <eraserix@...
> <mailto:eraserix@...>> wrote:
> 
>     I've got a package which contains a kernel module (packaged with
>     dkms). This kernel module is loaded by an init-script, which is also
>     part of the package. Now the problem is this: If an application is
>     running and using the device, the init script fails when it tries to
>     reload the updated module, which right now causes the package
>     installation to fail.
> 
>     Now the question is: Are there any best practices to handle this sort of thing?
> 
>     I thinking of implementing one of the following ideas:
>     I could ask the user with a debconf dialog if he wants to terminate
>     the application[s] holding the device node open, warning that an old
>     module version is used if the applications are not terminated.
> 
>     I could also just leave the module loaded and give a hint, that the
>     modules initscript needs to be called with restart.
> 
>     Christoph
> 
>     --
>     Ubuntu-motu mailing list
>     Ubuntu-motu@... <mailto:Ubuntu-motu@...>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
> 
> 
> Why not set up the module to load on demand from a modalias instead?

I think the issue is less to do with the initscript and more to do with
reloading the module -- after the upgrade, the postinst doesn't manage to reload
the module because something is holding onto the device node.

--

-- 
Kind regards,
Loong Jin

package vegastrike

Hi,

the package vegastrike is not available for Versions > hardy. But the packages vegastrike-data and
vegastrike-music are available for lucid. There is no reason, why music and data packages are available
with lucid but the game isn't.

kaputtnik

Re: package vegastrike

On 07/03/2011 04:06 PM, kaputtnik wrote:
> Hi,
>
> the package vegastrike is not available for Versions > hardy. But the packages vegastrike-data and
vegastrike-music are available for lucid. There is no reason, why music and data packages are available
with lucid but the game isn't.
>
> kaputtnik
>
>
The reason would be that someone forgot to file a removal request.  They
are all separate source packages.

Micah

Adding and maintaining new package

<div>
<p>Hello,</p>
<div><br></div>
<div>I have a question on what is a right way to add and maintain (provide updates) new package to Canonical repo. I've succeeded to found the following document related to that -&nbsp;<a href="https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages">https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages</a>. However, it covers only 'add new package' phase and doesn't clarify how the package should be updated.</div>
<div><br></div>
<div>More details on what I would like to achieve - the main idea is to provide convenient way to deliver free open source Community Edition of IntelliJ IDEA java ide (<a href="http://www.jetbrains.org/pages/viewpage.action?pageId=983211">http://www.jetbrains.org/pages/viewpage.action?pageId=983211</a>) to (k)ubuntu users. I.e. the company (JetBrains) is ready to assemble the application to *.deb format on every new release and wants to push that updated packages to the repo. It seems that firing new ticket every time the package should be updated is a little too much, especially in case of the 'dev' branch. Ideally, we would like to be able to push new IDEA packages as soon as they are constructed.</div>
<div><br></div>
<div>Please let me know how we can proceed that.</div>
<div><br></div>
<div>P.S.&nbsp;I found that there is a notion of &nbsp;Canonical Partnership (<a href="http://www.canonical.com/about-canonical/partnerships">http://www.canonical.com/about-canonical/partnerships</a>) but it doesn't provide enough information to understand if that is what we need.</div>
<div>
<br>
</div>
<div>Denis<br clear="all"><br>-- <br><a href="http://denis-zhdanov.blogspot.com">http://denis-zhdanov.blogspot.com</a><br>
</div>
</div>

xmame on x86 platform doesn't work at all

<div>Hello,<br>Sorry to trouble you, but I need your help. <br>I found something really buggy about the xmame-sdl package. <br>My system was Ubuntu 10.10 (amd64), but now I use Ubuntu 10.10 (i386). <br>

The problem is, when I install package xmame-sdl, and run xmame command, it doesn't work at all.<br><br><span>error: compiled byte ordering doesn't match machine byte ordering.</span><br><span>compiled for MSB first, are you sure you chose the right cpu in makefile.unix?</span><br><br>While I was using amd64, the problem never occurred, and according to the error message, this problem is most likely platform independent, and it seems that something is wrong with the configuration (makefile) with the i386 platform.<br><br>I tried to file this bug(possibly) using the bug tracking system, but my report is not assigned (for a long time), so I feel a little upset.<br>Again I need to say sorry if I had disturbed you.<br>Thank you for your time.<br>
</div>

Leaving the project

Hello,

For years I thought Ubuntu was a great project and with the time I
discovered it's myself. In the 2009 about I started to contribute
helping in the italian IRC channel support (#ubuntu-it), then helping on
the italian forum and after some time I started to help the italian
Ubuntu translations team maintaining some translations templates. Then I
also started to modify and maintain some wiki pages in italian. After a
while, I started to contribute to Ubuntu development: my first upload
was in the April 2010 when I did my first sync in Ubuntu. A while later,
I uploaded my first package, autotrash (however, I uploaded it in Debian
after some time and I started to maintain it there). I started to work
on the various development tasks (syncs, merges, bug fixing, ...). In
the later July 2010 I got my MOTU membership. Since that moment, I
earned more experience day after day.

With my adventure, I meet a lot of wonderful people. I also meet a
couple of people who helped me; I'm not going to mention them, because
the list would be quite big. I learned a lot of things, thanks everyone.

Because of some stuff in the real life, and other things, I'm afraid I
won't be able to still contribute to Ubuntu. I'm writing this mail
reluctantly, I will however remain in the MOTU team and an Ubuntu member
with the hope to come back one day. But I will still be around when I
can and I won't totally go.

Good luck with the future of the project and thanks for everything.

Lorenzo De Liso

Re: Leaving the project

Ciao Lorenzo,

Am 14.07.2011 12:59, schrieb Lorenzo De Liso:
> Good luck with the future of the project and thanks for everything.

Thanks a lot for all you did for Ubuntu and all the best for you and
your future projects.

Have a great day,
 Daniel

--

-- 
Ubuntu Developer Week: 11th-15th July 2011
https://wiki.ubuntu.com/UbuntuDeveloperWeek

Re: Leaving the project

On Thu, Jul 14, 2011 at 4:29 PM, Lorenzo De Liso <blackz@...> wrote:
> Hello,

Hello mate

>
> Because of some stuff in the real life, and other things, I'm afraid I
> won't be able to still contribute to Ubuntu. I'm writing this mail
> reluctantly, I will however remain in the MOTU team and an Ubuntu member
> with the hope to come back one day. But I will still be around when I
> can and I won't totally go.

Thanks mate for your contribution. Wish you all the very best in the future.

>
> Good luck with the future of the project and thanks for everything.
>

Good luck and thanks a lot to you too!

Cheers and regards,

-- 
Bhavani Shankar
Ubuntu Developer       |  www.ubuntu.com
https://launchpad.net/~bhavi

--

-- 
Ubuntu-motu mailing list
Ubuntu-motu@...
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu