From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] meta-isar/isar-image-base: make kernel optional
Date: Mon, 16 Apr 2018 09:09:06 +0200 [thread overview]
Message-ID: <7bc2ca00-bb6c-b6eb-3844-285b02cb81cf@siemens.com> (raw)
In-Reply-To: <ea6d73e5-b60e-61f6-ebd9-9f8fb1d089de@siemens.com>
On 2018-04-16 09:03, [ext] Claudius Heine wrote:
> Hi Baurzhan,
>
> On 2018-04-13 13:23, Baurzhan Ismagulov wrote:
>> On Fri, Apr 13, 2018 at 12:45:10PM +0200, Claudius Heine wrote:
>>>> If I want to generate an NFS rootfs w/o the kernel and an SD image
>>>> with one,
>>>> how would I proceed?
>>>
>>> With two multiconfigs? That would be how I would probably do it.
>>
>> One multiconfig (e.g, qemui386-stretch), product-image-base.bb,
>> product-nfs-base.bb.
>
> You are right. Two multiconfigs would not be the best idea. Also since
> that would double the required resources. I haven't done this before,
> since I only create nfs root file systems for my project.
Why would it double the used resources? If two multiconfigs use the same
machine and distro and only vary in the selected image, and that maybe
only in a small package set (image B is based on image A), that should
allow for massive sharing. Keep in mind that different multiconfig does
not mean at all different basis (machine, distro, base image).
Jan
next prev parent reply other threads:[~2018-04-16 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:36 [PATCH 0/1] Optional kernel claudius.heine.ext
2018-04-12 14:36 ` [PATCH 1/1] meta-isar/isar-image-base: make kernel optional claudius.heine.ext
2018-04-13 10:38 ` Baurzhan Ismagulov
2018-04-13 10:45 ` Claudius Heine
2018-04-13 11:23 ` Baurzhan Ismagulov
2018-04-16 7:03 ` Claudius Heine
2018-04-16 7:09 ` Jan Kiszka [this message]
2018-04-16 8:27 ` Claudius Heine
2018-05-03 15:58 ` Henning Schild
2018-05-03 16:18 ` Alexander Smirnov
2018-05-03 16:27 ` Henning Schild
2018-05-03 16:30 ` Alexander Smirnov
2018-05-03 18:50 ` Alexander Smirnov
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=7bc2ca00-bb6c-b6eb-3844-285b02cb81cf@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.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