Bug #16006

USB image: adjust documentation

Added by Anonymous 2018-09-28 10:55:57 . Updated 2019-01-29 11:00:20 .

Status:
Resolved
Priority:
Normal
Assignee:
sajolida
Category:
Target version:
Tails_3.13
Start date:
2016-04-14
Due date:
% Done:

100%

Feature Branch:
doc/16006-usb-images
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:
316

Description

This is just a placeholder ticket.

Subtasks

Feature #15660: Adapt our installation instructions to have 2 different downloads Resolved

100
Bug #16007: Document the usage of graphical dd tools Resolved sajolida

100
Bug #16163: Clarify updated release process requirements for USB image Resolved

100
Bug #16205: Fix PO files on the USB image doc branch Resolved

100

Related issues

Related to Tails - Feature #16408: Document how to run from a virtual USB storage in virt-manager from a USB image Resolved 2019-01-29

History

#1 Updated by sajolida 2018-11-11 09:17:22

  • Feature Branch set to doc/16006-usb-images

Sorry for the mess but I’m renaming our integration branch to doc/16006-usb-images (before it was called doc/15660-usb-images which is only a subticket).

#2 Updated by sajolida 2018-11-17 11:34:21

  • Target version set to Tails_3.11

#3 Updated by sajolida 2018-11-17 12:30:02

  • Assignee changed from sajolida to cbrownstein
  • Target version deleted (Tails_3.11)
  • QA Check set to Ready for QA
  • Feature Branch changed from doc/16006-usb-images to doc/15660-cleaning-up

Hey! Here is a branch that includes all the cleaning up that I could spot.

We might find other tiny bits to clean up here and there but this should be most of it.

Please have a look!

#4 Updated by intrigeri 2018-11-23 08:41:52

Hi sajolida! I see that doc/16006-usb-images is still being built on Jenkins and has commits not found in doc/15660-cleaning-up. Shall it be merged there or deleted?

#5 Updated by sajolida 2018-11-29 16:42:18

  • Assignee changed from cbrownstein to sajolida
  • QA Check deleted (Ready for QA)

doc/16006-usb-images is our integration branch (and Bug #16006 our master ticket).

Today I could merge all the others ones we still had into it and I tried to delete them on Jenkins as well.

I’ll close this ticket once Cody acked my comment Feature #15660#note-9.

#6 Updated by intrigeri 2018-12-01 09:41:43

  • Status changed from Confirmed to In Progress

#7 Updated by intrigeri 2018-12-01 11:36:52

  • Feature Branch changed from doc/15660-cleaning-up to doc/16006-usb-images

Do we have a plan wrt. doc for users to try the USB image, possibly in a alpha release at the end of the year and/or for 3.12~rc1?

#8 Updated by sajolida 2018-12-04 09:29:45

> Do we have a plan wrt. doc for users to try the USB image, possibly in a alpha release at the end of the year and/or for 3.12~rc1?

Very good point! I didn’t think about this earlier. Oops…

I see 2 low-cost options for users to test the USB images, as part of an alpha or 3.12~rc1:

  • Publish somewhere a PDF version of the steps for Windows, macOS,
    Linux, and Debian on the command line. See what we sent to the sponsor
    already. That would be the cheapest.
  • Have a simplified version of these instructions in the call for
    testing rc1. We could copy only the parts of Markdown on using Etcher
    and GNOME Disks, maybe even skip the screenshots if we want to spare a
    few MB in the Git history, etc. This might a bit nicer for people.

#9 Updated by sajolida 2018-12-04 12:13:17

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)

All done :)

#10 Updated by intrigeri 2018-12-05 12:57:40

> I see 2 low-cost options for users to test the USB images, for example as part of 3.12~rc1:

OK, good to see we have options :)

#11 Updated by Anonymous 2019-01-04 14:19:23

  • Status changed from Resolved to Confirmed
  • Assignee set to sajolida
  • QA Check set to Info Needed

@sajolida: on my Debian system (currently Stretch) I’m asked for my root/sudo password when restoring the image. Do we want to add this in the documentation? It is currently not there.

#12 Updated by sajolida 2019-01-07 19:03:16

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

I’d rather move track new issues as bug fixes and keep this ticket closed; otherwise we might never close it. See you on Bug #16318.

#13 Updated by segfault 2019-01-18 12:59:48

  • Status changed from Resolved to Confirmed
  • Assignee set to sajolida
  • QA Check set to Info Needed

Is there a plan to update the documentation of running Tails from a virtual USB storage in virt-manager (https://tails.boum.org/doc/advanced_topics/virtualization/virt-manager/index.en.html#index5h1)? The USB image can be used for this instead of using Tails Installer. The image must be increased to be at least 7200 MiB, I always do this with this command:

dd if=/dev/zero of=PATH_TO_TAILS.img conv=notrunc oflag=append bs=1000M count=6

#14 Updated by intrigeri 2019-01-19 09:26:30

>

> dd if=/dev/zero of=PATH_TO_TAILS.img conv=notrunc oflag=append bs=1000M count=6
>

FWIW one can get a simpler command line by using truncate.

#15 Updated by Anonymous 2019-01-29 11:00:20

  • Status changed from Confirmed to Resolved
  • Target version set to Tails_3.13

I’m reclosing this ticket and open Feature #16408 for the last remaining question.

#16 Updated by Anonymous 2019-01-29 11:01:06

  • related to Feature #16408: Document how to run from a virtual USB storage in virt-manager from a USB image added