Hi, Christian and I discussed if we should simplify the state extraction after a failed update, i.e. when we booted the previous version again. bg_printenv will then report something like this:
---------------------------- Config Partition #0 Values: in_progress: no revision: 2 kernel: C:BOOT0:linux.efi kernelargs: watchdog timeout: 0 seconds ustate: 0 (OK) user variables: ---------------------------- Config Partition #1 Values: in_progress: no revision: 0 kernel: C:BOOT1:linux.efi kernelargs: watchdog timeout: 0 seconds ustate: 3 (FAILED) user variables: But there is no simple command to find out that we are not OK but rather back from a failed update. There is bg_printenv -o ustate -r -c, but that will only report USTATE=0. We don't have a nice way to query the "FAILED" state of the other env, only "bg_printenv | grep FAILED". Any ideas how to address that best? Jan -- Siemens AG, Technology Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/bf924a72-df3f-6b27-5dc6-0ca951903778%40siemens.com.
