From: "Burton, Ross" <ross.burton@intel.com>
To: Norman Stetter <Norman.Stetter@garz-fricke.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building single package as image, respecting dependencies
Date: Thu, 23 May 2019 14:46:08 +0100 [thread overview]
Message-ID: <CAJTo0Lb7a63q_LezyqOovtBh9DdGj9ra16MHAehipsJcwCvK7g@mail.gmail.com> (raw)
In-Reply-To: <A24DC035FE5F8F4BAE7F63FB1B07D7BC53299E@SRV24.hamburg.garz-fricke.de>
[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]
On Thu, 23 May 2019 at 13:46, Norman Stetter <Norman.Stetter@garz-fricke.com>
wrote:
> That seems to be a misunderstanding. I want to keep the OS image as small
> as possible to reduce boot time. We only use python for some test
> scenarios, so it doesn’t have to be included in the OS image. I did some
> measurements and including python3 in the OS image increased the boot time
> by over 30%. So the idea is to have it separately, and only mount it, when
> needed.
>
What filesystem are you using? I wasn't aware of any modern file systems
where the number of files installed affected mount performance.
Could you just build two images and have a 'normal' image and a 'test
image'? This is basically what the tools-testapps image feature is for.
Ross
[-- Attachment #1.2: Type: text/html, Size: 1368 bytes --]
[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 14130 bytes --]
next prev parent reply other threads:[~2019-05-23 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 12:36 Building single package as image, respecting dependencies Norman Stetter
2019-05-23 12:15 ` Burton, Ross
2019-05-23 12:45 ` Norman Stetter
2019-05-23 13:46 ` Burton, Ross [this message]
2019-05-24 6:29 ` Norman Stetter
2019-05-24 9:44 ` Burton, Ross
2019-05-24 10:46 ` Norman Stetter
2019-05-24 14:28 ` Norman Stetter
2019-05-28 9:36 ` Paul Barker
2019-05-29 13:30 ` Norman Stetter
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=CAJTo0Lb7a63q_LezyqOovtBh9DdGj9ra16MHAehipsJcwCvK7g@mail.gmail.com \
--to=ross.burton@intel.com \
--cc=Norman.Stetter@garz-fricke.com \
--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.