Re: [Tails-dev] Feature #5301 - Clone or Backup Persistent V…

Delete this message

Reply to this message
Author: sajolida
Date:  
To: The Tails public development discussion list
Subject: Re: [Tails-dev] Feature #5301 - Clone or Backup Persistent Volume
u:
> Andrew Gallagher:
>> Nobody interested?
>
> I guess most of us are simply quite busy atm - but yes, as we created
> this ticket initially, we are interested in such a solution. Thank you
> for working on this.


Hi Andrew, sorry for not answering earlier but as u said we're all too
busy right now. It's the end of the year and we have to finish many
projects.

We have "backup system for persistence" on our roadmap for 2016 [1][2]
and I'll be the one to work on the broad picture, UX design, etc. So I'm
definitely interested in your work but I wanted to test it before
answering (but couldn't find the time to do so), tough I won't be able
review your Perl code.

[1]: https://tails.boum.org/blueprint/roadmap_2016-2017/
[2]: https://labs.riseup.net/code/issues/5301

> I had a quick view, but I am not knowledgeable in Perl and just saw that
> you use rsync, as suggested also in our blueprint on the matter:
> https://tails.boum.org/blueprint/backups/
> Did you read it?
>
> The Installer is written in Python and uses GTK so I suppose that a
> backup that wants to get integrated into the installer should probably
> use Python (correct me if that is totally wrong, please).


Right. At the moment I'm playing with Deja-Dup [3] for the backups of my
Tails. I really like the integration in the desktop but, as it's running
as the amnesia user, it can't create a perfect clone of the persistent
volume. So your approach is also something we've considered, see #8812 [4].

[3]:
https://wiki.gnome.org/action/show/Apps/DejaDup?action=show&redirect=DejaDup
[4]: https://labs.riseup.net/code/issues/8812