When exactly is pkg_postinst_ontarget_${PN} executed on the target? I would like to make sure that the time is correct (ntp service running and the time is right;)) and then it's executed. Is the mechanism explained somewhere? The only thing I find is this: cat /var/log/postinstall.log Created gpg homedir Importing keys from 'ipkkeypub.gpg'... Importing keys from 'key-ipkkey.gpg'... OK gpg (GnuPG) 2.2.20-unknown; Copyright (C) 2020 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Configuring sysvinit-inittab. Configuring opkg-keyrings. root@multi-v7-ml:/var/log# ----- with system-v init I see: /etc/init.d/run-postinsts ----- and this: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/run-postinsts/run-postinsts_1.0.bb ----- start 99 S . which looks like it some time at the end of the init scripts. ----- This would mean that S99 after S20. S20ntpd Hmmm
There is no existing bug that we could find but ontarget is mentioned a few times (3?) in: https://docs.yoctoproject.org/singleindex.html Robert, Could you and Alex agree on the text and submit a doc patch?
I guess it should be enough to say that running postinsts on first boot is provided by the run-postinsts service (available both via systemd and sysvinut), and refer anyone wanting details to http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/run-postinsts I don't know if anyone ensured it happens at truly the 'right' moment during boot, it is what it is. Patches welcome.
Robert, I assume that you won't have time to work on this so I've moved it to unassigned.
Closing as this is not a bug; if documentation needs adjustment, please submit the needed patches directly.