From: cedric_hombourger@mentor.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [andreas.r...@siemens.com: Re: Fwd: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods]
Date: Tue, 26 Feb 2019 05:39:17 -0800 (PST) [thread overview]
Message-ID: <0e1f08cc-2119-4677-9aff-16f5bf012950@googlegroups.com> (raw)
In-Reply-To: <20190226133148.GC17750@iiotirae>
[-- Attachment #1.1: Type: text/plain, Size: 3977 bytes --]
On Tuesday, February 26, 2019 at 2:33:28 PM UTC+1, Andreas Reichel wrote:
>
>
> We (at least me) have no scenario where we really build update artifacts
> with isar. One important question is, if the ext4 image is exactly the
> size of its contents or if it is the final partition size. If it is
> exactly the size of its contents only, it cannot be used as an update
> artifact because the resulting rootfs would have 0 bytes free and likely
> won't boot.
>
>
postinstall steps can be used to "resize2fs" the file-system after it was
installed
>
> So I would go Henning's way to extract the partition images...
>
>
It sure works. I however don't see much harm in keeping the ext4_img class
I would not expect much maintenance overhead there...
> Also we already have wic dependencies like sfdisk etc installed, where
> we can dump partition lists and use grep and dd.
>
> Andreas
>
> > Henning
> >
> > > Jan
> > >
> >
>
> > Date: Tue, 26 Feb 2019 13:12:18 +0100
> > From: Henning Schild <henning...@siemens.com <javascript:>>
> > To: "[ext] Jan Kiszka" <jan.k...@siemens.com <javascript:>>
> > CC: cedric_h...@mentor.com <javascript:>, isar-users <
> isar-...@googlegroups.com <javascript:>>,
> > Andreas Reichel <Andreas...@tngtech.com <javascript:>>
> > Subject: Re: [PATCH 1/1] meta/ext4-img: refactor to fit current image
> > creation methods
> > X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
> >
> > Am Tue, 26 Feb 2019 12:56:20 +0100
> > schrieb "[ext] Jan Kiszka" <jan.k...@siemens.com <javascript:>>:
> >
> > > On 26.02.19 12:35, cedric_h...@mentor.com <javascript:> wrote:
> > > > Hi Henning,
> > > >
> > > > One use-case on our side is the generation of SWUpdate image. Our
> > > > helper class uses do_ext4_image to generate the file-system image
> > > > we later embed into the .swu file
> > >
> > > Andreas, how do you address that scenario for upstream SWUpdate
> > > support?
> >
> > I guess a valid way would be to have a task after do_wic which will
> > extract all raw partitions if enabled. It is kind of stupid but if we
> > can not change wic we better build around and reuse instead of
> > reimplement.
> >
> > Henning
> >
> > > Jan
> > >
> >
>
> > Date: Tue, 26 Feb 2019 12:56:20 +0100
> > From: Jan Kiszka <jan.k...@siemens.com <javascript:>>
> > To: cedric_h...@mentor.com <javascript:>, isar-users <
> isar-...@googlegroups.com <javascript:>>,
> > Andreas Reichel <Andreas...@tngtech.com <javascript:>>
> > Subject: Re: [PATCH 1/1] meta/ext4-img: refactor to fit current image
> > creation methods
> > User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12)
> > Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
> >
> > On 26.02.19 12:35, cedric_h...@mentor.com <javascript:> wrote:
> > > Hi Henning,
> > >
> > > One use-case on our side is the generation of SWUpdate
> > > image. Our helper class uses do_ext4_image to generate the
> > > file-system image we later embed into the .swu file
> >
> > Andreas, how do you address that scenario for upstream SWUpdate support?
> >
> > Jan
> >
> > --
> > Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> > Corporate Competence Center Embedded Linux
>
>
> --
> Andreas Reichel
> Dipl.-Phys. (Univ.)
> Software Consultant
>
> Andreas...@tngtech.com <javascript:>, +49-174-3180074
> TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
> Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
> Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
>
>
> ----- End forwarded message -----
>
> --
> Andreas Reichel
> Dipl.-Phys. (Univ.)
> Software Consultant
>
> Andreas...@tngtech.com <javascript:>, +49-174-3180074
> TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
> Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
> Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
>
>
[-- Attachment #1.2: Type: text/html, Size: 8165 bytes --]
next prev parent reply other threads:[~2019-02-26 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 13:31 [andreas.reichel.ext@siemens.com: " Andreas Reichel
2019-02-26 13:39 ` cedric_hombourger [this message]
2019-02-26 14:50 ` [andreas.r...@siemens.com: " Henning Schild
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=0e1f08cc-2119-4677-9aff-16f5bf012950@googlegroups.com \
--to=cedric_hombourger@mentor.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