t; On Behalf Of Alberto Bursi
> >> Sent: Dienstag, 21. Juli 2020 09:48
> >> To: openwrt-devel@lists.openwrt.org; m...@adrianschmutzler.de
> >> Subject: Re: Restoring (old) config backups and
> >>
> >>
> >> On 20/07/20 19:32, Henrique de Moraes
>> On Aug 1, 2020, at 10:05 AM, Paul Oranje wrote:
>>
>>> Actually, my solution implements the config "on device" as a uci parameter,
>>> so the "on device" version is actually not the version of the firmware
>>> installed, but of the config installed. Therefore, one may indeed go that
>>> r
i 2020 09:48
>> To: openwrt-devel@lists.openwrt.org; m...@adrianschmutzler.de
>> Subject: Re: Restoring (old) config backups and
>>
>>
>> On 20/07/20 19:32, Henrique de Moraes Holschuh wrote:
>>>
>>>
>>> Any thoughts on this? I am certainly to have ove
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Alberto Bursi
> Sent: Dienstag, 21. Juli 2020 09:48
> To: openwrt-devel@lists.openwrt.org; m...@adrianschmutzler.de
> Subject: Re: Restoring (old) config backups an
On 20/07/20 19:32, Henrique de Moraes Holschuh wrote:
Any thoughts on this? I am certainly to have overlooked a lot of
stuff, especially if it is present only on master. Also, handling of
an uci-defaults "reset" (so that they'd run again) in
non-initramfs/overlayfs based system is likely
Hello,
> The problems we've observed with the backup *restore* functionality are:
>
> * It is applied with a simple reboot, and _apparently_, it has no hooks
> or other way to ensure system sanity before (or after) the backup restore.
>
> Which would be fine if the following point was never true:
