anonym:
> Let me add one, which is a special case of intrigeri's last point:
>
> * start Tails and "symlink" the relevant/changed files from your Tails source
> tree into the correct places in the filesystem of a running Tails session. So
> first you use sshfs or libvirt filesystem shares to make
Arnaud:
> intrigeri:
>> I personally combine two approaches, depending on the need:
>>
>> * build a modified ISO image
>> * start Tails and modify files in there (it *is* writable, but of course
>> the modifications go to a ramdisk)
Let me add one, which is a special case of intrigeri's last po
Arnaud:
> intrigeri:
>> AFAIK, modifying the rootfs in a persistent manner will produce very weird
>> results next time you boot
> What do you mean ? Is it because of some security mechanism of Tails
> that will detect my changes ?
No. It's because some bits of the Tails startup process are
not i
> On 14 Mar 2017, at 08:32, intrigeri wrote:
>
> I personally combine two approaches, depending on the need:
>
> * build a modified ISO image
> * start Tails and modify files in there (it *is* writable, but of
> course the modifications go to a ramdisk)
If you know your Debian-fu and need to
intrigeri:
> AFAIK, modifying the rootfs in a persistent manner will produce very weird
> results next time you boot
What do you mean ? Is it because of some security mechanism of Tails
that will detect my changes ?
> I personally combine two approaches, depending on the need:
>
> * build a modif
Hi,
Arnaud:
> just pondering and wondering on the preferred way (if any) to experiment
> and modify the Tails OS. I'd be happy to have Tails running in a VM and
> WRITABLE, so that I can really play with it. This is really for
> experimenting purpose.
AFAIK, modifying the rootfs in a persistent m