|author||Tails developers <firstname.lastname@example.org>||2012-10-02 13:12:14 +0200|
|committer||Tails developers <email@example.com>||2012-10-02 13:14:25 +0200|
Document how the persistence presets are implemented.
Diffstat (limited to 'wiki')
1 files changed, 10 insertions, 5 deletions
diff --git a/wiki/src/contribute/design/persistence.mdwn b/wiki/src/contribute/design/persistence.mdwn
index b75447a..4e5e86e 100644
@@ -242,12 +242,17 @@ Persistence settings changes are taken into account at next boot.
* apart of this, let's consider non-directories persistence an
advanced feature: to start with, and possibly forever, this could
only be configured by manually editing live-persist file
-* a few **presets** are made available (e.g. `~/.gnupg/`); the GUI
+* a few **presets** are made available (e.g. `~/.gnupg/`);
+ technically, each of these has a name, optionally a short
+ description and icon, and the needed information to make a simple
+ directory persistent (e.g. make `/home/amnesia/.gnupg` persist,
+ as the "gnupg" sub-directory of the persistent volume).
+ The GUI
displays every available preset, along with its current
- (enabled/disabled) status, and optionally a short description and
- icon; therefore, tails-persistence-setup needs to have means to
- merge the presets list with the configuration read from the input
- configuration file; to this end, it needs to know if a given preset
+ (enabled/disabled) status and available details (description, icon).
+ tails-persistence-setup has means to
+ merge its presets list with the configuration read from the input
+ configuration file; to this end, it knows if a given preset
is enabled in the input configuration file;
* by default, the current configuration is displayed as a list of
items (= config lines); listed items may be toggled on/off; an *Add