[ipxe-devel] Does imgextract keep writing to same named location by design?

[Christian Iwata Nilsson]

On Fri, 11 Mar 2022 at 17:42, John Hanks <griznog at gmail.com> wrote:

> Hi,
>
> I am using imgextract to download several images, like so
>
> imgextract --name one http://master/one.img
> imgextract --name two http://master/two.img
> imgextract --name three http://master/three.img
> boot kernel initrd=initrd.magic initrd=one initrd=two initrd=three blah
> blah blah
>
> So far so good, except that I wanted to try adding a lot of these but am
> restricted by the maximum kernel command line length. I naively tried
>
> imgextract --name mysystem http://master/one.img
> imgextract --name mysystem http://master/two.img
> imgextract --name mysystem http://master/three.img
> boot kernel initrd=initrd.magic initrd=mysystem blah blah blah
>
> and it worked!!! But, that seems way too easy, like I'm cheating. Is this
> expected to work this way or am I exploiting a bug that might get fixed
> later? I don't want to depend on this unless it's working this way on
> purpose.
>
> Thanks,
>
> griznog
>
>
Are you sure that the contents from them are all available?
Since you are using imgextract I assume that the contents of *.img is
compressed and that it contains CPIO archives?

Could you verify with imgstat that size adds up if you do them to separate
names and then try those 2 to the same file?
I see nothing that indicates this as being expected behaviour.

/Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20220311/2d51ab87/attachment.htm>