[andreas.reichel.ext@siemens.com: Re: Fwd: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods]

[andreas.reichel.ext@siemens.com: Re: Fwd: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods]

[Andreas Reichel]

> 
> Am Tue, 26 Feb 2019 12:56:20 +0100
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> 
> > On 26.02.19 12:35, cedric_hombourger@mentor.com 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?
> 

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.

> 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.
> 
Once upon a time, where wic kept the .p1, .p2 etc files... but wic was
patched to remove them. I had suggested an upstream patch two years ago
which was not accepted by the maintainers. They said if we really need
the partition files, we should work our own way around it.
This said, it is no bad idea to reextract the partition files again out
of the wic image. This is also because we extract what really would be
flashed and wic already adapted sizes, etc...

So I would go Henning's way to extract the partition images...

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.schild@siemens.com>
> To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
> CC: cedric_hombourger@mentor.com, isar-users <isar-users@googlegroups.com>,
>  Andreas Reichel <Andreas.Reichel@tngtech.com>
> 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.kiszka@siemens.com>:
> 
> > On 26.02.19 12:35, cedric_hombourger@mentor.com 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.kiszka@siemens.com>
> To: cedric_hombourger@mentor.com, isar-users <isar-users@googlegroups.com>,
>  Andreas Reichel <Andreas.Reichel@tngtech.com>
> 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_hombourger@mentor.com 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.Reichel@tngtech.com, +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.Reichel@tngtech.com, +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

Re: [andreas.r...@siemens.com: Re: Fwd: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods]

[cedric_hombourger]

[-- 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 --]

Re: [andreas.r...@siemens.com: Re: Fwd: [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods]

[Henning Schild]

Am Tue, 26 Feb 2019 05:39:17 -0800
schrieb <cedric_hombourger@mentor.com>:

> 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...

Yes, agreed. I just thought is can be deprecated with wic, just looking
at our internal layers and Isar itself. If that is not the case, let us
keep it.

Henning

> 
> > 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 
> >
> >  
>