Hi,
Roland Clobus (2021-02-16):
> On 16/02/2021 08:13, Juergen Fiedler wrote:
>> I am using a fairly up to date sid (live-build 1:20210122) to build a
>> sid ISO - and it's not working right now.
>>
>> This is caused by two invocations of mkfs.msdos that use the current
>> epoch as the volume-id...
>> The volume-id is supposed to be a 32bit hex number (in hex notation),
>> and the epoch is significantly larger than 8 digits. Older versions of
>> mkfs.msdos tolerated that - but the latest does not.
>>
>> Does the volume-id parameter in efi-image and binary_grub-efi serve an
>> important purpose? If not, could it please be dropped?
>
> The volume-id itself has no special importance. I've added volume-id
> parameter, because without it, the volume-id would have been chosen
> randomly, which makes the live image non-reproducible. I'll look into
> this to create a patch.
FWIW, in case it may help, here's how we create a the Tails FAT
filesystem reproducibly (pasting Python code as-is):
execute([
'mkfs.msdos',
'-v',
# Use constants for normally randomly generated or time-based data
# such as volume ID and creation time
'--invariant',
# Fill all 11 chars of the volume label to avoid any uninitialized
# memory from sneaking in
'-n', 'TAILS' + 6 * ' ',
self.partition.props.block.props.device,
])
Cheers!
