[OpenWrt-Devel] opkg upgrade all

[Luiz Angelo Daros de Luca]

Just like any Linux distribution, it is recommended to not mix a kernel
from a different release with runtime from another release. However, if
there is no incompatibility between them, you are free to do as you want.
The more distance each kernel is, the more likely to have
incompatibilities.

OpenWRT, although, is not developed with upgrade in mind. So, packages that
are renamed will be kept at the old version, and new package will not be
installed if not required by an existing package. You might get a mix of
kernel, old and new packages at the end. If, by chance, they are all
compatible, it will work nicely.

You'll need to mix old and new repos as any new kernel module must come
from the old repo. I don't know how well opkg deal with this.

Besides that, there is the extra space used. I guess jffs2 is also worse in
performance and compression.

It is just no good reason to do an upgrade and not a reflash. If you and
the packages are doing the backup correctly, you just need to reinstall all
extra packages after the new system is installed.

Regards,

Em qua, 30 de mar de 2016 02:30, Michal Hrusecky <Michal.Hrusecky at nic.cz>
escreveu:

> Luiz Angelo Daros de Luca -  1:41 30.03.16 wrote:
> > Michal,
> >
> > Google is your friend ;-)
>
> He pretends he is, but didn't provided the answer I was looking for, just
> plenty of workarounds I mentioned ;-)
>
> > But I'll easy your search
> > https://wiki.openwrt.org/doc/techref/opkg
> >
> > Check the upgrade description.
>
> Reread and the only thing that is mentioned there is general discourage to
> do
> upgrades and be careful what you are doing and that there are generally no
> updates available apart from trunk and that opkg will not upgrade kernel.
> No
> technical problem and no specific issue with upgrade all.
>
> > Regards
> >
> > Em ter, 29 de mar de 2016 às 04:45, Michal Hrusecky <
> Michal.Hrusecky at nic.cz>
> > escreveu:
> >
> > > Hi,
> > >
> > > there is a patch in OpenWRT that disables option to upgrade all
> packages
> > > and
> > > allows upgrading only specified packages which leads to plenty of
> answers
> > > online how to do that[1][2][3][...] Does anybody remembers the reason
> for
> > > disabling it? The only thing I can think of is discouraging people from
> > > doing
> > > upgrades and encourage them to reflash new squashfs image as they
> might not
> > > have enough free space. But as you can see, people will try and do it
> > > anyway so
> > > it might be a good idea to let the command there as it will be probably
> > > safer
> > > with integrated command than with random scripts on internet. Or is
> there
> > > some
> > > other reason and some real problem?
> > >
> > > [1] https://sandalov.org/blog/1777/
> > > [2]
> > >
> https://www.codeden.net/2015/05/upgrade-all-openwrt-packages-with-a-single-line-command/
> > > [3] http://blog.vanutsteen.nl/2014/01/12/openwrt-upgrade-all-packages/
> > > _______________________________________________
> > > openwrt-devel mailing list
> > > openwrt-devel at lists.openwrt.org
> > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> > >
> > --
> >
> > Luiz Angelo Daros de Luca
> > luizluca at gmail.com
>
-- 

Luiz Angelo Daros de Luca
luizluca at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20160330/fcccd01f/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel