path: root/wiki/src/contribute/design/persistence.mdwn
diff options
authorintrigeri <>2017-04-29 09:27:50 +0000
committerintrigeri <>2017-04-29 09:27:50 +0000
commit6ce90a372d4eaa6c5987b85150f739bffbd934ba (patch)
tree0f10e8392903214212b730d3339abd207eced322 /wiki/src/contribute/design/persistence.mdwn
parent2c99752019cae824cc44d53ca1beb32375822b30 (diff)
Design doc: drop bits about read-only persistence (Closes: #12361).
Diffstat (limited to 'wiki/src/contribute/design/persistence.mdwn')
1 files changed, 2 insertions, 15 deletions
diff --git a/wiki/src/contribute/design/persistence.mdwn b/wiki/src/contribute/design/persistence.mdwn
index 9b660cf..b20269e 100644
--- a/wiki/src/contribute/design/persistence.mdwn
+++ b/wiki/src/contribute/design/persistence.mdwn
@@ -70,12 +70,7 @@ The Tails persistent volume is a LUKS-encrypted GPT partition, labeled
-Once a persistent volume is enabled, two operation modes are
-* read-write access: changes to persistent files are saved
-* read-only access to **only** be able to *use* persistent files
- (e.g. a GnuPG keyring) without leaving any new trace.
+Once a persistent volume is enabled, changes to persistent files are saved.
@@ -121,11 +116,6 @@ That's why we have decided to:
directory (e.g. `$HOME`) to regular files stored in
a persistent location (e.g. `.gitconfig`, `.vimrc`, etc.)
-The read-only mode was implemented by merging the persistent
-volume with a "diff" branch on ramdisk using aufs, and mount the
-resultant device, so that the mountpoint is seen as writable by
-applications but no actual change is made on disk.
The code we ship lives in the `tmp-persistent-custom` branch in
our [[live-boot Git repository|contribute/git]]. We build packages
from the `master` branch in there, and drop them into the Tails main
@@ -269,8 +259,7 @@ we've written a graphical [[!tails_todo boot_menu]]:
#### Design
-* asks whether to enable persistence at all; if yes, read-only or
- read-write
+* asks whether to enable persistence at all;
* ask list of possibly valid persistent containers to `live-persist`
* initial implementation (MVC -speak): the model (`live-persist` and
tails-greeter code that runs it) supports enabling multiple
@@ -290,8 +279,6 @@ backend / tails-greeter interface
### Long story short
0. The user chooses to toggle persistence on in `tails-greeter`.
-0. Still in `tails-greeter`, the user chooses if s/he wants read-only
- or read-write persistence.
0. `tails-greeter` asks `live-boot` the list of possibly valid
persistent containers.
0. For each such volume, `tails-greeter` asks the user to enter the