Bug #15752

Instructions to copy persistence miss a step to reactivate the persistent features

Added by sajolida 2018-07-26 18:22:48 . Updated 2019-06-19 12:07:42 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Tails_3.14.1
Start date:
2018-07-26
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I’m dumping here what was reported to us on https://mailman.boum.org/pipermail/tails-ux/2018-July/003563.html:

There is just an instruction missing in the documentation book when you finish to move your persistent datas to another usb key... 
Once you start from the new usb key, you just need to go to Applications > System tools > and Configure persistent volume. 
Now you can check all the datas you want to be persistent at the next start.

But I haven’t tested it myself.

Subtasks

Related issues

Blocks Tails - Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing Resolved 2018-09-11

History

#1 Updated by sajolida 2018-07-26 18:23:19

  • Assignee set to cbrownstein

Cody: another bit of the big problem space “Persistent storage vs Backups”.
Please check which parts of it are the best to tackle first.

#2 Updated by sajolida 2018-07-26 18:23:39

  • blocks Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing added

#3 Updated by sajolida 2018-07-26 18:26:18

  • Subject changed from Instructions to copy persistence miss a step to reactive the persistent features to Instructions to copy persistence miss a step to reactivate the persistent features

#4 Updated by hummy 2018-08-03 16:25:51

sajolida wrote:
> I’m dumping here what was reported to us on https://mailman.boum.org/pipermail/tails-ux/2018-July/003563.html:
>
> […]
>
> But I haven’t tested it myself.

I have made the test and by following the documentation when you create a new persistent volume you select the features you want to make persistent(point 3 of section “Create a new USB stick”). Then, you copy the folders and reset the perms as instructed and if you selected the features previously, no need to redo that.

So this ticket could be closed. Maybe add a comment in the doc( [https://tails.boum.org/doc/first_steps/persistence/copy/index.en.html] ) about the need to select the persistent features when you create the new persistent volume could make the subject clearer.

#5 Updated by sajolida 2018-08-04 10:01:10

  • Assignee changed from cbrownstein to sajolida
  • Target version set to Tails_3.9

Cody: if you don’t mind I’ll take over this problem space for some time since I’ve been working on Bug #15685 lately.

#6 Updated by sajolida 2018-08-13 13:59:44

  • Target version changed from Tails_3.9 to Tails_3.10.1

#7 Updated by sajolida 2018-09-11 17:57:36

  • blocked by deleted (Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing)

#8 Updated by sajolida 2018-09-11 17:57:41

  • blocks Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added

#9 Updated by sajolida 2018-10-21 20:47:06

  • Target version changed from Tails_3.10.1 to Tails_3.11

#10 Updated by sajolida 2018-12-10 15:40:13

  • Target version changed from Tails_3.11 to Tails_3.12

#11 Updated by sajolida 2019-01-28 18:45:35

  • Target version changed from Tails_3.12 to Tails_3.13

#12 Updated by sajolida 2019-03-15 18:05:41

  • Target version changed from Tails_3.13 to Tails_3.14

#13 Updated by sajolida 2019-05-10 11:14:38

  • Target version deleted (Tails_3.14)

#14 Updated by sajolida 2019-06-04 06:57:43

  • Target version set to Tails_3.15

#15 Updated by sajolida 2019-06-07 13:56:28

  • Status changed from Confirmed to Rejected
  • Assignee deleted (sajolida)

@hummy is right: there’s already a step for that:

Enable again on this new USB stick the persistence features of your choice.

#16 Updated by anonym 2019-06-19 12:07:42

  • Target version changed from Tails_3.15 to Tails_3.14.1