From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <tom_rini@mentor.com>
Cc: poky@yoctoproject.org
Subject: Re: busybox & update-alternatives
Date: Fri, 11 Feb 2011 11:24:16 -0700 [thread overview]
Message-ID: <4D557ED0.4050705@mlbassoc.com> (raw)
In-Reply-To: <4D5574D7.3010005@mentor.com>
On 02/11/2011 10:41 AM, Tom Rini wrote:
> On 02/11/2011 09:53 AM, Gary Thomas wrote:
>> A build for my platform with today's master
>> 49a18f1748d2417958b8e19cdd58c0c79f4fc728
>> shows a new behaviour - many messages like this:
>> update-alternatives: Linking //usr/bin/wc to ../../bin/busybox
>>
>> Questions:
>> * Is this truly new or was it just quiet before?
>> * Can't this be done at image build time? On my little
>> embedded OMAP-L138, it takes nearly 2 minutes to run
>> through this. My root is a ramdisk, so this is a cost
>> I see on _every_ boot.
>> * If it can't be done at build time, can I disable it?
>
> It can be done at build time _except_ for when there's a conflict. I suspect what's going on is that a recent change has introduced a conflict (which is to say, busybox provides
> foo as an alternative and something else also provides it, but isn't registering it as an alternative). If you check the whole boot log (or log.do_rootfs) you can find where the
> conflict is and then do something like http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=902b98f32ffd35661e43382f47226f65528ff1b1 (it's a little more complicated if the
> recipe also does BBCLASSEXTEND, since you don't want to do the move for virtclass-foo).
Running the postinst script manually, I get this error:
+ update-rc.d -s syslog busybox-udhcpc defaults
usage: update-rc.d [-n] [-f] [-r <root>] <basename> remove
update-rc.d [-n] [-r <root>] [-s] <basename> defaults [NN | sNN kNN]
update-rc.d [-n] [-r <root>] [-s] <basename> start|stop NN runlvl [runlvl] [...] .
-n: not really
-f: force
-v: verbose
-r: alternate root path (default is /)
-s: invoke start methods if appropriate to current runlevel
Looks like update-rc.d is not being called properly. This
was introduced by
commit 427472e980cd6254a5e4ef37209b327e15af259b
Author: Mark Hatle <mark.hatle@windriver.com>
Date: Thu Feb 3 19:29:50 2011 -0600
Mark, any comments?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-02-11 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 16:53 busybox & update-alternatives Gary Thomas
2011-02-11 17:41 ` Tom Rini
2011-02-11 18:24 ` Gary Thomas [this message]
2011-02-11 18:30 ` Mark Hatle
2011-02-11 18:37 ` Mark Hatle
2011-02-11 18:51 ` Koen Kooi
2011-02-11 19:22 ` Gary Thomas
2011-02-11 19:46 ` Mark Hatle
2011-02-11 19:50 ` Gary Thomas
2011-02-12 6:05 ` Khem Raj
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=4D557ED0.4050705@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=tom_rini@mentor.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox