Bug #12253
Use persistence.conf in Tails Server
Start date:
2017-02-18
Due date:
% Done:
0%
Description
Currently Tails Server does not use the persistence.conf. Instead, it bind-mounts the files/directories directly, both when the persistence option is enabled and when tails-service --restore
is executed. The systemd unit chroot_local-includes/lib/systemd/system/tails-server-persistence.service
executes tails-service --restore
after boot, to mount the persistent files.
It would be nice if instead we would use the same persistence framework everywhere.
Subtasks
Related issues
Related to Tails - Bug #11533: Add support for bind-mounted files to the live-boot persistence backend | In Progress | 2016-06-15 |
History
#1 Updated by segfault 2017-02-18 14:15:38
- related to Bug #11533: Add support for bind-mounted files to the live-boot persistence backend added
#2 Updated by intrigeri 2017-06-01 07:28:01
- Status changed from Confirmed to In Progress
Applied in changeset commit:b896d7f7051b76ec92aec8c212fc470b4de8febe.
#3 Updated by intrigeri 2017-06-01 07:31:20
- Status changed from In Progress to Confirmed
Ouch, sorry I’ve mistyped a ticket number and erroneously referenced this one.
#4 Updated by Anonymous 2018-01-16 10:16:09
@segfault, would you like to set a target version for this?
#5 Updated by segfault 2018-01-17 18:00:48
- Target version set to Tails_3.9
#6 Updated by segfault 2018-02-10 09:29:54
- Parent task set to Feature #5688
#7 Updated by segfault 2018-08-05 19:24:30
- Target version deleted (
Tails_3.9)