Tails

#1 Updated by intrigeri 2014-01-09 08:24:23

> When using Persistence read-only, the `Persistent` folder is currently writable, even
> though changes are not saved. It should actually by read-only in order not to confuse
> the user.

I beg to disagree.

First, that’s on purpose, both by design and documented: “If you
select the Read-Only check box, the content of persistent volume will
be available and you will be able to modify it but the changes will
not be saved.”

There are valid usecases (including things I do myself) that need this
kind of pseudo-write access to files: most software get kinda confused
when they cannot write to their state / lock / log /
whatever directory.

Also, changing a feature’s behaviour 1.5 years after introducing it is
likely to confuse people too…

But perhaps the Greeter and/or the documentation aren’t clear enough
wrt. what read-only persistence is about?

Please start this discussion on tails-dev if you want to carry on with
this proposal.

#3 Updated by intrigeri 2014-02-06 13:26:29

At the monthly meeting, we agreed here that this doesn’t look like a bug. Then, unless the discussion is (re)started on tails-dev, we’ll close the ticket after next month’s meeting.