From: Carsten Haitzler (The Rasterman) <raster@rasterman.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org,
Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: [oe-commits] Koen Kooi : initscripts: only run ldconfig on boot when ld.so. conf is present
Date: Sat, 1 Nov 2008 08:53:34 +1100 [thread overview]
Message-ID: <20081101085334.8afcd730.raster@rasterman.com> (raw)
In-Reply-To: <gef9q7$o65$1@ger.gmane.org>
On Fri, 31 Oct 2008 16:55:50 +0100 Koen Kooi <k.kooi@student.utwente.nl>
babbled:
> On 31-10-2008 13:37, Carsten Haitzler (The Rasterman) wrote:
> > On Fri, 31 Oct 2008 12:00:45 +0100 (CET) git@amethyst.openembedded.net (GIT
> > User account) babbled:
> >
> > is there any reason to run ldconfig on boot? this should be handled by opkg
> > on package install/upgrade or by the flash image creation (this slows boot
> > significantly and i've patched out/disabled ldconfig run in bootmisc.sh
> > with no ill effects).
>
> Not all images have a package management tool inside, so depending on
> that is a no-go. Recently OE stopped shipping ld.so.conf so the ldconfig
> on boot won't get run. Doing it this way seemed to me the safest way to
> get a nice speedup and keep things working for the funky people needing
> ld.so.conf without a package manager :)
no package manager? gads. well - i'd lean to the "then you're on your own
buddy" line there - u install libs, you remember to run ldconfig, or suffer :)
maybe i'm just too harsh :) though your way is clean. why don't we make it
if [ ! -e /etc/ld.handled ]; then
/sbin/ldconfig
fi
and opkg adds a /etc/ld.handled to its package?
similar effect to what you did butbasically if someone knows they will handle
ldconfig then they just need to throw in that file into their system one way or
another?
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@rasterman.com
next prev parent reply other threads:[~2008-10-31 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081031110045.7EF89189333@amethyst.openembedded.net>
2008-10-31 12:37 ` [oe-commits] Koen Kooi : initscripts: only run ldconfig on boot when ld.so. conf is present Carsten Haitzler
2008-10-31 15:55 ` Koen Kooi
2008-10-31 21:53 ` Carsten Haitzler [this message]
2008-11-01 8:22 ` Koen Kooi
2008-11-01 11:38 ` Stanislav Brabec
2008-11-01 19:20 ` Phil Blundell
2008-11-02 7:45 ` Koen Kooi
2008-11-01 23:08 ` Carsten Haitzler
2008-11-02 4:51 ` Denys Dmytriyenko
2008-11-02 6:37 ` Carsten Haitzler
2008-11-02 10:52 ` Stanislav Brabec
2008-11-02 11:25 ` Running one-off target binaries, was: " Koen Kooi
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=20081101085334.8afcd730.raster@rasterman.com \
--to=raster@rasterman.com \
--cc=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.