Tails

For context, here’s what my trusted machine looks like:

$ df -h / /home
Filesystem                  Size  Used Avail Use% Mounted on
/dev/mapper/armor--vg-root   19G   16G  2.2G  88% /
/dev/mapper/armor--vg-home  367G  330G   19G  95% /home

which means I made sure there was plenty of space on my home directory for the 3.11 release process, but I was a little short on my root filesystem, which includes /tmp.

The IUK creation loop triggered ENOSPC and left a bunch of temporary files and mount points, but there was also no way to figure out when it happened. Unfortunately, tails-create-iuk works on the specified output file directly, so it can leave a corrupted file behind. (Maybe it could work on a temporary file and rename it into place so that we get the specified output file only if everything went fine?)

That’s why I’m proposing two patches:

• the former makes it possible to set TMPDIR, and suggests doing so in the paragraph before the IUK generation loop;
• the latter simply prints which IUK is currently being generated.

Thanks for considering.