> > I tested this on Debian Unstable, with an iso I already had > downloaded. There were some warnings about my internal hdd: > austin@debian-laptop:~$ tails-installer-launcher > [creator.py:622 (detect_supported_drives)] WARNING: Skipping device > '/org/freedesktop/UDisks2/block_devices/sda' connected to '' interface > [creator.py:622 (detect_supported_drives)] WARNING: Skipping device > '/org/freedesktop/UDisks2/block_devices/sda5' connected to '' > interface > [creator.py:622 (detect_supported_drives)] WARNING: Skipping device > '/org/freedesktop/UDisks2/block_devices/sda3' connected to '' > interface > [creator.py:622 (detect_supported_drives)] WARNING: Skipping device > '/org/freedesktop/UDisks2/block_devices/sda2' connected to '' > interface > [creator.py:622 (detect_supported_drives)] WARNING: Skipping device > '/org/freedesktop/UDisks2/block_devices/sda1' connected to '' > interface > > fyi (not sure if that's intended for users to see or not). In any > case, the installer worked fine on a 4GB usb key, though it did > require me to authenticate with sudo twice. Perhaps a warning should > be made that this will occur in the GUI (or recommend root). It booted > on my hardware that I normally use with tails.
I can confirm similar behaviour on stable. The sudo requests do not make it clear that they come from tails-installer, and there was a brief moment of confusion when I got an auth request from syslinux. Less savvy users may be concerned by this. But that's a niggle. A _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
