Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-21 Thread Adam Burns
On 21/03/17 20:15, anonym wrote: > I just meant that detailed knowledge about aufs is not central to > understanding Tails and being able to hack on it. :) I think it is enough to > know the general idea, that we stack filesystems on top of each other. OTOH > if this area excites you, by all

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-21 Thread anonym
Arnaud: > 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

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread Arnaud
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

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread anonym
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

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread intrigeri
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

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread Andrew Gallagher
> 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

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread 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 ? > I personally combine two approaches, depending on the need: > > * build a

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread intrigeri
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

[Tails-dev] Experimenting with Tails, preferred workflow ?

2017-03-14 Thread Arnaud
Dear Tails, 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. Right now, I'm trying to run Tails in a VM in this