Re: [RAUC] [External] Re: Only Application FS Update

["Kilimci, Caglar" <caglar.kilimci@accenture.com>]

Hi Enrico,

>> I guess, there is still misconfiguration or a bug. RAUC still installs to the "next" slot. Here:
>>
>> # rauc status
>> Compatible:  Phytec
>> booted from: system1
>> slot states:
>>   rootfs.0: class=rootfs, device=/dev/mmcblk0p2, type=ext4, bootname=system1
>>       state=booted, description=, parent=(none), mountpoint=(none)
>>   rootfs.1: class=rootfs, device=/dev/mmcblk0p2, type=ext4, bootname=system2
>>       state=inactive, description=, parent=(none), mountpoint=(none)
>>   appfs.0: class=appfs, device=/dev/mmcblk0p5, type=ext4, bootname=(null)
>>       state=inactive, description=, parent=rootfs.1, mountpoint=(none)
>>   appfs.1: class=appfs, device=/dev/mmcblk0p6, type=ext4, bootname=(null)
>>       state=active, description=, parent=rootfs.0, mountpoint=(none)
>
>This is before or after updating? The update group rootfs.0 and appfs.1 is active. If it is before, RAUC should write the next update into 'appfs.0' (and rootfs.1 if there was an image for).

This was before updating. So I got that. Thank you so much and have a nice day.

Best Regards,
Caglar

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com
_______________________________________________
RAUC mailing list