You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a release that was already copied to the collection of base datasets (/iocage/base/<RELEASE>), the datasets representing the datasets need to get updated as well.
I wonder what the most efficient way to do that is. Here are some options:
Run freebsd-update a second time
+ does not need to write/touch all files - HardenedBSD currently does not cache assets on the host (yet) - It it another source of errors that require our action (e.g. roll back changes from the previous release update, so that the release and the base do not diverge)
Copy over the files
+ simple - slow - reads and writes back from disk - errors like full disks may still require our action to handle rollbacks
Suggestions welcome
The text was updated successfully, but these errors were encountered:
When a release that was already copied to the collection of base datasets (
/iocage/base/<RELEASE>
), the datasets representing the datasets need to get updated as well.I wonder what the most efficient way to do that is. Here are some options:
Run freebsd-update a second time
+ does not need to write/touch all files
- HardenedBSD currently does not cache assets on the host (yet)
- It it another source of errors that require our action (e.g. roll back changes from the previous release update, so that the release and the base do not diverge)
Copy over the files
+ simple
- slow
- reads and writes back from disk
- errors like full disks may still require our action to handle rollbacks
Suggestions welcome
The text was updated successfully, but these errors were encountered: