IRC channel #tails gateway report From: Jan. 10, 2014 To: Jan. 17, 2014
*** Documentation and Website:
People think the documentation about *installing* Tails (manual method) and
creating a persistent volume should be *clearer*
somehow. There is confusion about creating a running Tails (source USB)(that
cannot be made persistent) and the Tails you
install onto a (Target) USB with Tails installer which can be made persistent
by running *configure persistent volume*.
Much of the confusion comes with the *manual* install method. Users think that
persistence can be setup on the first
(source) usb after using Universal USB installer or dd'ing the iso and are
upset and they think they wasted a USB stick.
For some reason they don't *notice* or *read* (more probable) the warning
notice there about no persistence on source USB.
3 people said the documentation was unclear about this. Maybe it should also be
mentioned in the *configure persistence*
documentation that persistence cannot be setup on the *source/first* USB if you
used the manual install method?
One of the users thought that UUI (Universal USB Installer) *was/is* the Tails
installer
I read the documentation multiple times and it seems clear to me
*** Call for testing:
1 reported test of 0.22.1~rc1
*** Issues:
1 user reported losing their persistent volume on reboot after a normal
shutdown -Tails 0.22, user could
still input PW into Tails greeter and boot to Tails desktop (but persistent
volume was gone) Tails greeter
would also reject a wrong PW and would also boot to desktop with no persistence
enabled. --seems to be a problem with
the aufs bind maybe?
1 user reported that his persistence.conf file had been _reset?_ (for lack of a
better word) to reading: 0,0-1 ALL
-with all configured pesets *missing*, user had to copy/paste presets from
another Tails usb to gain access -Tails 0.22
*** Known Issues:
weasel | on tails-i386-feature_uefi-0.23-20140110T0926Z-568489c, the tails
installer, at least in
| Clone&Install mode, will detect my 2nd USB stick,
| will start the process and say "Resetting Master Boot Record of
/dev/sdd", and then just hang
| if the usb-stick is read-only.
| maybe it should catch that and produce some sane error message.
| both the manual isohybrid install and the cloned install boot on my
(thinkpad) x220.
| similarly, on boot, if persistence is enabled but read-only is not
selected, the system hangs on
| read-only usb sticks
*** Features:
<< no comments >>
*** Miscellaneous:
<< no comments >>
_______________________________________________
Tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
