This is mostly done to align the different device type and how the
initial raw disk image is processed. The "beaglebone" type differed
a lot from how it is done for "raspberrypi" and "qemu", the big
difference was that it did not extract the necessary images from
the raw disk image. move the them to the mender disk image where
addition processing was done. Instead it processed directly on
the raw disk image.
To be able to optmize the workflows and stages, they have to be
executed in a similar fashion on all the device types.
Now do_raw_disk_image_create_partitions will always extract the
the images from the raw disk image, instead of doing it in the
device specific do_make_sdimg_* functions which contained a lot
of duplication.
By aligning the workflow we have can also get rid of the
beagblebone specific stage-3, and it can use the "generic" one.
Changelog: Optimizations to speed up conversion, utilizing sparse
images.
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Only crucial information is presented to the user as
console output.
More verbose information is stored in the build.log.
Issues: MEN-2172
Changelog: None
Signed-off-by: Adam Podogrocki <a.podogrocki@gmail.com>
Succeeding conversion steps added. Some commands' output silenced.
Still too much output logged from e.g. autotools.
Logging more verbose info to log file still missing.
Issues: MEN-2172
Changelog: None
Signed-off-by: Adam Podogrocki <a.podogrocki@gmail.com>
mender-conversion-tool with add-on scripts allow user to:
- shrink an existing embedded Linux image (shorter time of building final .sdimg raw disk image)
- restructure partition table of an existing embedded Linux image to follow Mender layout
- install Mender client related files
- install Grub related files for platforms supporting it
- patch U-Boot for platforms where Grub integration is not feasible (e.g. Raspbian)
- create Mender artifact based on the created .sdimg file
Issues: MEN-1867 / MEN-2037 / MEN-2038 / MEN-2041
Signed-off-by: Adam Podogrocki <a.podogrocki@gmail.com>