Initial flashing over "OEM-OpenWrt"

[Adrian Schmutzler]

Hi,

> -----Original Message-----
> From: Henrique de Moraes Holschuh [mailto:henrique at nic.br]
> Sent: Montag, 8. Februar 2021 12:02
> To: Chuanhong Guo <gch981213 at gmail.com>; Adrian Schmutzler
> <mail at adrianschmutzler.de>
> Cc: OpenWrt Development List <openwrt-devel at lists.openwrt.org>
> Subject: Re: Initial flashing over "OEM-OpenWrt"
> 
> On 08/02/2021 04:03, Chuanhong Guo wrote:
> > On Sun, Feb 7, 2021 at 12:49 AM Adrian Schmutzler
> > <mail at adrianschmutzler.de> wrote:
> >> when reviewing device-support PRs, I frequently encounter the case that
> initial flashing means sysupgrading from an OEM-modified OpenWrt.
> >>
> >> This obviously means that the config of this OEM-OpenWrt should be
> wiped to prevent config-clashes, but since we only provide sysupgrade in this
> case we can only tell the user to do so.
> >>
> >> In this context, I wonder whether we should exploit the compat_version
> for that purpose, i.e. make the initial "proper" OpenWrt image version 1.1.
> >> Since the OEM-OpenWrt won't know about compat_version, this
> technically will have the same effect as removing SUPPORTED_DEVICES, i.e.
> the user will need to use -F (and we still can't check whether he uses the
> necessary -F -n).
> >
> > Wouldn't the same message annoy all current OpenWrt users as OpenWrt
> > 19.07 and older don't know about compat_version either?
> >
> >> However, the compat_version approach will give us the chance to show
> an additional message, and thus at least will allow to instruct the user during
> the upgrade itself, and not just in the Wiki or in the commit message (which
> he might or might not read).
> >>
> >> The purpose of this e-mail is thus to ask:
> >> 1. Do we need this, or do we just expect the user to care, i.e. if he breaks
> the device by keeping config it's his fault?
> >
> > Fixing this kind of breakage is as simple as pressing down the reset
> > button if we have the reset button properly defined. I think that's a
> > fair price to pay for not reading the instructions :D
> 
> Can I humbly suggest providing "factory" images for these devices ?
> 
> After all, it doesn't matter if it is OEM openwrt you're updating from, if it is
> still a "vendor", and we already have this convention of "use factory images
> to update from vendor firmware to openwrt"...

I'd probably say yes if there was a nice and proper way to force resetting config there _only once_.
Is there one I'm just not aware of?

Best

Adrian

> 
> --
> Henrique de Moraes Holschuh
> Analista de Projetos
> Centro de Estudos e Pesquisas em Tecnologias de Redes e Operações
> (Ceptro.br)
> +55 11 5509-3537 R.:4023
> INOC 22548*625
> www.nic.br
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20210208/0873163a/attachment.sig>