Skip to contentSkip to conversation

postinst problem: module vs. update-rc.d

DISCUSSION Steffen Sledz 3 participants 3 messages Oct 14, 2011

lore
Share & tools
lore
#0 lore raw

We have a problem with a package that needs to install a kernel module and an initscript.

The recipe contains

inherit module update-rc.d

The generated postinst script is

#!/bin/sh
if [ -n "$D" ]; then
exit 1
else

        depmod -a 2.6.24.7
        update-modules || true
  fi
  if test "x$D" != "x"; then
        OPT="-r $D"
  else
        OPT="-s"

fi
update-rc.d $OPT somescript start 90 S . stop 10 0 1 6 .

The 'exit 1' leads to an error if $D contains a nonzero length string (what is the case in the OE image creation step at the build host) and suppresses the execution of the second (update-rc.d) part.

Because of this error the postinst is run a second time when the target device boots the first time ("opkg-cl configure" from /etc/rcS.d/S40configure).

The problem is that the update-rc.d execution (and therefor the creation of the new symlink into rcS.d) is done from within rcS itself. So the rcS.d/S90somescript will *not* be executed at this boot. :(

We see two possible solutions.

A) Don't use "inherit module update-rc.d" but write the pkg_postint ourselfs.

B) Create two packages (one for the module, one for the initscript) with a runtime dependency.

I don't like both of them. Any other ideas? Is it possible to force the order of postinst fragments (update-rc.d code before module code)?

Regards,
Steffen

Signature · 7 lines
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
#1 lore raw
Quoted 6 lines · Steffen Sledz

The 'exit 1' leads to an error if $D contains a nonzero length string (what is the case in the OE image creation step at the build host) and suppresses the execution of the second (update-rc.d) part.

Because of this error the postinst is run a second time when the target device boots the first time ("opkg-cl configure" from /etc/rcS.d/S40configure).

The problem is that the update-rc.d execution (and therefor the creation of the new symlink into rcS.d) is done from within rcS itself. So the rcS.d/S90somescript will *not* be executed at this boot. :(

Quoted 7 lines

We see two possible solutions.

A) Don't use "inherit module update-rc.d" but write the pkg_postint ourselfs.

B) Create two packages (one for the module, one for the initscript) with a runtime dependency.

I don't like both of them. Any other ideas? Is it possible to force the order of postinst fragments (update-rc.d code before module code)?

I think either update-rc.d or update-rc.d.bbclass should probably invoke the script as "start" when it installs it for the first time.

p.

#2 lore raw
In reply to Steffen Sledz
Quoted 30 lines · Steffen Sledz

We have a problem with a package that needs to install a kernel module and an initscript.

The recipe contains

inherit module update-rc.d

The generated postinst script is

#!/bin/sh
if [ -n "$D" ]; then
exit 1
else

        depmod -a 2.6.24.7
        update-modules || true
  fi
  if test "x$D" != "x"; then
        OPT="-r $D"
  else
        OPT="-s"

fi
update-rc.d $OPT somescript start 90 S . stop 10 0 1 6 .

The 'exit 1' leads to an error if $D contains a nonzero length string (what is the case in the OE image creation step at the build host) and suppresses the execution of the second (update-rc.d) part.

Because of this error the postinst is run a second time when the target device boots the first time ("opkg-cl configure" from /etc/rcS.d/S40configure).

The problem is that the update-rc.d execution (and therefor the creation of the new symlink into rcS.d) is done from within rcS itself. So the rcS.d/S90somescript will *not* be executed at this boot. :(

We see two possible solutions.

Quoted 8 lines

A) Don't use "inherit module update-rc.d" but write the pkg_postint ourselfs.

B) Create two packages (one for the module, one for the initscript) with a runtime dependency.

I don't like both of them. Any other ideas? Is it possible to force the order of postinst fragments (update-rc.d code before module code)?

Regards,
Steffen

BTW: there is another problem with update-modules:

SHR root@gjama ~ $ opkg files syslog-ng | grep modules.conf /etc/modules.conf
SHR root@gjama ~ $ update-modules
Error: the current /etc/modules.conf is not automatically generated. Use "update-modules force" to force (re)generation.

so if someone is using syslog-ng, than kernel-module-* or any "inherit module" package won't update ie autoloads properly..

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]