Feature #7422
Do not duplicate syslinux on the ISO root filesystem
0%
Description
The solution to Bug #7345 duplicates syslinux, both inside the squashfs and on the image’s root fs. We could avoid that and use the in-squashfs syslinux binary without root privileges by employing stuff like fuseiso (in Debian), "squashfuse":https://github.com/vasi/squashfuse (not in Debian, but see [1] below), and fakechroot (in Debian) instead of a real chroot for running the syslinux binary. Or similar tools.
Beyond eliminating the duplication of syslinux, we’d get the “mechanism to run post-upgrade scripts” mentioned in Bug #7345#note-4, which may come in handy in the future.
[1] As an alternative to squashfuse it should be easy to make a sudo-safe wrapper around mount -o loop -t squashfs ..., that checks that the destination folder is writeable by the $SUDO_USER.
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2014-06-24 | |
|
Related to Tails - |
Resolved | 2016-04-14 | 2019-01-29 |
|
Related to Tails - |
Resolved |
History
#1 Updated by intrigeri 2014-06-20 12:59:16
- Category deleted (
Installation) - Status changed from New to Confirmed
Removing the category, as this implies changes both in Tails Upgrader and Tails Installer.
#2 Updated by intrigeri 2014-06-21 20:12:12
- related to
Bug #7345: Tails 1.1~beta1 created by upgrade from ISO from a 1.0 USB does not boot added
#3 Updated by Anonymous 2018-08-18 13:52:44
- related to
Feature #15292: Distribute a USB image added
#4 Updated by intrigeri 2018-08-18 14:12:17
- related to
Feature #15806: Use GRUB for USB boot on EFI 64-bit added
#5 Updated by intrigeri 2018-08-18 14:14:31
- Status changed from Confirmed to Rejected
I don’t think it’s worth the effort. It’ll be made irrelevant by Feature #15292 except for sticks cloned with Tails Installer, but we should do Feature #15806 anyway.