From: Gary Thomas <gary@mlbassoc.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Can anything be done about do_rootfs speed?
Date: Wed, 02 Oct 2013 13:20:46 -0600 [thread overview]
Message-ID: <524C720E.1090009@mlbassoc.com> (raw)
In-Reply-To: <CALmOhgnU1vHzM263H=CtXxayw4GaTGdTxdB5gG9=CQpe8+DMXg@mail.gmail.com>
On 2013-10-02 10:37, Trevor Woerner wrote:
> On 28 August 2013 06:55, Gary Thomas <gary@mlbassoc.com> wrote:
>> Hopefully
>> someone will document all of this in great detail some day. (in fact I filed
>> a
>> bug to this end many years ago...)
>
> It would appear that
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1088 can now be
> closed as a result of commit 581778c52493b662f449bbbed36453f161501c18
> in git://git.yoctoproject.org/yocto-docs.
Technically, yes, but the section on IPK based systems is incredibly
thin. I would be hard pressed to figure this out if I didn't know how
to do it already. I can't really comment on the RPM section as I don't
use that method.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-10-02 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 22:27 Can anything be done about do_rootfs speed? Paul D. DeRocco
2013-08-27 23:25 ` Gary Thomas
2013-08-28 0:10 ` Paul D. DeRocco
2013-08-28 7:20 ` Martin Jansa
2013-08-28 8:36 ` Paul D. DeRocco
2013-08-28 8:49 ` Samuel Stirtzel
2013-08-28 11:30 ` Samuel Stirtzel
2013-09-04 23:50 ` Paul D. DeRocco
2013-09-05 6:56 ` Nicolas Dechesne
2013-08-28 10:55 ` Gary Thomas
2013-08-28 11:29 ` Paul Barker
2013-09-02 12:26 ` Burton, Ross
2013-10-02 16:37 ` Trevor Woerner
2013-10-02 19:20 ` Gary Thomas [this message]
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=524C720E.1090009@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=trevor.woerner@linaro.org \
--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.