On Mon, Aug 8, 2016, at 03:32 PM, Joanna Rutkowska wrote:
> Hello,
>
> Is there any special reason why the partition where Tails installs itself
> is
> non-deterministic? It is thanks to differing timestamps on the
> filesystem.
What you have asked about sounds at least similar to an issue I had
https://git-tails.immerda.ch/tails/plain/debian/changelog
lists each Tails release as "unstable". Why? These are the final
releases; not betas or release candidates.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-d
ey there:
here a patch for a typo on the website.
please review and merge.
From c5f370cb5c61d81aa370046a4377d29a4426420b Mon Sep 17 00:00:00 2001
From: emma peel
Date: Thu, 25 Aug 2016 01:08:11 +
Subject: [PATCH] small typo
---
wiki/src/doc/first_steps/startup_options.mdwn | 2 +-
1 file c
Hello!
There are two new source releases available on dist.torproject.org.
Please remember to check the signatures.
Changes in version 0.2.8.7 - 2016-08-24
Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
option in 0.2.8.6, and replaces a retiring bridge authority. Everyo
Awesome explanation. Thanks heaps. Looks like the dotfiles option is the
most straightforward.
Re: upgrade hazards, maybe dconf locks could help:
https://help.gnome.org/admin/system-admin-guide/stable/dconf-lockdown.html
ghostlands
On 2016-08-24 14:18, intrigeri wrote:
ghostla...@autistici
ghostla...@autistici.org:
> Why is it not already possible for the persistence feature to save/reference
> the
> .config directory and everything in it (and whatever other config directories
> in the
> home directory)? And of course load these saved settings at startup?
This would persist not on
I'd like to butt in with a question here, with apologies for whatever
obvious things I may be missing (that I hope someone is also willing
point out):
Why is it not already possible for the persistence feature to
save/reference the .config directory and everything in it (and whatever
other co
segfault:
> Hi everone,
>
> the GSoC ends this week. My goal was to implement the basis of the Tails
> Server, which should include a GUI and a CLI to install, configure and
> start onion services in Tails. I implemented a prototype which meets
> this goal. There are nightly images [1] of Tails in
> I did not look at the branch but it should not completely remove the
> alt, just its contents when necessary.
Sorry for my misspelling, when I say "remove alt" I talk about the
content, not the tag itself.
xin
signature.asc
Description: OpenPGP digital signature
_