Question - example on building a self-installing image

Question - example on building a self-installing image

[John W]

[-- Attachment #1.1: Type: text/plain, Size: 345 bytes --]

Hi Isar team,

Is there any example on building a self-installing image to a x86 machine? 
I've found the following post online:
https://www.thegoodpenguin.co.uk/blog/self-installing-yocto-image-from-a-usb-drive/
However it does not seem trivial to use the same approach in isar so 
wondering if there's any existing example for this. 

Thanks!

[-- Attachment #1.2: Type: text/html, Size: 437 bytes --]

Re: Question - example on building a self-installing image

[Jan Kiszka]

On 03.01.24 18:17, John W wrote:
> Hi Isar team,
> 
> Is there any example on building a self-installing image to a x86
> machine? I've found the following post online:
> https://www.thegoodpenguin.co.uk/blog/self-installing-yocto-image-from-a-usb-drive/
> However it does not seem trivial to use the same approach in isar so
> wondering if there's any existing example for this.
> 

Nothing public yet, but Quirin has created something like that
internally. Not sure about plans to publish or upstream that, though.

And then we have another approach in [1] which generally works as well -
but not in all cases. Its idea is to replicate and individualize the
content of an external media on first boot.

Jan

[1]
https://github.com/siemens/meta-iot2050/tree/master/recipes-core/install-on-emmc

-- 
Siemens AG, Technology
Linux Expert Center

Re: Question - example on building a self-installing image

[Gylstorff Quirin]

On 1/3/24 19:59, Jan Kiszka wrote:
> On 03.01.24 18:17, John W wrote:
>> Hi Isar team,
>>
>> Is there any example on building a self-installing image to a x86
>> machine? I've found the following post online:
>> https://www.thegoodpenguin.co.uk/blog/self-installing-yocto-image-from-a-usb-drive/
>> However it does not seem trivial to use the same approach in isar so
>> wondering if there's any existing example for this.
>>
> 
> Nothing public yet, but Quirin has created something like that
> internally. Not sure about plans to publish or upstream that, though.

I created an separate installer image which uses bmap/dd to install the 
given wic image to a harddisk on the device.


Quirin

> 
> And then we have another approach in [1] which generally works as well -
> but not in all cases. Its idea is to replicate and individualize the
> content of an external media on first boot.
> 
> Jan
> 
> [1]
> https://github.com/siemens/meta-iot2050/tree/master/recipes-core/install-on-emmc
> 

Re: Question - example on building a self-installing image

[Roberto A. Foglietta]

[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]

On Thu, 4 Jan 2024 at 09:36, 'Gylstorff Quirin' via isar-users <
isar-users@googlegroups.com> wrote:

>
> I created an separate installer image which uses bmap/dd to install the
> given wic image to a harddisk on the device.
>

I suppose that the most valuable part of that ISAR part would be:

- create the image for one of all the supported architecture and systems
- create a bootable image for the related architecture and system

In such a way that this provide the ISAR user the ability to make a
bootable installation USB-key with the related customizable menu to install
and storage device.

It is the "separate" adjective that makes me ask about it. Because,
otherwise every USB bootable key template that provide

- boot loader
- root filesystem with some tools and a terminal - mainly, busybox
- an autoresize data partition to fullfil all the extra space in the USB
key whatever the size would be.

This can provide a separate installer image (or a template for it) because
the data partition will contain the image to install on the target system.

Limited to the supported platform and architectures {x86, ia64, arm6,
amr7}, it can be easily achieved with tinycore.

Therefore, my curiosity is about the "separate" meaning. It is separate by
ISAR project because it has not been or it is not planed to be integrated
with it or it is separated because it is something completely different
from the ISAR building e.g. the USB bootable installer is not created from
the same source or binaries that are included into the image created by
ISAR?

 Best regards, R-

[-- Attachment #2: Type: text/html, Size: 2198 bytes --]