All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Problems with postinstall
Date: Fri, 06 Jun 2014 13:08:37 +0200	[thread overview]
Message-ID: <lms7fl$84c$1@ger.gmane.org> (raw)
In-Reply-To: <CANyK_8f8oO+7gVbcXXOLVAdxa5OpmHR2s6yj199LpWaQcjSheQ@mail.gmail.com>

Am 06.06.2014 12:54, schrieb Paul Barker:
> I usually leave things more than a day before sending a ping email,
> people can be busy but usually you'll get replies within a couple of
> days on this list.
>

Sorry, I guess these 18h were driving me crazy as I don't understand why
it is not working. I actually thought, it had already been working
earlier...

>>>
>>> # Overwrite some configuration data with specific files
>>> pkg_postinst_${PN} () {
>>>     install -o root -g root -m 0600 ${S}/ssh/sshd_config ${D}/etc/ssh/
>>>     install -m 0755 ${S}/etc/rc.local ${D}/etc/
>>>     install -m 0644 ${S}/etc/watchdog.conf ${D}/etc/
>>>     install -m 0400 ${S}/etc/shadow ${D}/etc/
>>>     install -m 0440 ${S}/etc/sudoers ${D}/etc/
>>>     install -d ${D}/etc/default
>>>     install -o root -g root -m 0644 ${S}/etc/default-ntpdate
>>> ${D}/etc/default/ntpdate
>>> }
>>>
> 
> The postinst is executed by the package manager when the package is
> installed. If that installation takes place during do_rootfs, ${D}
> will refer to the rootfs directory for the image being built and ${S}
> will probably refer to something else to do with the image recipe but
> I'm not entirely sure on the details. If the installation takes place
> on the device, or the postinst is delayed until the first boot, ${D}
> and ${S} will not be set.
> 
> Hope this helps,
> 

So, I guess there are now two possibilities:
a.) The postinstall is not done at all.
b.) The postinstall is done, but before the other packages are
installed, which overwrite the files again. Is this possible? If yes,
howto specify that this postinstall should really be done last of all?

Thanks a lot

Michael



  reply	other threads:[~2014-06-06 11:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 10:44 Problems with postinstall Neuer User
2014-06-06  6:16 ` Neuer User
2014-06-06  7:11   ` Søren Holm
2014-06-06 10:54   ` Paul Barker
2014-06-06 11:08     ` Neuer User [this message]
2014-06-06 11:19       ` Jacob Kroon
2014-06-06 11:24         ` Neuer User
2014-06-06 12:31       ` Burton, Ross
2014-06-06 12:37         ` Neuer User

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='lms7fl$84c$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --cc=yocto@yoctoproject.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.