Re: What's the deal with discover*?
> Currently, there's no python in d-i, so isenkram is a no-go (as already
> mentioned a few months ago).
The isenkram-autoinstall-firmware script is bourne shell, not python.
There is no need for python in d-i to use this. The python related
stuff part is for running when /target/ is operational (ie when tasksel
is executed. I suspect we are talking past each other, as your comment
do not make sense to me.