Hi both,
On 11/07/2026 20:47, Cyril Brulebois wrote:
Michael Tokarev <[email protected]> (2026-07-11):
Re-reading #925979 again, it feels like at the time, things were in
hurry for the upcoming buster release, and "something" went wrong.
But I really don't see where the breakage might come from, - it is
just wrong. Upstream busybox without the hacks Just Works, and it
works better than our hacked version (because of the changes in
showenv() to display the "bad" variabled).
Maybe that was the issue here? -- somewhere in d-i it compared the
output of `set` with something? But it is very unlikel.
The regular upstream version should work just fine...
I think it should be okay to drop the two patches now and see what
happens next.
I'll do that in a couple days, if no one objects.
I don't have enough time or energy to look back at what happened exactly
at the time, but I'm pretty sure something broke in some obvious
fashion, and that whatever I implemented (even if it looks weird now)
restore whatever was broken.
From memory, what broke was passing d-i preseed options that contain a
slash as kernel arguments. 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.
Cheers,
Chris
--
Chris Boot
[email protected]
