Project

General

Profile

Bug #17116

Improve lost persistence.conf instructions on known issues page

Added by cbrownstein about 1 month ago. Updated 14 days ago.

Status:
Needs Validation
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:

Description

  • instead of reconfiguring the persistent features, persistence.conf.bak can be copied to persistence.conf
  • ownership of /live/persistence/TailsData_unlocked might need to be reset to root:root
  • warning: live-additional-software.conf might end up lost without a backup

Related issues

Related to Tails - Bug #10976: persistence.conf lost, recoverable by reconfiguring In Progress 02/12/2019
Related to Tails - Bug #17112: Persistence config files "insecure" backup get emptied in some situations Confirmed

History

#1 Updated by cbrownstein about 1 month ago

  • Related to Bug #10976: persistence.conf lost, recoverable by reconfiguring added

#2 Updated by cbrownstein about 1 month ago

  • Related to Bug #17112: Persistence config files "insecure" backup get emptied in some situations added

#3 Updated by cbrownstein 20 days ago

  • Status changed from Confirmed to In Progress

#4 Updated by cbrownstein 14 days ago

  • Status changed from In Progress to Needs Validation
  • Assignee changed from cbrownstein to sajolida

Here's a branch:

https://0xacab.org/cbrownstein/tails/commits/doc/17116-improve-known-issue-persistence-conf

  • instead of reconfiguring the persistent features, persistence.conf.bak can be copied to persistence.conf

I decided not to document this. The already-documented way is simpler.

  • ownership of /live/persistence/TailsData_unlocked might need to be reset to root:root

Done.

  • warning: live-additional-software.conf might end up lost without a backup

I'll probably create a separate ticket for this.

Also available in: Atom PDF