[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1010878: installation-reports: preseeding passwords doesn't work on mips64el under qemu



Hi Phil,

Quoting Philip Hands (2022-05-12 13:40:51)
> BTW I somehow failed to notice that you were pointing preseed/url at the
> example-preseed.cfg when I ran that locally.
> 
> Given that you're already relying on a network preseed, you should just
> put a copy of that somewhere you control, and make all the changes that
> you are trying to put on the command line into your preseed.cfg instead,
> and it should work fine.
> 
> Also, you can save some more command line characters by using aliases:
> 
>   https://d-i.debian.org/manual/en.amd64/apbs02.html#preseed-aliases
> 
> If you wanted to make your preseed setup clever enough to handle
> different arch's differently, from the same preseed files, then there
> are some examples of scripting here that may provide inspiration:
> 
>   https://hands.com/d-i/
> 
> (it's not got arch specific stuff, but it does demonstrate that you go
> wild with scripting, if you want to)

thank you, that's a great resource! I don't think I need full-blown framework
but reading the code made me learn about more things I can do with d-i. I'm
running into a problem though and maybe I can pick your brain a bit:

So I want to download a script (I'm running my own HTTP server) and execute it
at the end of the installation. I'm currently having this in my
d-i/bullseye/preseed.cfg:

d-i preseed/early_command string preseed_fetch setup-testbed /tmp/setup-testbed
d-i preseed/late_command string /tmp/setup-testbed /target

If I understand the docs of preseed_fetch correctly, then this should fetch the
setup-testbed script from a path relative to where it got the preseed file
from. Thanks to https://hands.com/d-i/ I now am just using

preseed/url=http://10.0.2.2:8000

Unfortunately (and thanks for pointing me to the keyboard shortcuts to access
the log) this results in the following:

May 13 07:26:28 preseed: successfully loaded preseed file from http://10.0.2.2:8000/d-i/bullseye/./pres
May 13 07:26:28 preseed: running preseed command preseed/early_command: preseed_fetch setup-testbed /tm
May 13 07:26:28 log-output: /bin/fetch-url: .: line 35: can't open '/usr/lib/fetch-url//setup-testbed':

I'm confused. Shouldn't preseed_fetch try to obtain the setup-testbed relative
to the preseed file it just obtained?

Thanks again!

cheers, josch

Attachment: signature.asc
Description: signature


Reply to: