Re: [T(A)ILS-dev] Freeze ->0.7?

Delete this message

Reply to this message
Autor: bertagaz
Data:  
Para: The T(A)ILS public development discussion list
Assunto: Re: [T(A)ILS-dev] Freeze ->0.7?
On Thu, Feb 10, 2011 at 04:55:01PM +0100, intrigeri wrote:
> Hi,
>
> bertagaz@??? wrote (10 Feb 2011 14:41:49 GMT) :
> > Commits 9e34169b... to 1d080597... should have closed the todo item
> > on implementing memory wiping on media removal. Seems to be ready
> > for the freeze :)
>
> Wow, seems nice. Building a test image.


Did so too before commiting, and it worked, but peer review is good :) I
didn't test on a cdrom this time, as it's only minor change and only in
the cache mechanism.

> One remaining question: any idea what the impact of the memlockd is on
> minimal system requirements for running and using T(A)ILS?


Biggest files are the initrd.img, the kernel, the libc and the kexec
executable. Other executables are all linked to almost the same libs.
I'd say that it shouldn't be more than 20M max.

> It seems like we don't mention any minimum RAM on the website yet
> (though we should) but IIRC 0.5 was useable with 384MB: one could run
> iceweasel with a few tabs and Pidgin at the same time.
>
> Squeeze-base builds probably raise the bar a bit, as does the locking
> of memory of the files needed for memory wiping on boot media removal.
> I am curious how much they do.
>
> Bye,
> --
> intrigeri <intrigeri@???>
> | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
> | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
> | We're dreaming of something else.
> | Something more clandestine, something happier.
> _______________________________________________
> tails-dev mailing list
> tails-dev@???
> https://boum.org/mailman/listinfo/tails-dev