On Wed, 2018-04-25 at 13:13, Damiano Verzulli wrote:
> On 25/04/2018 00:22, Stefan Monnier wrote:
>
> > Was so sure I didn't need to
> > do it again. I know this data is flushed upon reboot, but is it also
> > flushed at other times (I could swear that I haven't rebooted since the
> > last time I had done "opkg update")?
>
> Three things come to my mind:
>
> 1 - I learnt that "uptime" is much more trustable than my mind, when
> needing to take decisions based on "reboot-time" of my
> little-devices-OpenWRT-based :-)
>
> 2 - I'm wondering --right now-- why "opkg update" is _NOT_
> reboot-persistent. I mean:
To save space on devices, which is usually scarce on the storage.
> - is having _OLD_ package indexes WORSE than not having them at all?";
> - are package indexes kept in memory? Why aren't they flushed on the
> file-system?
>
> What am I missing, here?
>
> 3 - It would be nice --as a new feature of the "opkg" client tool-- to
> raise an alert when package indexes is too-old or, worse, is completely
> missing. I for myself, a couple of years ago, spent much time exactly
> missing this requirement ("opkg update"). It was such a bad-feeling that
> since then, _EVERY_ time I need to install something, I _ALWAYS_ prefix an
> "opkg update" :-)
It could be set by editing /etc/opkg.conf and set some directive. I
forgot exact syntax, because some years passed when I did that, but I
think it could be 'lists_dir', to point to somewhere in the permanent
storage with enough free space.
By default it points to /var but the /var is symlink to /tmp which is
tmpfs.
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
