From: Roman I Khimov <khimov@altell.ru>
To: openembedded-devel@lists.openembedded.org
Subject: Re: postinst scripts and opkg configure
Date: Fri, 9 Apr 2010 15:26:53 +0400 [thread overview]
Message-ID: <201004091526.53400.khimov@altell.ru> (raw)
In-Reply-To: <k2j48239d391004090353mcc7c01a0o4bc58d8c1efd5c27@mail.gmail.com>
В сообщении от Пятница 09 апреля 2010 14:53:22 автор Sergey Lapin написал:
> On Fri, Apr 9, 2010 at 2:39 PM, Roman I Khimov <khimov@altell.ru> wrote:
> > В сообщении от Пятница 09 апреля 2010 14:26:22 автор Sergey Lapin написал:
> >> So, with recent images I have to run all postinst scripts again on
> >> device for services
> >> like udev or dropbear to work. These packages get 'installed' status,
> >> so postinst
> >> scripts won't normally run during 'opkg configure', but /etc/rc*d
> >> links are not created for them during
> >> image build. Any ideas on fixing, or what is really being wrong here?
> >
> > Do "set -e" in the beginning of postinst if it can only do its job on
> > target. I have some patches adding that in queue.
>
> I can't understand why creation of links won't work on host,
> because that will be a problem for filesystems like squashfs.
Actually, update-rc.d scripts should work on build host (that "$OPT" in script
is exactly for that purpose) and so are update-alternatives (thanks to
OPKG_OFFLINE_ROOT magic), so there might be something wrong with your setup.
What I was talking about is something more like postfix.
next prev parent reply other threads:[~2010-04-09 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 10:26 postinst scripts and opkg configure Sergey Lapin
2010-04-09 10:39 ` Roman I Khimov
2010-04-09 10:53 ` Sergey Lapin
2010-04-09 11:26 ` Roman I Khimov [this message]
2010-04-09 13:58 ` Sergey Lapin
2010-04-09 14:26 ` Mike Westerhof
2010-04-09 14:52 ` [PATCH] update-rc.d.bbclass: add dependency on update-rc.d-native Roman I Khimov
2010-04-09 11:19 ` [PATCH] rootfs_ipk.bbclass: run preinst/postinst scripts with "-e" Roman I Khimov
2010-04-09 15:48 ` Chris Larson
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=201004091526.53400.khimov@altell.ru \
--to=khimov@altell.ru \
--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.