On 7/12/26 00:03, Chris Boot wrote:
From memory, what broke was passing d-i preseed options that contain a slash
as kernel arguments.
Yes, this is what #925979 is about. The problem is that I
don't see this happening now, nor was happening with the
version at the time (without the d-i-env-hack) - I built the
older busybox to see how it worked - it allows having
variables/with-slashes just fine.
See the resulting diff -- in there, the upstream codepath
which allows funny variable names is being taken only in d-i
mode, while in non-d-i mode, this is disallowed. Our patch
*restricted* funny-named variables usage compared with the
upstream version.
> So if you build a busybox without the hack, try > passing e.g. "netcfg/get_hostname=it-works-now" to d-i and see what you get. I seem to remember
it was about as simple as that, and it certainly may
have been changed or been fixed in more recent versions of busybox or d-i.
Yeah. The only problem is that I don't know how to build
d-i - I never looked this way, ever. This might be quite
a problem for me :)
Have some guide for me? :) Or maybe you can try building
it yourself with the "fixed" busybox?
Thanks,
/mjt
