Project

General

Profile

Bug #17179

create-usb-image-from-iso maybe mixes syslinux data between Vagrant box and chroot

Added by anonym about 2 months ago. Updated about 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Build system
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

When working on migrating the Vagrant box to Debian buster some syslinux-related differences between the USB images were found.

The changes we did in #16748 were probably incomplete: for example, even if we run chroot/usr/bin/syslinux, that binary will probably look for its data files (MBR and such) in / and not in chroot/, so there's a change that we were still mixing up bits of Stretch (from the Vagrant box) with bits from Buster (from the chroot).

So, let's properly chroot into chroot/ when running syslinux. The comment #16748#note-12 might be a starting point.


Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by anonym about 2 months ago

#2 Updated by anonym about 2 months ago

anonym wrote:

The changes we did in #16748 were probably incomplete: for example, even if we run chroot/usr/bin/syslinux, that binary will probably look for its data files (MBR and such) in / and not in chroot/, so there's a change that we were still mixing up bits of Stretch (from the Vagrant box) with bits from Buster (from the chroot).

We should verify this before we implement the suggested solution. I guess we could just run the same commands under strace or similar to record which files are actually accessed.

#3 Updated by anonym about 2 months ago

  • Subject changed from create-usb-image-from-iso mixes syslinux data between Vagrant box and chroot to create-usb-image-from-iso maybe mixes syslinux data between Vagrant box and chroot

Also available in: Atom PDF