Bug #696

Is opkg db stored in volatile dirs?

Added by Hammel over 1 year ago. Updated 8 months ago.

Status:ClosedStart date:10 Mar 2019
Priority:ImmediateDue date:
Assignee:Hammel% Done:

100%

Category:04 - Applications
Target version:1.1.0 - Upgrades
Severity:01 - Critical

Description

Installing packages once makes them show up immediately with opkg list, but a reboot shows they aren't installed. This suggests the db is being stored in a volatile location.

Associated revisions

Revision 3c776d34
Added by Hammel 8 months ago

RM #696: Properly configure opkg.conf so package info is retained between boots. Package info is stored in overlay.

History

#1 Updated by Hammel over 1 year ago

There is a config file in /etc/opkg/opkg.conf. It can be updated to set the db directory, as described in the OpenWRT Opkg documentation.

You might want to change the lists_dir ext /var/opkg-lists to lists_dir ext /path/on/disk if your device has 32 MiB
or less of RAM and you expanded your firmware's storage space in an external drive, so you can use opkg without
causing Out Of Memory errors.

#2 Updated by Hammel 11 months ago

With the migration to a versioned squashfs/overlay boot process I now have a structure on the third partition that is non-volatile and could be used for package management. It's arguable that package management should exist within the overlay, of course. So research should be done on how to handle packages on system upgrades.

The full set of config file options is available in the man-page.

Options I probably want to add:
  • arch
  • cache_dir
  • info_dir
  • lists_dir
  • status_file
  • tmp_dir
Some that I need to investigate:
  • offline_dir
  • overlay_dir
  • volatile_cache

I might want to setup a dummy download url for later use too.

#3 Updated by Hammel 9 months ago

  • Priority changed from Urgent to Immediate
  • Severity changed from 03 - Medium to 01 - Critical

#4 Updated by Hammel 8 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Implemented, tested, committed and pushed.

Closing issue.

Also available in: Atom PDF