Hi Phil, Thank you so much for your response. Apologies for my delayed response.
>So far I've failed to persuade this code to leave a mktemp generated >name in /etc (or elsewhere), so I'm obviously not running it in the >correct context. Please explain the circumstances under which this bug >can be reproduced. To be specific, the temporary file in question is generated in the "/etc" directory within the "setup-dir" specified. For example: host$ setupcon --setup-dir /tmp/foo host$ ls /tmp/foo/etc/console-setup/ tmpkbd.yvvgAq host$ setupcon --setup-dir /tmp/foo1 host$ ls /tmp/foo1/etc/console-setup/ tmpkbd.EgYD9B >Even so, I'm dubious about the way this is being fixed, because it seems >to me that a randomly named file seems unlikely to be used by anything >for its configuration, so I'm left wondering why it's being saved at all. This temporary file is being referenced in a script named "setupcon" under the "/bin" directory within the "setup-dir" specified. host$ cat /tmp/foo1/bin/setupcon #!/bin/sh # A micro-version of setupcon with static configuration. kbd_mode '-u' loadkeys '/etc/console-setup/tmpkbd.EgYD9B' > '/dev/null' mkdir /run/console-setup >/run/console-setup/keymap_loaded exit 0 This script is generated here[1] [1] https://salsa.debian.org/installer-team/console-setup/-/blob/master/setupcon?ref_type=heads#L1286 At the moment, I am not clear on the details on how this config is used. I'll have a deeper look. If you have any thoughts on this please do let me know. Thanks and Regards, Adithya Balakumar
