On Sun, Nov 28, 2010 at 3:50 AM, koniu <[email protected]> wrote: > Greg, I'm not sure if I clearly understand your point but check this out: > > I took up the adventure and manually cleaned up > /overlay/usr/lib/opkg/status and /overlay/usr/lib/opkg/info/* to NOT > include the packages that are installed in /rom. Now opkg > list_upgradable doesn't give me all these bogus updates. > > However there's just been an update to an /overlay-installed package > libiwinfo: > > r...@marvin:~# opkg list_upgradable > libiwinfo - 10 - 11 > > > r...@marvin:~# opkg upgrade libiwinfo > Upgrading libiwinfo on root from 10 to 11... > Downloading http://10.7.7.7:8000/libiwinfo_11_ar71xx.ipk. > Installing libnl-tiny (0.1-1) to root... > Downloading http://10.7.7.7:8000/libnl-tiny_0.1-1_ar71xx.ipk. > Configuring libnl-tiny. > Configuring libiwinfo. > > As we can see it pulled libiwinfo's dependency libnl-tiny (which is > already installed in /rom) and - needlessly - installed it in > /overlay. > > So it seems that we need /overlay/usr/lib/opkg/status to include > /rom-installed packages. Or better yet /overlay to have an exact copy > of /rom. This is why various block-extroot setup instructions tell you > to copy contents of /rom to the new external filesystem: ie. > http://wiki.openwrt.org/doc/howto/extroot#configure.the.system.if.not.preconfigured
Yes, I understood that to be correct as well. I'm readig through the scripts today to get a more granular view of what happens. Might I inquire as to what router you have in case there are specifics for it. Wether you started with squashfs or jffs. I am using jffs only here.. > Which is what I've done. Then I rebooted and started using the extroot > writing everything, including newly installed packages, onto /overlay. > > But then (and this is the core of my issue) what happens after that > when we reflash the router with an updated image that has newer > version of, say, kernel: > - /rom/usr/lib/opkg/status shows the new kernel version > - /overlay/usr/lib/opkg/status shows the old kernel version > - /overlay version of the status file 'masks' its /rom version > - opkg thinks we've got a package to upgrade when we don't > - the package is marked as HOLD so it never gets upgraded in /overlay's status > - we're stuck with the message forever Yeah, that sounds strange to me too. > > My question really is: what is the preferred way of handling this? I would like to know as well. I'll be stabbing at this today as well, until my scheme for replacing redboot is ready to implement. -Greg > cheers, > koniu > _______________________________________________ > openwrt-users mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-users > _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
