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

Hi Michael, You are triggering slightly undefined behaviour by using both > "initrd=initrd.magic" and an explicit "initrd=" argument. > > The "initrd=initrd.magic" will cause the kernel to already see an initrd > that comprises the concatenation of all of the images as seen by > "imgstat". (The

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

Hi Thomas, I've added marker files to the images and as far as I can tell nothing is missing from the end result, it's just not clear which unpacked image will win when the same file exists in multiple images using the ipxe script I have been using. griznog On Mon, Mar 14, 2022 at 1:34 AM

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

On 11/03/2022 16:44, John Hanks wrote: 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

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

Adding a /one to image one, a /two to image two etc would make it easier to see whether all files are there Am 11.03.22 um 21:13 schrieb John Hanks: On Fri, Mar 11, 2022 at 1:55 PM John Hanks mailto:griz...@gmail.com>> wrote: If I get the OS container first, then get the ssh