Bug #15989

Update our plans to remove removable flag requirement

Added by Anonymous 2018-09-28 10:23:47 . Updated 2020-03-09 19:42:19 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Installation
Target version:
Start date:
2018-09-28
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Related to Tails - Feature #10731: Tails Installer should not allow installing on non-removable USB sticks Rejected
Related to Tails - Feature #6397: Support booting from devices exposed as non-removable Confirmed 2014-06-30
Related to Tails - Feature #15292: Distribute a USB image Resolved 2016-04-14 2019-01-29

History

#1 Updated by Anonymous 2018-09-28 10:35:38

  • blocked by Bug #15991: Code review & rubber-duck for USB Image added

#2 Updated by intrigeri 2018-10-09 09:23:03

  • blocks deleted (Bug #15991: Code review & rubber-duck for USB Image)

#3 Updated by intrigeri 2018-10-09 09:28:14

  • Target version changed from Tails_3.10.1 to Tails_3.11

“up to 4h, iff. it fits into intrigeri’s total allocated time budget” ⇒ I’ll only know if this fits once I’ve done the rest of my work, which won’t happen before the 3.10 release.

#4 Updated by intrigeri 2018-10-09 09:30:20

  • related to Feature #10731: Tails Installer should not allow installing on non-removable USB sticks added

#5 Updated by intrigeri 2018-10-09 09:30:50

  • related to Feature #6397: Support booting from devices exposed as non-removable added

#6 Updated by intrigeri 2018-10-12 14:21:11

  • Target version changed from Tails_3.11 to Tails_3.12

#7 Updated by intrigeri 2018-10-12 14:21:22

  • Type of work changed from Communicate to Research

#8 Updated by intrigeri 2018-11-02 17:43:38

Not sure if / how much it matters but commit:eca9bf61b0a9a5d7df435a150eea6302bd05b4e8 adds the FSUUID= option to the syslinux config :)

#9 Updated by intrigeri 2018-12-29 10:12:22

  • Target version deleted (Tails_3.12)
  • Deliverable for deleted (316)

intrigeri wrote:
> “up to 4h, iff. it fits into intrigeri’s total allocated time budget”

It does not fit. I would still like to look into this at some point but anyone should feel free to take it over. Please reassign the ticket to you before you start working on it, to limit the risk of race conditions and duplicated work :)

#10 Updated by Anonymous 2019-03-06 11:50:31

#11 Updated by intrigeri 2019-03-06 11:59:22

#12 Updated by intrigeri 2019-03-06 11:59:38

#13 Updated by intrigeri 2020-03-09 19:42:19

  • Status changed from Confirmed to Resolved

Done: see today’s updates to Feature #6397, Feature #7475, and Feature #10731.

I did not update the list of things that will need adjustments, after Feature #6397 is done, to fully support Feature #8422: I did that Feature #8422 years ago, it was never used, and it bitroted. I’d rather see us first implement the 6 years old Feature #6397, which will already solve some real-world problems, before I spend time making plans for the next steps.