Project

General

Profile

Bug #5672

Feature #4685: Umbrella: New software update feature

Feature #4690: Umbrella: New FreeNAS build / packaging / update creation process

Where should the package database go?

Added by Sean Fagan over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Sean Fagan
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Right now, I've got the package database going into /data -- it's writable, has space, and doesn't get shadowed by a mfs mount (unlike /etc/ and /var).

However, if we go to having a separate dataset for /data, this will cause issues with the setup. In that case, it would need to go to a new location. It generally only needs to be writable when doing an update or install, but it needs to accurately reflect the root filesystem.

History

#1 Updated by Sean Fagan over 6 years ago

  • Status changed from Unscreened to Investigation

#2 Updated by Sean Fagan over 6 years ago

  • Status changed from Investigation to Resolved

Okay, it's going into /data/pkgdb

That was easy.

We'll put the configuration file for updates in /data. This will be used and manipulated by the update code, possibly at the behest of the GUI.

#3 Updated by Jordan Hubbard about 6 years ago

  • % Done changed from 0 to 100

Also available in: Atom PDF