This means that `grub-install` and `update-grub` no longer risk
bricking the device, but will produce boot scripts with Mender support
integrated. It also means that the standard GRUB menu will be
available.
It is supported on x86_64 platforms where `grub.d` is available, and
can be turned on and off with `MENDER_GRUB_D_INTEGRATION`. The default
is to use it if available.
Devices that did not previously use `grub.d` integration won't be
upgraded correctly with it turned on, so it is advised to set
`MENDER_GRUB_D_INTEGRATION=n` if you are upgrading existing devices.
Changelog: Commit
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
Changelog: grub-mender-grubenv: User space tools, "fw_printenv" and
"fw_setenv" have been renamed to "grub-mender-grubenv-print" and
"grub-mender-grubenv-set", respectively. This has been done in order
to avoid conflict with U-Boot's user space tools, which have the same
names.
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
From grub-mender-grubenv changelog:
Changelog: add 'rootwait' to bootargs
Changelog: grubenv: Handle debug command prompt when running as EFI app.
Changelog: utilize regexp to dynamically set mender_grub_storage_device
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
2.04 does not work on Beaglebone Black.
Ticket: https://tracker.mender.io/browse/MEN-2404
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
The goals of the re-write was to achieve the following:
1. It should be easy to extend the tool to support other boards or distributions
2. We should not compile code in the tool (rely on binaries built elsewhere)
compiling code increases complexity, due to requirement of toolchains etc.
3. The tool shall not be designed around specific hardware/platform types
- This is the case today with the usage of --device-type flag
4 The tool should be to convert images without knowing anything about the hardware/platform
relates to above 3.
5. Configuration interface should be simplified
- command line flags -> configuration files
6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code
7. It shall be easy to extend functionality
- support for rootfs overlay to inject user applications/configurations
- ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts)
8. Code structure should be modular
- Eases Maintenance and possibility of making isolated changes
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Kristian Amlie
Drew Moseley
Lluis Campos
Mirza Krak