Guidance on resolving early networking and setup-alpine issues
I would like some guidance on what is likely to be accepted in terms of MR that touch https://gitlab.alpinelinux.org/dalpine/mkinitfs https://gitlab.alpinelinux.org/alpine/alpine-conf and https://gitlab.alpinelinux.org/alpine/aports. For proper resolution all three repositories will requires at least one MR. This gets a little awkward.
In a nutshell, the issue is that setup-alpine
does not handle well the situation where a network (especially DHCP, hence activating udhcpc
via https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/master/initramfs-init.in#L164 )
There are a few places in setup-alpine
and other setup-*
scripts where the network configuration is altered and the network goes and and comes back up. This affects SSH sessions (which @macmpi mentioned in alpine-conf!99 (merged)) as well as my attempt to add automatic answerfile execution with a kernel cmdline parameter danielfdickinson/mkinitfs!1 and danielfdickinson/aports!1 for which I created an issue in mkinitfs#26 .
This resulted in the discovery of alpine-conf#10525 , which is ultimately the topic of this issue. I'm willing to put in the work to get this working, but I'd like to know that if I put the time in that I'm doing so in a way that is likely to be accepted rather than wasting my time (of which I have not nearly enough).
Thank you for your consideration.