From: "Jürgen Borleis" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bth@kamstrup.com>
Subject: Re: [ptxdist] [PATCH] prelink: first boot warning
Date: Thu, 18 Jun 2015 15:08:32 +0200 [thread overview]
Message-ID: <201506181508.32817.jbe@pengutronix.de> (raw)
In-Reply-To: <1434631899-27229-1-git-send-email-bth@kamstrup.com>
Hi Bruno,
On Thursday 18 June 2015 14:51:39 Bruno Thomsen wrote:
> Running prelink with rc.once.d causes a first boot stall
> of about 2 minutes on Freescale i.MX28 454MHz ARM9 processor.
> This can be expensive if first device boot is during product
> manufacturing (assembly, programming, configuration, test).
>
> Signed-off-by: Bruno Thomsen <bth@kamstrup.com>
> ---
> rules/prelink.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/rules/prelink.in b/rules/prelink.in
> index 5d04fb0..1e06200 100644
> --- a/rules/prelink.in
> +++ b/rules/prelink.in
> @@ -21,6 +21,7 @@ config PRELINK_RC_ONCE
> help
> install a script that will be run on the first boot to
> prelink all programs and libraries.
> + warning! this can increase first boot with a few minutes!
With Using a recent linker the prelink becomes redundant. It is already done
when the linker hash-style it set to "gnu" (which is the default in a recent
PTXdist).
Or did you still see improvements with or without the pre-link step and that's
why you are still using this feature?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-06-18 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:51 Bruno Thomsen
2015-06-18 13:08 ` Jürgen Borleis [this message]
2015-06-19 10:41 ` Bruno Thomsen
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=201506181508.32817.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=bth@kamstrup.com \
--cc=ptxdist@pengutronix.de \
/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