On Wed, 2019-03-06 at 07:55 +0100, Fabiano Fidêncio wrote: > On Tue, Mar 5, 2019 at 10:50 PM Cole Robinson <crobinso@xxxxxxxxxx> wrote: > > Another piece to consider: the script is generated in a predictable path > > ~/.cache/virt-manager/fedora.ks for example. It's not likely to happen > > but two virt-install runs could overwrite each others scripts here. Agreed that we should avoid this kind of collision. > > I'd > > expect the generated filename to be sometime like tmpfile output. > > One thing that we could easily do is generate the script in > ~/.cache/virt-manager/<random_generated_per_vm_name>/fedora.ks ... > > The problem we had in the past, if my memory is not playing tricks on > me, is that some distros (or Windows?) expected a specific filename. > Although it my not apply to initrd injection. I remember spending some time trying to convince d-i to pick up a configuration file *not* called preseed.cfg, with little success. Using a randomly-generated directory name would nicely sidestep the issue. -- Andrea Bolognani / Red Hat / Virtualization _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
