From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Draft design][RFC] Running postinst at rootfs generation time
Date: Tue, 05 Jul 2011 11:22:42 +0100 [thread overview]
Message-ID: <1309861363.19115.7.camel@phil-desktop> (raw)
In-Reply-To: <0C757E680E33864AB113392C7E83F910BE5196@GSX300A.mxchg.m.corp>
On Tue, 2011-07-05 at 12:06 +0200, Hauser, Wolfgang (external) wrote:
> Especially we have to cover some adduser/addgroup issues, modify the volatile file handling for our needs, and for omap3 graphics the handling of the GLES version.
> A failed offline postinst causing a runtime configuration. So the image generation log has to be checked for such failing scripts.
Nowadays you can set IMAGE_FEATURES = "read-only-rootfs", which will
result in a fatal error if any packages are still unconfigured after
rootfs construction is finished.
p.
next prev parent reply other threads:[~2011-07-05 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 2:09 [Draft design][RFC] Running postinst at rootfs generation time Cui, Dexuan
2011-06-28 4:11 ` Mark Hatle
2011-06-28 13:15 ` Richard Purdie
2011-06-28 14:44 ` Mark Hatle
2011-06-28 16:58 ` Hauser, Wolfgang (external)
2011-07-04 0:23 ` Cui, Dexuan
2011-07-05 8:42 ` Tom Parkin
2011-07-05 10:06 ` Hauser, Wolfgang (external)
2011-07-05 10:22 ` Phil Blundell [this message]
2011-07-05 10:30 ` Hauser, Wolfgang (external)
2011-07-05 10:36 ` Phil Blundell
2011-07-12 17:07 ` Mark Hatle
2011-07-13 7:58 ` Hauser, Wolfgang (external)
2011-07-13 10:04 ` Phil Blundell
2011-06-28 13:18 ` Richard Purdie
2011-06-28 20:31 ` Saul Wold
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=1309861363.19115.7.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@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.