Re: [Tails-dev] next big features: status update

Borrar esta mensaxe

Responder a esta mensaxe
Autor: anonym
Data:  
Para: The Tails public development discussion list
Asunto: Re: [Tails-dev] next big features: status update
02/29/2012 07:15 PM, intrigeri:
>
> The general testing process would be:
>
> 1. use the USB installer to install Tails on a USB stick
> 2. boot the newly installed Tails
> 3. use tails-persistence-setup to bootstrap a persistence container


This step failed once for me with an udisks error stating something like
"daemon is inhibited". I'm pretty sure it was because I had set a sudo
password in tails-greeter, and if so all we need is an appropriate
sudoers.d file for tails-persistence-setup.

>   4. "configure which bits are persistent" is not implemented yet,
>      so create a live.persist file in the TailsData filesystem:
>      https://tails.boum.org/todo/persistence/#index7h3
>   5. reboot
>   6. enable persistence in tails-greeter
>   7. enjoy


Other than that it seems to work just fine. Oh, I enjoyed it! :)

I have a few comments:

* We're currently quite wasteful when allocating space to the Tails
partition. On a 1.88 GiB USB stick a whooping 1.46 GiB was allocated
for Tails, leaving only 424 MiB for TailsData. The Tails installation
I used was just 767 MiB, leaving 732 MiB unused. That seems a bit
excessive or do we anticipate wheezy to be that much of a monster?

I'm not sure what the right approach would be here. It would be sweet
to have a slider which goes from $TAILS_ISO_SIZE to
min($SIZE_OF_USB_DRIVE, $LARGEST_TAILS_ISO_SIZE_WE_WANT_TO_SUPPORT)
which determines the size of the Tails partition. Depending on where
the slider is some label would show warnings like:

  - "This is likely too little space for being able to upgrade Tails in
    the future" and
  - "This will just leave only $LOW_NUMBER MB of space for persistence"


when appropriate.

* I think we should activate the --log-file option for both the list
and activate calls of live-persist. This will make it a lot easier to
debug certain errors when we're testing this, and if support to
include them is added to whisperback, also good when it's released
into the wild.

Cheers!