From: Christophe Aeschlimann <c.aeschlimann@acn-group.ch>
To: openembedded-devel@lists.openembedded.org
Subject: do_rootfs : (offline root mode: not running openntpd.postinst)
Date: Wed, 29 Apr 2009 14:22:34 +0200 [thread overview]
Message-ID: <49F8468A.7060305@acn-group.ch> (raw)
Hi,
I'm facing a problem with the openntpd recipe (version 3.9p1). When I select
this recipe to be build in my image it builds correctly and is present on my
jffs2 image file which is great. But then it won't run on the target because
openntpd requires a special user to be created and it is not. (as stated in the
recipe by the build configuration this user should be named "ntpd").
By checking the recipe I saw that pkg_postinst is defined and should create the
user in the passwd file after the package has been installed. So far so good.
But then I realized that this function was never called when the do_rootfs is
done for my image file.
It seems that when the packages are installed in the rootfs directory
(do_rootfs) all the pkg_postinst functions of the recipes are skipped with the
following message :
(offline root mode: not running base-passwd.postinst)
(offline root mode: not running busybox.postinst)
(offline root mode: not running dropbear.postinst)
[stripped]
(offline root mode: not running openntpd.postinst)
etc...
I guess that this a feature and not a bug but I'd like to understand why these
functions are not called ?
Of course I can modify the recipe so it will change my passwd file during
install or add some initialization script to check that this user is created
before ntpd runs but I'm more curious about why we skip all the postinst scripts.
Thanks for any comments,
Christophe
next reply other threads:[~2009-04-29 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 12:22 Christophe Aeschlimann [this message]
2009-04-29 12:57 ` do_rootfs : (offline root mode: not running openntpd.postinst) Phil Blundell
2009-04-29 13:35 ` Christophe Aeschlimann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F8468A.7060305@acn-group.ch \
--to=c.aeschlimann@acn-group.ch \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.