Bug #696


Is opkg db stored in volatile dirs?

Added by Hammel about 5 years ago. Updated about 4 years ago.

04 - Applications
Target version:
Start date:
10 Mar 2019
Due date:
% Done:


Estimated time:
01 - Critical


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.

Actions #1

Updated by Hammel about 5 years 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.
Actions #2

Updated by Hammel over 4 years 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.

Actions #3

Updated by Hammel about 4 years ago

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

Updated by Hammel about 4 years 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